Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency nightwatch to v2 #579

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 14, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nightwatch (source) ^1.7.11 -> ^2.0.0 age adoption passing confidence

Release Notes

nightwatchjs/nightwatch

v2.2.2

Compare Source

Important fixes
  • Fixed #​2975expect.element().to.not.be.present throws error when the element is not present
  • Fixed – an issue with persisting http data for the HTML reporter
New features

The new Nightwatch init CLI tool is now available to use in order to kick-start a new Nightwatch test project in under 60 seconds.

Simply run:

npm init nightwatch
Nightwatch CLI tool preview

Release notes for create-nightwatch:
https://github.com/nightwatchjs/create-nightwatch/releases/tag/v1.0.0

Other
  • Downgraded selenium to 4.1.1 to mitigate a chromedriver startup issue

v2.2.1

Compare Source

The latest release introduces a new built-in HTML reporter and several new API commands based on the Chrome Devtools Protocol for mocking network responses, capturing logs, and more.

Improvements

Other

  • Added support to find frame when passing argument as id or name - #​3205
  • Upgraded selenium-webdriver to v4.2.0 - #​3215

v2.1.8

Compare Source

  • Added - platform methods in case of Appium client (#​3166)
  • Fixed - an issue with generating XML output for when running tests in parallel (#​3163)

v2.1.7

Compare Source

  • Upgraded the global package to fix an issue on windows

v2.1.5

Compare Source

  • Fixed #​3127 -- skipped count was incorrect in global reporter results
  • Fixed #​3163 -- a circular reference issue occurring sometimes when running tests in parallel
  • Added support to throw an error when passing undefined args in sendKeys command (#​3045)
  • Added support to find frame when passing argument as id or name (#​3097)
  • Added update to browserstack transport and built-in config (#​3148)
  • Added support for marking test scenarios passed/failed and send reason to Browserstack while using Cucumber as a test-runner (#​3132)

v2.1.4

Compare Source

  • Fixed #​3033 – global element() was ignoring the global locate strategy
  • Fixed #​3138 -- Unhandled rejection while using expect assertions in an async test step

v2.1.3

Compare Source

  • Fixed #​3159 - updated ejs to avoid a high severity vulnerability
  • Fixed #​3154 - updated peer dependency version of chromedriver

v2.1.2

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

The Nightwatch 2.1 release adds a few important fixes and several improvements, including upgrade to Selenium 4.1.1. Here's the full list:

Improvements

describe('sample with relative locators', function () {
  before(browser => browser.navigateTo('https://archive.org/account/login'));
  
  it('locates password input', function (browser) {
    const passwordElement = locateWith(By.tagName('input')).below(By.css('input[type=email]'));

    browser
      .waitForElementVisible(passwordElement)
      .expect.element(passwordElement).to.be.an('input');

    browser.expect.element(passwordElement).attribute('type').equal('password');
  });
});

  • New error stack trace output which parses and highlights the source code line – #​3071

image

  • Set network emulation settings in Chrome/Edge with the .setNetworkConditions() command (#​2996)

browser.setNetworkConditions({ 
  offline: false, 
  latency: 5, // Additional latency (ms). 
  download_throughput: 500 * 1024, // Maximal aggregated download throughput. 
  upload_throughput: 500 * 1024 // Maximal aggregated upload throughput. 
});

  • Automate the input of basic auth credentials with the .registerBasicAuth() command (Chrome/Edge) (#​3116)

browser
     .registerBasicAuth('test-username', 'test-password')
     .navigateTo('http://browserspy.dk/password-ok.php');

Important Fixes

  • Fixed #​3079 – unable to clear element in setValue command
  • Fixed #​3085 – failing waitFor commands did not failed the test when using the cucumber built-in runner
  • Fixed #​3124 - multiple terminal windows opening when running in Chrome on Windows
  • Fixed #​3086 - 'RangeError: Maximum call stack size exceeded' when requiring unknown modules

v2.0.10

Compare Source

Fixed an issue occurring when using the Mocha integrated test runner and a test failure was logged in an async testcases.

v2.0.9

Compare Source

  • Fixed #​3077 - an issue with page navigate where the url was defined as a function

v2.0.8

Compare Source

This releases adds a few important fixes and improvements. We have made sure that Nightwatch works very well when using the Selenium 4 server in standalone mode and we've added several improvements and fixes for when using Mocha as a test runner.

Users of Selenium Server can now install our own jar download library from NPM and then use it in Nightwatch with no other config necessary. Make sure that chromedriver or geckodriver are also installed from NPM. You can install the Selenium Server with:

npm i @​nightwatch/selenium-server
Fixes
  • Fixed #​3054 – default port was not updated for some commands when running in parallel mode
  • Fixed #​3052 – Running Nightwatch with Selenium Server 4 in standalone mode
  • Fixed #​3055 – Missing error message in case of overwriting an existing command
  • Fixed #​3050 – required definition of package.json in current directory
  • Fixed #​3075 - an unhandledRejection was occurring when assertion fails while in async mode and if followed by other chained assertions
  • Fixed #​3074 - chrome CDP commands loading was throwing an error
Improvements
  • Added support to start/stop Selenium Server separately when in parallel mode (nightwatchjs/nightwatch@282e269)
  • Added several improvements for child process output formatting when running in parallel mode with test workers
  • Added support to specify test workers count in the cli as --parallel=<number of workers>

v2.0.7

Compare Source

  • Fixed #​3031 - unable to start selenium server from nightwatch on windows

v2.0.6

Compare Source

v2.0.5

Compare Source

  • Added several improvements to better support component testing (d8dec00)
  • Added added an improvement for external globals to be persisted properly (af54791)

v2.0.4

Compare Source

  • Fixed an issue with expect not rejecting the promise correctly and causing an unhandledRejection (a17a7ac)
  • Added support for expect.element().an() to accept case-insensitive tag names and regular expressions (efb6f10)

v2.0.2

Compare Source

v2.0.1

Compare Source

v1.7.13

Compare Source

v1.7.12

Compare Source


Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 14, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN deprecated [email protected]: The functionality that this package provided is now in @npmcli/arborist
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN @octokit/[email protected] requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.

lerna notice cli v3.22.1
lerna info versioning independent
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/mocha/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

lerna notice cli v3.22.1
lerna info versioning independent
lerna info Bootstrapping 25 packages
lerna info Installing external dependencies
lerna ERR! npm install --ignore-scripts --ignore-scripts --no-audit --package-lock-only exited 1 in '@tds/community-skeleton-provider'
lerna ERR! npm install --ignore-scripts --ignore-scripts --no-audit --package-lock-only stderr:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @tds/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.2 || ^17.0.0" from the root project
npm ERR!   peer react@"^16.8.2 || ^17.0.0" from @tds/[email protected]
npm ERR!   node_modules/@tds/core-heading
npm ERR!     peer @tds/core-heading@"^2.2.5 || ^3.1.0" from the root project
npm ERR!   4 more (react-dom, styled-components, @tds/core-image, @tds/core-text)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! recompose@"^0.30.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR!   node_modules/recompose
npm ERR!     recompose@"^0.30.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-04-12T05_54_40_619Z-debug-0.log

lerna ERR! npm install --ignore-scripts --ignore-scripts --no-audit --package-lock-only exited 1 in '@tds/community-skeleton-provider'

@renovate renovate bot force-pushed the renovate/nightwatch-2.x branch from c7f4de7 to 1d49594 Compare April 12, 2022 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant