Protractor - ScriptTimeoutError: asynchronous script timeout: result was not received in 20 seconds

Question

I\'m new to Protractor and I am trying to run my script.

describe(\'Navigator homepage\', function() {
it(\'should proceed to login\', function() {
browser.         


        

Answer 1

I had a similar issue, I solved it by turning on ignore sync

browser.ignoreSynchronization = true

Answer 2

Given your added error-message (see comment), the cause seems an continuously polling $timeout, which lets a promise unresolved for indefinite time and therefore leads to a asynchronous timeout of protractor (see details here).

solution

The correct solution is to avoid the use of $timeout and use $interval instead. That way protractor can stay in charge of the ControlFlow, managing your asynchronous tasks. So it's kind of a software bug, not a protractor error.

your error message:

Failed: Timed out waiting for asynchronous Angular tasks to finish after 20 seconds. This may be because the current page is not an Angular application. Please see the FAQ for more details: https://github.com/angular/protractor/blob/master/docs/timeo‌​uts.md#waiting-for-a‌​ngular While waiting for element with locator - Locator: By(css selector, md-raised md-primary md-button md-ink-ripple). *The following tasks were pending: - $timeout: function (){return _this.getVersion()}*

Workaround

The not so nice workaround is to switch off the waitForAngular part of Protractor by setting browser.waitForAngularEnabled(false); (either in a beforeEach or directly in the spec.

However this also means, taking manually care of the controlFlow within the test specs itself. This requires using a lot of .then() and ExpectedConditions, losing one of the main advantages of Protractor.

Debug possibilities

Check the descriptions here for potential causes and workarounds. Specifically try also browser.waitForAngularEnabled(false); to exclude angular-protractor-issues.

If you can't find cause, it could be a timing issue (unlikely, but worth being examined at that point).

You can try to add log-messages to narrow down the effective order of execution:

describe('Navigator homepage', function() {
    it('should proceed to login', function() {
    browser.get('url').then(function(){
        console.log("Page is fully loaded");
        });
    });
    it('Clicks the proceed button',function() {
        console.log("Start 2nd Test");
        const proceedButton = element(by.id('auth-login-page-button'));
        proceedButton.click();
    });
});

Or you put the actions in the same test case, using then() to execute them synchronously:

describe('Navigator homepage', function() {
    it('should proceed to login', function() {
    browser.get('url').then(function(){
        const proceedButton = element(by.id('auth-login-page-button'));
        proceedButton.click();
    });
});

Open Homepage within onPrepare

As one nice side remark: If you always load the Homepage first, just put it into an onPrepare-part of your conf.js and it will always be executed once before your tests start:

onPrepare: function () {
    browser.driver.manage().window().maximize();
    browser.get('url');
},