-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test runs infinitely with combination of async error, 'fail' event, and done callback #3349
Labels
Milestone
Comments
chrisbreiding
added
type: bug
pkg/driver
This is due to an issue in the packages/driver directory
labels
Feb 6, 2019
31 tasks
jennifer-shehane
added
the
stage: ready for work
The issue is reproducible and in scope
label
Feb 7, 2019
Is there any reason this is slated for |
Good point. Changed it to |
@chrisbreiding I think there are two separate issues here:
it('should timeout', (done) => {
cy.visit('/')
}))
|
cypress-bot
bot
added
stage: backlog
and removed
stage: ready for work
The issue is reproducible and in scope
labels
Apr 4, 2019
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: backlog
labels
Sep 6, 2019
cypress-bot
bot
added
stage: work in progress
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Sep 25, 2019
jennifer-shehane
added
stage: pending release
and removed
stage: work in progress
labels
Oct 1, 2019
The code for this is done, but this has yet to be released. We'll update this issue and reference the changelog when it's released. |
Released in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior:
Test will hang if there's an async error, use of the
fail
event to catch the failing test, and adone
callback. Since the command resolves before the error is thrown, thefail
event is not fired and thedone
never gets invoked.This is primarily an internal issue since we use the
fail
event to test Cypress. can be seen in the failing driver test in this PR. That test is using new and changed aspects of4.05.0, but it can reproduced in the current version of Cypress using the steps below.Desired behavior:
The
fail
event should be fired, which will allow the test to finish.Steps to reproduce: (app code and test code)
Versions
Cypress 3.1.5
Chrome 71
MacOS 10.14.2
The text was updated successfully, but these errors were encountered: