Skip to content

@beatfactor beatfactor released this Sep 1, 2019 · 2 commits to master since this release

  • Added - new configuration settings to for fine tuning the Webdriver server process:
  • status_poll_interval - Interval (in ms) to use between status ping checks when checking if the Webdriver server is up and running
  • max_status_poll_tries - Maximum number of ping status check attempts when checking if the Webdriver server is up and running before returning a timeout error.
  • process_create_timeout - The entire time (in ms) to wait for the Node.js process to be created and running (default is 2 min), including spawning the child process and checking the status

More details

Assets 2

@beatfactor beatfactor released this Aug 12, 2019 · 22 commits to master since this release

New commands

Added several new commands in-line with the W3C Webdriver API:

Improvements

  • waitForElementVisible doesn't throw an error anymore if the element cannot be found - #2148
  • Added W3C Webdriver API compatibility support for .timeouts() command;
  • Added suppressNotFoundErrors option for element selector properties to enable suppressing NoSuchElement errors when element is not found for commands such as .click() or .getText() etc.

Fixes

  • Fixed #2155 - an issue with page object element selectors
  • Fixed #2165 - an issue with page object relative urls
  • Fixed #1301 - an issue with using .perform() with async callback
  • Fixed #2168 - setWindowSize for geckodriver
Assets 2
Aug 12, 2019
1.2.0

@beatfactor beatfactor released this Jun 30, 2019 · 49 commits to master since this release

  • Fixed #2141 - .verify assertions not working correctly
Assets 2

@beatfactor beatfactor released this Jun 10, 2019 · 54 commits to master since this release

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

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
  }
}
Assets 2

@beatfactor beatfactor released this May 23, 2019 · 61 commits to master since this release

  • 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
Assets 2

@beatfactor beatfactor released this May 20, 2019 · 68 commits to master since this release

  • 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)
Assets 2
Pre-release

@beatfactor beatfactor released this May 16, 2019 · 74 commits to master since this release

  • 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 = client.page.home();
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.

Assets 2
Pre-release

@beatfactor beatfactor released this May 6, 2019 · 85 commits to master since this release

  • 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).
Assets 2
Pre-release

@beatfactor beatfactor released this Apr 28, 2019 · 90 commits to master since this release

  • Fixed #2077 - an issue with nested page objects
Assets 2
You can’t perform that action at this time.