-
### Description of the bug/issue
When I use `element.findAll(selector).nth()` to find an element, I expect to put this element into the old command like `setValue(ele, text)`, but throw error. It wor…
-
### Description of the bug/issue
When I run my test with screenshots enabled on failure and my test fails I expect a screenshot to be saved under the screenshots directory of the current browser sc…
-
### Description of the bug/issue
When I run my test suite using
```ts
chromeOptions: {
args: ['--incognito'],
},
```
and I open a new tab in my test using `browser.window.o…
-
The below command won't fail cucumber tests when it fails.
```JavaScript
// These won't fail
await this.browser.waitForElementVisible(
'#not-existing-element',
1000,
…
-
Since most of our apps don't change in terms of essential functionality, it would not be a terrible idea to add end-to-end tests for some key processes / use cases. For example, we can add tests for:
…
-
When upgrading to nightwatch 1.0.0 or subsequent, the new api loader does not like the current way the testarmada assertions are written. I get this error:
`The assertion module needs to contain an…
-
### Description
When we do `browser.element.find(selector).assert.present()`, if the element is not found, we get the `NoSuchElementError` error, but in case of `assert.present`, this error should …
-
### Description of the bug/issue
I have an async page object command that returns an object containing Definition(s). Those definitions are found by chaining using syntax like
```ts
const billing…
-
We're currently at `nightwatch@0.9.21`. Version `1.0.0` was recently published, however there are some major changes that will break this repo.
https://github.com/nightwatchjs/nightwatch/wiki/Migra…
-
We need more user friendly commands which perform the equivalent of `elementIdElement()` and `elementsIdElement` but work more like `findElement()` and `findElements()`, accepting the same type of arg…