Releases: nightwatchjs/nightwatch
v2.0.10
Fixed an issue occurring when using the Mocha integrated test runner and a test failure was logged in an async
testcases.
v2.0.9
v2.0.8
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 (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
v2.0.6
v2.0.5
v2.0.4
v2.0.0
The public NPM release of Nightwatch 2.0 is here and can be installed directly with:
npm i nightwatch --save-dev
Over the past few weeks we have worked tirelessly to finalise the apis, add a few more examples, and try and smooth over any rough edges.
Important Changes
- Added a new plugin API; check out the docs for how to create a Nightwatch plugin: nightwatchjs.org/guide/extending-nightwatch/plugin-api.html
- Added support for using
nightwatch.conf.cjs
as config file for projects that use ES Modules - Upgraded
chai expect
to version 5 and added support for using regular chaibrowser.expect()
assertions; this doesn't affect the existingexpect.element()
,expect.elements()
,expect.cookie()
,expect.title()
, andexpect.url()
.- Example:
See examples/tests/shadowRootExample.js for the complete example.const infoElement = element('.info'); expect(infoElement.property('innerHTML')) .to.be.a('string') .and.to.include('validation code');
Improvements
- Added several new assertions:
- titleEquals
- titleMatches
- urlMatches
- textMatches
- textEquals
- domPropertyMatches
- attributeMatches
- valueEquals
- hasClass
- hasAttribute
- elementsCount
- Added new element commands:
- getFirstElementChild
- getNextSibling
- getPreviousSibling
- hasDescendants
- isPresent
- Added new API mouse actions:
- clickAndHold
- rightClick
- releaseMouseButton
- Added new
--devtools
CLI flag to open the Chrome Devtools automatically
Fixes
v2.0.0-beta.3
v2.0.0-beta.2
- Fixed Fixed a regression issue with using execute() command - #2970
- Updated selenium-webdriver to v4.1 and other depedencies