-
I just upgraded to version 2.0 and I'm seeing that verify.equal is failing the test rather than continuing when the assertion fails.
-
## Describe the bug
when I run tests in parallel, only one connects and others fail with this error : Failed to connect to ChromeDriver on localhost with port 9515.
this used to work on older vers…
-
## Summary
As we traverse down the path of adding front end pages to the site, we'll need to have trustworth integration tests that validate the site is working as expected when changes are made. Thes…
-
## Describe the bug
Setting `output: false` in the nightwatch.conf.js file is not working for navigation output.
I am using cucumber test runner using these configs:
```
module.exports = {
ou…
-
### Description of the bug/issue
When using `setValue` in tests, and also ´setPassword`, the field is visible in the html, json and xml reports.
I found an old issue regarding this that was clo…
-
Hi,
I am trying to switch into an iframe, but I cannot in the current headless Chrome version. Looks like a faulty interface is being used in the following method which accepts a string, but should…
-
### Description of the bug/issue
I'm running a test on multiple envs (dev,qa,stage,...) all on same browser (Chrome).
I noticed that only one XML is found at the end of the run because each time the…
-
I wrote a custom test runner with the new version 2.0.4 which is really cool! Love the new architecture of the programmatic API. The test runner sequentally runs multiple tests. If a test fails, it sh…
-
## Describe the bug
When we call .waitForElementVisible with a "false" flag for abortOnFailure, the sample script will pass if the call is not nested. However, if the .waitForElementVisible() is part…
-
### Description of the bug/issue
Exit Code is always zero value with nightwatch - 3.1.2 and @cucumber/cucumber - 9.3.0 which causes gitlab CI/CD the test job appears as pass because it is expecting…