All Versions
Latest Version
Avg Release Cycle
23 days
Latest Release
941 days ago

Changelog History
Page 3

  • v1.1.13 Changes

    June 30, 2019
    • ๐Ÿ›  Fixed #2141 - .verify assertions not working correctly
  • v1.1.12 Changes

    June 10, 2019
    • ๐Ÿ›  Fixed #2123 - the .init() command was broken starting with v1.1.8
    • ๐Ÿ›  Fixed #2118 - Set default POST body to be empty JSON in order to use chromedriver 75
      If using Chromedriver 75 you need to set the following capabilities in your config:

      desiredCapabilities : { browserName : 'chrome', chromeOptions: { w3c: false } }

    0๏ธโƒฃ Chromedriver 75 has W3C Webdriver protocol enabled by default, however we recommend sticking to the JSONWire for now as some endpoints aren't implemented yet (e.g. /displayed). If using the default w3c webdriver mode, make sure to adjust the config like so:

    { capabilities: { browserName : 'chrome', }, webdriver: { use\_legacy\_jsonwire: false } }
  • v1.1.11 Changes

    May 23, 2019
    • ๐Ÿ›  Fixed element commands (e.g. getText) not being able to be used with ES6 async/await
    • ๐Ÿ›  Fixed an issue with using assert.elementPresent/elementNotPresent with W3C Webdriver
    • ๐Ÿ›  Fixed #2104 - an issue with waitForElement commands being called with a custom message
    • ๐Ÿ›  Fixed #2101 - a problem with loading custom commands located in sub-folders of the initial source folder(s)
    • ๐Ÿ›  Fixed #2099 - an issue with creating custom commands by extending built-in waitForElement commands
  • v1.1.10 Changes

    May 20, 2019
    • ๐Ÿ›  Fixed #2087 - an exception occured when creating screenshots in some cases
    • โž• Added support for Firefox to be used in parallel environment runs (i.e. multiple browsers)
  • v1.1.9 Changes

    May 16, 2019
    • ๐Ÿ›  Fixed #2091 - an issue with waitForElementNotPresent causing the test to fail immediately if the element is found, without retrying;
    • โž• Added support for Safari to use W3C Webdriver protocol by default;
    • โž• Added support for using protocol element commands directly on the page object sections:

      const homepage =;const navigation = homepage.section.navigation;navigation.api .elementIdElements('@versionDropdown', 'css selector', 'option', function(result) { console.log('result', result); });

    โœ… Checkout the nightwatch-website-tests example tests also for more usage details.

  • v1.1.8 Changes

    May 06, 2019
    • โž• Added support for ES6 async/await custom commands (such as this example); previously async/await support was limited to testcases;
    • ๐Ÿ›  Fixed error handling for some cases when session was not created in Chrome and the error wasn't reported, unless you were in verbose mode;
    • ๐Ÿ›  Fixed #2079 - a regression which was causing waitForElementNotPresent command to not mark the assertion as failed when the element was still present after the timeout;
    • ๐Ÿ›  Fixed #2018 - calling custom commands on page objects would fail if first argument is an array (e.g. when using execute).
  • v1.1.7 Changes

    April 28, 2019
    • ๐Ÿ›  Fixed #2077 - an issue with nested page objects
  • v1.1.6 Changes

    April 23, 2019
    • ๐Ÿ›  Fixed #1990 - loading of page objects from nested folders
    • โž• Added - support for relative urls in page objects
  • v1.1.5

    April 23, 2019
  • v1.1.4

    April 23, 2019