-
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
.verify swallows custom assertion initialization errors #4147
Comments
hey assign these issue to me and I will resolve these |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug/issue
when I execute browser.verify.myCustomAssertion(), and there is an error inside myCustomAssertion definition function, I expect that the error will be visible in the test runner output console, but what happens is that no output is written for the custom assertion as if there was no such line in the test case at all. Also, no error message is logged to the test runner output console.
When the same custom assertion run via .assert,
browser.assert.myCustomAssertion()
, the error is visibleSteps to reproduce
npx nightwatch --group custom
files content
Sample test
Verbose Output
Nightwatch Configuration
No response
Nightwatch.js Version
3.4.1
Node Version
20.11.1
Browser
chrome (123.0.6312.59) on MAC
Operating System
MacOs 14.4 (23E214)
Additional Information
No response
The text was updated successfully, but these errors were encountered: