A Jasmine Spec has timed out: Resetting the webdriver control flow
See original GitHub issueHi
I’m pretty new to protractor and currently using version 1.0.0-rc4
When I’ve got multiple specs, and I run them via protractor config.js, I get the following error
A Jasmine Spec has timed out: Resetting the webdriver control flow
with the first spec passing (logging into the website) but the next spec failing with the above line in the command prompt
Any ideas?
Issue Analytics
- State:
- Created 9 years ago
- Comments:32 (3 by maintainers)
Top Results From Across the Web
A Jasmine spec timed out. Resetting the WebDriver Control Flow
Jasmine has timeout for each spec i.e. each it in jasmine framework. so if any spec ( it ) exceeds jasmine spec's default...
Read more >A jasmine spec has timed out: resetting Webdriver control flow
This is a Protractor issue - Protractor treats timeout issues specially (since it needs to make sure that the control flow is clean...
Read more >angular/protractor - Gitter
A Jasmine spec timed out. Resetting the WebDriver Control Flow. Error: Timeout - Async callback was not invoked within timeout specified by jasmine....
Read more >PROTRACTOR:How to tell protractor to stop or skip the TEST ...
Waits for long time and throws A Jasmine spec timed out. Resetting the WebDriver Control Flow. EXPECTED BEHAVIOR: On failure on any Testcase, ......
Read more >Timeouts - Protractor - end-to-end testing for AngularJS
Looks like: an error in your test results - ScriptTimeoutError: asynchronous script timeout: result was not received in 11 seconds · Default timeout:...
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
Your second spec timed out - there are many possible reasons for this. Check out https://github.com/angular/protractor/blob/master/docs/timeouts.md
Hi, I also have a similar issue. Any update?