Dynamically set allScriptsTimeout from an it block
See original GitHub issueFeature request: Dynamically set allScriptsTimeout
from an it
block.
Motivation: Suppose uploading a large file to a website takes 3-5min. If I have allScriptsTimeout
set to 30s, Protractor will timeout automatically (due to the POST request taking longer than 30s). I prefer to keep allScriptsTimeout
relatively small (e.g., 30s) for all the other tests, and it would not be appropriate to increase the global timeout.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:9 (2 by maintainers)
Top Results From Across the Web
set timeouts dynamically - javascript - Stack Overflow
It seems that you've multiple elements with the same class, you can just use their index to create a dynamic array of timers....
Read more >Timeouts - Protractor - end-to-end testing for AngularJS
Looks like: an error in your test results - Timed out waiting for asynchronous Angular tasks to finish after 11 seconds. Default timeout:...
Read more >Getting Started for Selenium E2E Testing using Protractor
To setup the Protractor with ChromeDriver, set the directConnect property to true in configuration as in the following code block.
Read more >Is it possible to use AngularJS in a Dynamic block...
Hi everyone, I got a question for the Community about Angular in ServiceNow. I got it that you can create UI Pages or...
Read more >Protractor Tutorial: Handling Timeouts With Selenium
overriding default value of allScriptsTimeout parameter for ... The test specification i.e. the 'it block' of the Protractor testing case ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mwsessom
Sorry, I had the wrong script. If your run this you will see it works. Mind the comment in the first
it
-block at the endconfig
example test
output
I’m going to close the issue now based on the above testcase. You are able to influence it from the
it
-block. It’s still open for discussionjasmine.DEFAULT_TIMEOUT_INTERVAL is different than allScriptsTimeout.
jasmine.DEFAULT_TIMEOUT_INTERVAL is specific to Jasmine. allScriptsTimeout is specific to Protractor.
jasmine.DEFAULT_TIMEOUT_INTERVAL refers to the total time to run a single test. allScriptsTimeout refers to the time to wait for a single async request.
You can view the documentation here http://www.protractortest.org/#/timeouts