You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jasmine will time out the test after 460 milliseconds, but the listener will still fire after 460 milliseconds. This can cause the next it block to fail, or even worse, if the error occurs before Jasmine has started the next test, the whole thing fails as an uncaught exception.
The text was updated successfully, but these errors were encountered:
It seems I've problems with this issue in combination with protractor and grunt-protractor. In this combination its unable to get a clean termination of the running processes.
Are there any updates or workarounds for this bug?
If an individual command is still running when the test comes out, listeners registered on it will still be called. For example:
Jasmine will time out the test after 460 milliseconds, but the listener will still fire after 460 milliseconds. This can cause the next
it
block to fail, or even worse, if the error occurs before Jasmine has started the next test, the whole thing fails as an uncaught exception.The text was updated successfully, but these errors were encountered: