Closed reallymello closed 1 year ago
Here is a zip of the entire test project
I also want to clarify my expectation is that on reporting that if the waitFor fails with abortOnFailure false that the test is still considered passing as well
WaitForElement
commands always had hard asserts. For soft asserts we can use verify
.
We need to change the documentation.
Raised a PR to fix the doc: https://github.com/nightwatchjs/nightwatch/pull/3934
Closing this issue as this is not an actual problem. There is a problem related to it which is explained in this #3939
Description of the bug/issue
When I use waitForElementNotVisible with the abortOnFailure parameter set to false I expect the test to carry on without failures if the element is present and remains visible in excess of my specified wait time for it to no longer be visible. Conversely, if I use waitForElementVisible with abortOnFailure set to false and the element is present, but doesn't become visible within the specified duration parameter I expect the test to carry on without failure after waiting unsuccessfully for the condition.
However, in both cases the test fails with
expected "not visible" but got: "visible" or expected "visible" but got: "not visible"
respectively. It doesn't seem to matter if I use the abortOnFailure parameter. It seemingly is ignored.Steps to reproduce
Sample test
Command to run
Verbose Output
Nightwatch Configuration
Nightwatch.js Version
3.2.1
Node Version
18.16.0
Browser
Chrome 117
Operating System
Windows 10
Additional Information