Open tamlyn opened 9 years ago
I'm having this same issue. I'm wondering if there's a way to just tell protractor to move on....
I'm able to use this module, write a protractor test to verify login, using this.
beforeEach(function() {
browser.ignoreSynchronization = true;
});
afterEach(function() {
browser.ignoreSynchronization = false;
});
I'm trying to write some end-to-end tests for my application which uses this module. My problem is that Protractor waits for all
$http
requests to finish before running the tests. Since the request is intercepted, Protractor just times out:There's a related question on SO but no answers.
Anyone have a strategy for handling this situation?