CODEWITHSUNDEEP
javascriptautomationjasmineprotractorui-automation
sarathezil
sarathezil

Reputation: 11

Protractor: Failure during waitForPromise: asynchronous script timeout: result was not received in 11 seconds

Protractor regression test specs were working fine till last week, then out of nowhere when I run the same specs now protractor takes a lot of time to interact with the webelements like (getText() from dropDown,context menu so on) in the application even there were no changes in code. It throws this error:

"Failure during waitForPromise: asynchronous script timeout: result was not received in 60 seconds (Session info: chrome=75.0.3770.100) (Driver info: chromedriver=2.41.578737 (49da6702b16031c40d63e5618de03a32ff6c197e),platform=Windows NT 10.0.17763 x86_64) [11:24:57] E/plugins - ScriptTimeoutError: asynchronous script timeout: result was not received in 11 seconds"

Tried using this option in Onprepare function -browser.driver.manage().timeouts().setScriptTimeout(60000); After this step getting the same error which ends with "result was not received in 60 seconds"

Tried these below tags as well but all the pages in the application are angular only. When i use any of the below tags could able to resolve the above issue but other test cases are failing which are supposed to wait for angular.

browser.ignoreSynchronization = true;
browser.waitForAngularEnabled(false);

I can enable and disable these tags before and after the particular step, but I have 1000+ test cases and i have to invest a lot of time to find where and all it is happening , moreover these tests were working well for more then 8 months and why failing now?

Upvotes: 1

Views: 302

Answers (2)

Ram
Ram

Reputation: 11

Add the following code snippet in your configuration file & re run it.

jasmineNodeOpts: { defaultTimeoutInterval: 100000 };

Upvotes: 0

Nitin Sahu
Nitin Sahu

Reputation: 621

enter image description here

I suspect that Driver version and chrome version incompatibility could be the reason for your problem. Since chrome driver 2.41 supports v67-69 and you are using v75. We also observed that there are many evident instances of this. I would suggest first make sure that drive and chrome browser compatibility before running any test case. You can update the webdriver-manager to get the right version of chrome driver

Upvotes: 0

Related Questions