Skip to content

Releases: nightwatchjs/nightwatch

v2.4.1

20 Oct 20:13
9404c36
Compare
Choose a tag to compare
  • Fixed an issue resulting from await-ing test hooks properly in some cases 4f6c31

v2.4.0

19 Oct 15:15
c54a6c0
Compare
Choose a tag to compare

New features

The v2.4.0 release brings improved support for Component Testing, which includes:

  • @nightwatch/storybook
    • new official plugin which integrates Nightwatch with Storybook
    • adds ability to run component stories directly from Nightwatch, including:
      • interaction tests using the play() function
      • run test hooks in the Nightwatch context
      • run test() function in the Nightwatch context
      • run configured accessibility rules automatically using the axe-core suite of commands
  • vite-plugin-nightwatch
    • upgraded plugin to use Vite 3
  • @nightwatch/vue
    • new dedicated Vue.js component testing plugin which includes Vite 3 and manages its own Vite dev server
  • @nightwatch/react

New CLI flags

  • --serial to run tests in serial mode (disable parallelism)
  • --workers to specify the number of test workers to be used when running tests in parallel
  • --reuse-browser to reuse the browser session if running in serial mode

component testing related

  • --debug – automatically pause the test execution after mounting the component and open the Nightwatch debug REPL interface.
  • --story - allows to specify which story to run from the current file (when using Storybook or JSX written in component story format)
  • --preview - used to preview a component story/test; automatically pause the test execution after mounting the component.

Other Improvements

  • Added support to use --devtools CLI flag in Edge and Safari to open the Dev Tools automatically
  • Added support to enable running tests in parallel by default if not set PR #3364
  • Added support for using nightwatch.conf.ts as config file and a few other improvements for running typescript tests PR #3316

Fixes

  • Fixed #3404 an issue with the moveTo command
  • Fixed #3256 .verify assertions do not resolve when called from within the .perform() command

v2.3.9

24 Sep 17:27
ec82134
Compare
Choose a tag to compare

Minor update for the axe-nightwatch-verbose dependency.

v2.3.8

23 Sep 14:33
5197a7b
Compare
Choose a tag to compare
  • Fixed #3396 showing version using the --version cli flag
  • Fixed #3336 an issue with using browser.resizeWindow()

v2.3.7

16 Sep 15:07
449e928
Compare
Choose a tag to compare

Fixed #3355 – updating the build name using client.updateCapabilities did not work

v2.3.6

15 Sep 14:47
2712b15
Compare
Choose a tag to compare

v2.3.5

14 Sep 15:13
d994575
Compare
Choose a tag to compare
  • Added new CLI flag ``--report-filename` to specify the report file name for the JSON reporter d73a6f
  • Fixed #3361 -- expect.cookie always returning undefined value
  • Fixed an issue where the error thrown for using incorrect arguments for element commands was not reported if using async/await testcase e9e38c
  • Fixed #3372 -- chaining custom commands from page objects when imported through plugins interface
  • Added analytics feature to collect anonymous user metrics (opt in only) PR #3141

v2.3.4

02 Sep 07:48
161c11e
Compare
Choose a tag to compare
  • 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

19 Aug 12:27
e55a1ba
Compare
Choose a tag to compare

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

20 Jul 21:26
8909fa1
Compare
Choose a tag to compare

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
Nightwatch release walkthough