Changelog History
Page 1
-
v1.5.1 Changes
October 29, 2020- 🛠 Fixed #2529 - false warnings about settings being defined in globals
-
v1.5.0 Changes
October 20, 2020Nightwatch 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:
-
v1.4.3 Changes
September 18, 2020 -
v1.4.2 Changes
September 11, 2020- 🛠 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 Changes
September 06, 2020- 🛠 Fixed #2486 - mocha test runner was unavailable.
-
v1.4.0 Changes
September 04, 2020🐎 This version significantly improves the network stability and performance of the test runner, by improving the underlying http retry mechanism and error detection and reporting of API commands – a particularly important update for when using cloud testing services.
➕ Additionally, we have added better support for writing advanced custom commands to make it easier to extend Nightwatch, and improved support for using Nightwatch programmatically. See writing custom commands docs page.
⚡️ The Developer Guide docs also have been updated.
🔄 Changelog:
- ➕ Added improved http request retry mechanism and better error reporting for api commands – a04162c
- ➕ Added enhancements to assist in writing of custom commands – c977b16
- ➕ Added
abortOnElementLocateError
global property to control if the testcase in progress should continue in the event of an element locate error (as a result of a click, getText, etc. command) – #2459 - 🛠 Fixed an issue with merging the config settings when passed programmatically – #2483
- 🛠 Fixed an issue where transport was set incorrectly for Chrome when using
chromeOptions.w3c:true
– d56a9db 🛠 Fixed an issue where the locator strategy was not taken into account when specifying first argument in a waitFor* command – #2446
🛠 Fixed #2458 - implemented proper handling of 5xx server errors sometimes encountered during element commands, usually when using cloud testing services or selenium grid
-
v1.3.8 Changes
July 25, 2020- 🛠 Fixed #2458 - implemented proper handling of 5xx server errors sometimes encountered during element commands, usually when using cloud testing services or selenium grid
-
v1.3.7 Changes
July 22, 2020Added new setting
test_workers.node_options
to enable passing node options to individual test worker processes.
Usage:This will pass all of
process.execArgv
:test_workers: {enabled: true,// automatically compute the number of workers based on CPU coresworkers: 'auto',// pass node arguments to individual workers (all of the process.execArgv)node_options: 'inherit',},
This will pass only the specified cli options:
test_workers: {enabled: true,workers: 'auto',// selectively pass node arguments to individual worker processesnode_options: ['--inspect']},
-
v1.3.6 Changes
May 30, 2020- 🛠 Fixed #2417 -
--filter
argument was ignored if both--filter
and--skiptags
are set - 🛠 Fixed - an issue occurring when using
--filter
argument and an emptysrc_folders
setting - b2c2daa - ➕ Added - improved jUnit reporting for assertions in before/after test hooks - 0cc3627
- ➕ Added - stripping of ansi control characters in jUnit xml reports and improved
currentTest
api property - 0cc3627 - 🛠 Fixed - an issue with running tests using the
describe
interface more than once in the same test run - cb1221d - 🛠 Fixed - a problem with using the global
--timeout
argument in some cases - 1b3abcd - 🛠 Fixed - an issue where a failed assertion inside the
after
test hook would have blocked the test run - 1e11032 - 🛠 Fixed - displaying the correct error message in case of using an unknown api assertion (e.g. due to a typo) - abaaaf8
- 🛠 Fixed - remove the
isVisible
workaround for Safari lower than v12 - c8e34b2
- 🛠 Fixed #2417 -
-
v1.3.5 Changes
May 03, 2020- 🛠 Fixed #2365 - Removed deprecated
optimist
package and updated implementation of cli help display; - 🛠 Fixed an issue with specifying a non-default port to geckodriver and chromedriver;
- 🛠 Fixed a potential issue when not specifying a callback to some element protocol actions;
- 🛠 Fixed #2375 - remove incorrect cli args from safaridriver.
- 🛠 Fixed #2365 - Removed deprecated