How do I ask protractor not to wait for angular?

[Droogans]

When I click a menu element on my page, it fires off a request to an api. Protractor will (correctly) wait for that request to return, have angular redraw some elements, and then will continue.

In this example, when I click this element, it will expose a sub-menu, and will also make a call to the api.

This causes protractor to hang around and wait a few seconds for the call to finish, even though I have no interest in it. I'd like to have it simply "click through" these menus, opting not to wait until angular is completely finished with the api request.

Do you have any suggestions for these kinds of situations? Is there any way to have protractor cancel an api call from angular so that it's done waiting?

[mcalthrop]

Assuming I understand your question correctly, I don't think Protractor can cancel an API call, as that is in the JS code running in the browser.

However, to tell Protractor not to wait for HTTP requests to return, do the following:

browser.ignoreSynchronization = true;

NOTE: it is generally bad practice to do this, so I'd suggest you follow this kind of pattern, so that you set the value just for the tests you want:

describe('When you do x', function () {
  beforeEach(function () {
    browser.ignoreSynchronization = true;
  });
  afterEach(function () {
    browser.ignoreSynchronization = false;
  });
  it('y should happen', function () {
    expect(...).toXXX();
  });
});

[alexanderjeurissen]

As @mcalthrop already mentioned disabling Synchronization is an option.

Another solution would be to add a mock module that intercepts that specific API requests that hangs your tests.

describe('When you do x', function () {
  var httpBackendMock = function () {
    angular.module('httpBackendMock', ['ngMockE2E', 'yourAngularApp'])
      .run(function ($httpBackend) {
        $httpBackend.whenPOST('https://apiUrl/api/v1/endpoint')
          .respond(
            200, {}
        );
      });
  };

  beforeEach(function () {
    browser.addMockModule('httpBackendMock', httpBackendMock);
  });

  afterEach(function () {
    browser.removeMockModule('httpBackendMock');
  });

  it('y should happen', function () {
    expect(...).toXXX();
  });
});

[Droogans]

Can't mock it as these are specifically meant to run in a live environment,
this would violate that requirement.

We have a separate set of protractor tests that do mock all api requests.
On Mar 4, 2014 5:12 PM, "Alexander Jeurissen" notifications@github.com
wrote:

As @mcalthrop https://github.com/mcalthrop already mentioned disabling
Synchronization is an option.

Another solution would be to add a mock module that intercepts that
specific API requests that hangs your tests.

describe('When you do x', function () {
var httpBackendMock = function () {
angular.module('httpBackendMock', ['ngMockE2E', 'yourAngularApp'])
.run(function ($httpBackend) {
$httpBackend.whenPOST('https://apiUrl/api/v1/endpoint')
.respond(
200, {}
);
});
};

beforeEach(function () {
browser.addMockModule('httpBackendMock', httpBackendMock);
});

afterEach(function () {
browser.removeMockModule('httpBackendMock');
});

it('y should happen', function () {
expect(...).toXXX();
});});

Reply to this email directly or view it on GitHubhttps://github.com//issues/576#issuecomment-36691076
.

[alexanderjeurissen]

I understand, then I think that the solution that @mcalthrop suggested (temporarily ignoring synchronisation in a describe block) might be your only option...

[juliemr]

Sounds like this is solved - ignoreSynchronization is your best bet.