-
When using `sequence` to read fields I've found that it sometime does not correctly handle the case where a list is empty, which can lead to subsequent fields holding incorrect data.
For example th…
-
### Description of the bug/issue
We are unable to upgrade to newer that chrome 86 since newer versions forces w3c protocol on browserstack.
In the transport.js there is an IF .usingBrowserstack() a…
-
Sorry to bother you, but you seem very knowledgeable on this subject. How can I make the appium server point to YWinAppDriver through the appium-windows-client? I want to (try to) use your driver as …
-
### Description of the bug/issue
When a test fails, I'd like to get the final URL of the page for easier debugging.
To do this, I've registered a `afterEach` event that gets the URL of the browser…
-
### Description of the bug/issue
- I execute npx nightwatch tests/* --reporter mocha-junit-reporter
- Expected result: JUnit report is created
- Actual result: "_Error: An error occurred while…
-
### Description of the bug/issue
Once a test fails, I'd like to keep the browser open so I can see what went wrong.
I can do this by setting `end_session_on_fail` to `false`, which works perfect…
-
## Describe the bug
When using .waitForElementPresent and the element does not exist in the DOM I get the following error in the output log
`[22184:13332:0409/200244.007:ERROR:device_event_log_imp…
-
### Description of the bug/issue
If the last `verify` command inside an `it-block` fails, the rest of tests are skipped. Ideally the tests should keep running.
### Steps to reproduce
Run the p…
-
### Description of the bug/issue
I am using an example that is recommended in documentation. Repo can be find here https://github.com/nightwatchjs-community/nightwatch-examples.
In globals.js We h…
-
### Description of the bug/issue
When I execute a test suite with several test cases in it leveraging @nightwatch/apitesting I'm seeing log entries from the tests in that suite getting mixed up under…