Nightwatch v2.0.0-beta.1 is released

[beatfactor]

We're delighted to present the first beta version of Nightwatch v2.0! Upcoming beta releases will incrementally be made available in NPM under the next tag, so in order to install it you'd have to run the following:

npm i nightwatch@next

Over the coming weeks we will also finish updating the documentation website with more pages in the Guide section and documenting the new APIs.

Important Changes

Since the previous alpha release we have only added a few improvements and several fixes. The fixes are mainly concerning working with the new element() api and using cucumber-js.

Improvements

• Added dragAndDrop element command which uses the new Actions API from Selenium – Api commands #2920;
• Added support to use the config file as Promise – feat: config as promise #2896
• Added support to use glob patterns in config for src_folders, page_object_path, custom_commands_path, custom_assertion_path options – added support for glob pattern for path in config #2910;
• Added new webdriver.log_file_name setting to specify the filename where webdriver server logs should be written – 1277601
• Added support to write individual webdriver server logs for each test suite – 1277601
• Added support to define page object commands as an ES6 class – example db03e68;
• Added support to use Selenium WebElement ids as arguments to element commands, such as .click(), e.g.:

// with async
const elements = await browser.findElements('input');
await browser.click(elements[1]);

// with callback
browser.findElements('input', function(result) {
  browser.click(result.value[1]);
});

Fixes

• Reverted getAttribute command to use the W3C endpoint instead of the Selenium atom script - Fixes/update get attribute #2926;
• Fixed an issue where the session was hanging after a failure when using suiteRetries – 1277601

---

This discussion was created from the release v2.0.0-beta.1.

[tim-yao]

Thanks @beatfactor for the cucumber native support. I have tried today and have some questions about the cucumber options. If I want to use those cucumber options like retryor dry-run in test runner option settings, it doesn't work. Seems not all cucumber options supported. That can be a problem for me.

It will be nice to let us use cucumber with all cucumber features. And I can forward cucumber options from nightwatch cli command. Is that on your plan?

[beatfactor]

Thanks @beatfactor for the cucumber native support. I have tried today and have some questions about the cucumber options. If I want to use those cucumber options like retry or dry-run in test runner option settings, it doesn't work. Seems not all cucumber options supported. That can be a problem for me.

It will be nice to let us use cucumber with all cucumber features. And I can forward cucumber options from nightwatch cli command. Is that on your plan?

Not all the cli options are forwarded, but I think you should be able to specify the test_runner options? We can also look into adding more cli arguments to the cucumber cli if needed. Feel free to have a look at the code for the cucumber runner and suggest changes in a PR.

[tim-yao]

Hi @beatfactor , thanks for the link. That helps a lot. I think only listed options are passed to cucumber in https://github.com/nightwatchjs/nightwatch/blob/v2/lib/runner/test-runners/cucumber.js#L134, I definitely can give you a full list which will enable the full support of cucumber options. Also the options like tags, only support being forwarded from cli, not in test runner options. https://github.com/nightwatchjs/nightwatch/blob/v2/lib/runner/test-runners/cucumber.js#L117
What is the best way to suggest a PR? Do we need to follow a process or create an issue first?

[beatfactor]

You can create a new enhancement and describe briefly what would you like us to add. If you can also send a PR for that it would be appreciated, otherwise we'll try to add it in the next beta.

[tim-yao]

@beatfactor I have created an issue #2962. Any thought is welcome. If I can get some clear solution direction, I may create a PR for it. Cheers!

[humphreyn]

Hi @beatfactor ,
First up I would like to give you a big 👍 for adding native cucumber support. We have been using NightwatchJS along with CucumberJS for at least 4 years.

I have a couple of questions though:

1. Does NightwatchJs v2.* support Selenium 4? If not are there any plans for adding it?
2. The additional support for Chrome DevTools is that via Selenium 4 as it too supports using Chrome DevTools

Cheers

[beatfactor]

Hi @beatfactor , First up I would like to give you a big 👍 for adding native cucumber support. We have been using NightwatchJS along with CucumberJS for at least 4 years.

I have a couple of questions though:

1. Does NightwatchJs v2.* support Selenium 4? If not are there any plans for adding it?
2. The additional support for Chrome DevTools is that via Selenium 4 as it too supports using Chrome DevTools

Cheers

Sure, Nightwatch uses the latest selenium-webdriver package for interacting with the browsers and CDP support is done either via the traditional HTTP based methods available via the browser.chrome namespace or via the new WebDriver bidirectional apis, which use Websockets. I'm working on finalizing the docs for v2 which will also have more info on this.