Open reallymello opened 1 year ago
The element has been found, but it results in unhandled rejection while running assertions for text.
The root cause is the global expect
node leaking into subsequent nightwatch command nodes.
Example:
expect(infoElement.property('innerHTML')).to.include(
'card validation code'
);
browser.click(infoElement);
For these two nightwatch commands here are the verbose logs
Logs show that the global expect command is executed in between click
command execution
Description of the bug/issue
When I use browser.expect on an element found using .find() I expect it to run my expect assertion, but instead the browser terminates and I get an unhandled rejection.
Steps to reproduce
Running this test without line 18 works, but with the browser seems to terminate early
Sample test
Command to run
Verbose Output
Nightwatch Configuration
Nightwatch.js Version
2.6.21
Node Version
18.16.0
Browser
Chrome 113
Operating System
Windows 10
Additional Information