v2.3.4

• Fixed #3284 – beforeEach hook was executed even it() / test() is marked as skipped
• Fixed #3352 – a TypeError was thrown if a custom command is throwing an error

v2.3.3

Improvements

• Added support for using native mobile drivers (#3335)
• Added new cli flag --list-files (#3246)
• Added support to retain the html report between test runs (#3309)

Fixes

• Fixed #3304 - added buildname to settings when running on Browserstack
• Fixed #3301 - awaited asserts used inside custom commands were hanging the test run
• Fixed #3257 - expect.elements(..).count should be 0 if element not found

v2.3.0

New feature

• Added pause and debug capabilities - #3243

  Pause mode

  Add a pause() command to pause your tests indefinitely. In pause mode, you can check the state of your browser or use DevTools to debug. You can also see step-by-step execution from the paused state where the test automatically pauses at the next step.

  Note: The current pause command usage stays as is. You can pass the duration of the pause and the test will pause only for that duration on the mentioned devices.

  Debug mode

  Add a debug() command to pause your test at that step. The debug mode also allows you to check the state of the browser and use DevTools. Furthermore, it offers you an interface to try out nightwatch commands and assertions while your test is paused.

Improvements & Fixes

• Added actionable error messages - #3233
  Redesigned error messages for improved context, relevant documentation and mitigation steps to fix the error.
• Fixed #3177 – additional options in config does not getting passed to cucumber runner
• Added support for waitUntil to use a custom message for timeout errors (4b79d79)

Release Walkthrough

Nightwatch release walkthough

v2.2.3

• Fixed #3183 – setting chromeOptions in older format didn't work
• Fixed #3130 – an issue with setting the driver service port number in case of parallel runs with test workers
• Fixed #3096 – an issue with session request redirection when using SauceLabs
• Fixed #3264 – HTML reporter raw http logs were failing to escape html
• Added support for .mockNetworkResponse() to accept relative urls (to launch_url setting)
• Other – Upgraded selenium-webdriver version to 4.3.1 (#3278)

v2.2.2

Important fixes

• Fixed #2975 – expect.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

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

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

• Added new integrated HTML reporter with test status, assertion logs & raw HTTP logs - #3223; Read more

• Added built-in API commands for working with the Chrome Devtools Protocol - #3208:

  • setGeolocation
  • captureNetworkRequests
  • mockNetworkResponse
  • setDeviceDimensions
  • getPerformanceMetrics
  • enablePerformanceMetrics
  • takeHeapSnapshot
  • captureBrowserConsoleLogs
  • captureBrowserExceptions

• Added --mocha cli flag to quickly switch the test runner to use Mocha

• Added --open cli flag to open the generated HTML report automatically

• Added new integrated JSON reporter

• Added support for using multiple reporters - #3003; to specify more reporters just add several --reporter arguments, e.g.: nightwatch --reporter html --reporter junit --reporter custom-reporter

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

• 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

• Upgraded the global package to fix an issue on windows

v2.1.6

This release only contains a few dependency updates, such as the ejs package and the cucumber peer dependency version which was causing issues in newer version of NPM.

v2.1.5

• 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)