Bump nightwatch from 1.3.6 to 1.7.12

[dependabot]

Bumps nightwatch from 1.3.6 to 1.7.12.

Release notes

Sourced from nightwatch's releases.

v1.7.11

• This version is only updating the proxy-agent dependency package to the latest version.

v1.7.10

• Fixed #2899 – an issue with setValue/sendKeys commands
• Added new updateValue command

v1.7.9

• Fixed an issue where selenium_host config property wasn't set (#2892 )
• Added support to set browserName to null in order to accommodate Appium (#2882)

v1.7.8

• Fixed #2777 – an issue with using Chrome and Edge in parallel (#2790)
• Fixed #2794 – using .verify asserts with await or waitFor commands with abortOnFailure=false didn't work in case of test failure (#2802, #2797)
• Fixed #2817 – inconsistent response format when using findElements command (#2820)
• Added support to send last error as failure reason in Browserstack transport (#2778)

v1.7.7

• Fixed #2748 - tests not running in parallel when source folder is specified as cli argument

v1.7.6

• Fixed #2755 – npm postinstall issue on windows

v1.7.5

• Fixed an issue with parallel running where the number of available workers wasn't set correctly in some cases - 7754054b34fcc750549d6a204f7f03dbaec97a41
• Fixed xml output generation when running tests with multiple environments in parallel (#2734)

v1.7.3

Nightwatch v1.7

New features

Nightwatch v1.7.0 introduces a few major new features and improvements for the test runner and also regarding the test syntax, such as:

Fluent API

It is now possible to use ES6 async/await syntax and also chain api commands together in the same test case; e.g.:

it('find elements example', async function(browser) {
    const resultElements = await browser
      .url('https://nightwatchjs.org')
      .findElements('.features-container li');
resultElements.forEach(item => console.log('Element Id:', item.getId()))

});

Integrated support for Microsoft Edge

You can now use the newer (Chromium-based) Microsoft Edge browser to run your Nightwatch tests. The auto-generated nightwatch.conf.js already includes configuration, so you can just run by passing the edge environment:

</tr></table> 

... (truncated)

Commits

• b08733e 1.7.12
• af22b87 Update README.md
• fdab42b added eslint 7
• cea8af0 Update README.md
• 84bf32f Update README.md
• 0bf8d08 updated dependencies
• 7fcac7e Update README.md
• 73f27e7 updated dependencies
• b69a97e 1.7.11
• 0e9921e updated dependencies
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #68.