-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Errors in custom commands hang the test (fail silently in parallel, no reports generated) #1965
Comments
This seems to only happen in custom commands. If I move the logic to the test, it fails and continues |
I am also seeing this behaviour. Could it be related to #1941? |
Possibly @baubie , my only hesitation is the reported versions though. This was working in 1.0.11 and lower, where as 1941 is present in 0.9.21 as well. But it definitely looks similar |
@ClaytonAstrom Thanks for reporting this. The afterEach(browser) {
browser.end()
}, |
It's only related in the sense that it is also affecting custom commands and their completion, but it appears to be a different problem. In the case of #1941, the issue happens when the user doesn't emit the "complete" event (so it's more of an improvement), while in this case the completion should happen as a result of the "error" event, which is not happening. |
Should be fixed in v1.0.18. |
I'm currently experiencing this in 1.0.19. It might be the way the callbacks are put together that prevents the parent nightwatch command from figuring out that it failed? A utility command to find and then click an element never recovers context and just hangs indefinitely.
it gives me "timed out while waiting for element to be present" -- got "not found" (the first command, the waitForElementPresent). then it hangs. |
Nightwatch: 1.0.17 (reproducible in 1.0.12+)
Node: 8.12.0
OS: Mac 10.13.6
Webdriver: Chrome 2.45
Standalone Grid: 3.141.5
Looks like custom commands are hanging on failure. In parallel, the testsuite is closed and we don't even see a report of the failure. This can be a lot of missed coverage. Seems to be introduced into 1.0.12.
The text was updated successfully, but these errors were encountered: