Update dependency nightwatch to v1.7.13 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
nightwatch (source)	1.4.0 -> 1.7.13

---

Release Notes

nightwatchjs/nightwatch (nightwatch)

v1.7.13

Compare Source

v1.7.12

Compare Source

v1.7.11

Compare Source

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

v1.7.10

Compare Source

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

v1.7.9

Compare Source

• 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

Compare Source

• 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

Compare Source

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

v1.7.6

Compare Source

• Fixed #​2755 – npm postinstall issue on windows

v1.7.5

Compare Source

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

v1.7.3

Compare Source

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:

$ nightwatch --env edge

Parallelism for Firefox, Chrome, Safari, and Edge

You can now run tests in parallel via workers in any browser. Not only that, but now you can also run via test workers across multiple browsers in parallel.

Example:

$ nightwatch --env edge,firefox,chrome --parallel

New API commands

• .findElement() / .findElements() - these commands provide improved support for locating single/multiple elements on the page; the response contains the web element id and a .getId() convenience method.

Example:

const resultElements = await browser.findElements('.features-container li');
resultElements.forEach(item => console.log('Element Id:', item.getId()))

const resultElement = await browser.findElement('.features-container li:first-child');
console.log('Element Id:', resultElement.getId());

• .setPassword - support to redact params in logs (#​2672)
• .isSelected() element command and assert.selected() assertion
• .isEnabled() element command and assert.enabled() assertion

Fixes & Improvements

• Added support to recursively append properties from super-env in test-settings (#​2718)
• Fixed #​2695 - use locate strategy from args when valid strategy is found for waitFor element commands (#​2716)
• Fixed #​2677 - add option to disable loading of typescript tests
• Fixed an issue where test status wasn't reported for parallel runs (#​2733)

v1.7.2: -beta

Compare Source

Minor update to the auto-generated nightwatch config.

v1.7.1: -beta

Compare Source

This is a minor update to increase the default timeout option for browserstack in the auto-generated nightwatch config.

v1.7.0: -beta

Compare Source

This is a pre-release version for v1.7.3

v1.6.4

Compare Source

• Fixed #​2402 - screenshots are not captured in some cases when failure occurs
• Fixed #​2508 - add timestamp in currentTest result
• Fixed #​2001 - add stackTrace for no element found errors

v1.6.3

Compare Source

• Fixed #​2532 - passing a custom message with only time(%d) placeholder
• Fixed #​2627 - an issue with custom commands written in Typescript
• Fixed an issue where passing timeout and retryInterval as element properties in assertions didn't work (#​2637)

v1.6.2

Compare Source

• Added filename_format config option for setting the filename format of the screenshots -- #​2023 (see docs

v1.6.1

Compare Source

• Fixed #​2624 - use locate strategy from config as default for page object elements

v1.6.0

Compare Source

• Added #​2559 – support for using TypeScript (.ts) for test files
• Added #​2616 – support for using config locate strategy as default for page object element selectors
• Fixed #​2573 – an issue where result of element() and elements() commands where inconsistent when used on section elements
• Fixed #​2522 – an issue where element results where incorrect for Safari in BrowserStack
• Fixed #​2582 – making sure the test results are not discarded when an uncaught exception occurs.

v1.5.1

Compare Source

• Fixed #​2529 - false warnings about settings being defined in globals

v1.5.0

Compare Source

Nightwatch v1.5 introduces support for using third-party automation libraries directly into Nightwatch tests, thus providing significantly more flexibility in writing custom commands/assertions and also the test itself. This functionality also aims to eliminate some of the burden in choosing between various frameworks, by providing the possibility to combine the functionality offered by other libraries, such as selenium-webdriver or WebdriverIO, with Nightwatch.

Other fixes and improvements:

• Fixed #​2245 - test_settings is undefined in global before hook
• Added --parallel cli flag for easier running of tests with test workers – 5cfc278
• Added a config setting to display timestamps in iso format – 1dad022

v1.4.3

Compare Source

• Fixed #​2489 - api commands throwing TypeError when called inside page section custom commands
• Fixed #​1969 - element selectors from page sections not working when used in custom commands

v1.4.2

Compare Source

• Fixed #​2488 - 'element not found' errors thrown by JsonWire protocol for /element requests were not ignored
• Fixed an issue where the WebElement ID is not retrieved correctly when using chrome with selenium server and jsonwire transport

v1.4.1

Compare Source

• Fixed #​2486 - mocha test runner was unavailable.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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, check this box

---

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

[renovate]

⚠ 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: pils-frontend/package-lock.json

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: copy-webpack-plugin@5.1.1
npm ERR! Found: webpack@3.12.0
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"3.12.0" from the root project
npm ERR!   peer webpack@">=2" from babel-loader@8.0.6
npm ERR!   node_modules/babel-loader
npm ERR!     dev babel-loader@"8.0.6" from the root project
npm ERR!   7 more (extract-text-webpack-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0 || ^5.0.0" from copy-webpack-plugin@5.1.1
npm ERR! node_modules/copy-webpack-plugin
npm ERR!   dev copy-webpack-plugin@"5.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@5.88.2
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0 || ^5.0.0" from copy-webpack-plugin@5.1.1
npm ERR!   node_modules/copy-webpack-plugin
npm ERR!     dev copy-webpack-plugin@"5.1.1" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/1b4392/3a0723/cache/others/npm/_logs/2023-08-07T19_49_58_505Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/1b4392/3a0723/cache/others/npm/_logs/2023-08-07T19_49_58_505Z-debug-0.log

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (85cc939) 22.34% compared to head (2599f81) 22.34%.
Report is 2 commits behind head on main.

❗ Current head 2599f81 differs from pull request most recent head 1ac859c. Consider uploading reports for the commit 1ac859c to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1052   +/-   ##
=======================================
  Coverage   22.34%   22.34%           
=======================================
  Files          14       14           
  Lines         179      179           
  Branches       21       21           
=======================================
  Hits           40       40           
  Misses        121      121           
  Partials       18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication