What's new with Nightwatch v2?



Nightwatch's underlying architecture has been completely redesigned by the Nightwatch team to improve cross-browser integration and DOM element handling. Nightwatch also runs faster tests. It now uses the Selenium Webdriver bindings to Node.js.

These are the top features and enhancements that make Nightwatch even more powerful than ever:

Support for Actions API

Automate complex gestures with the new API user actions (via the existing .perform() command).

Expanded automatic command retries

Nightwatch will attempt to retry failed element commands, such as when click encounters errors such as element click interception.

Locators for relative elements

Nightwatch automatically includes the new Selenium 4 relative locators. It also enhances the existing locators via Selenium By() API.

Support for file uploads built-in

Nightwatch uploading files can be difficult, but Nightwatch v2 comes with a built-in command that works with the fileDetectorAPI.

Extended Capabilities Support

While the nightwatch.conf.js configuration file will continue to be the primary method of defining capabilities, all capabilities objects created using the Selenium CapabilitiesAPI are supported in v2.

Chrome: Setting network conditions

When working with browser automation, manipulating network conditions is an often needed feature. v2 supports this feature for Chrome and Edge at the beginning.

Support for Devtools Protocol

Nightwatch can now run Chrome DevTools commands. Chrome DevTools Protocol provides tools for inspecting, diagnosing, debugging, profiling, and instrumenting Chromium-based browsers such as Chrome or Edge.

Ready for Webdriver BiDi

The most recent development in Selenium is the BiDirectional WebDriver Protocol. These APIs allow you to receive Javascript or console error messages directly from your browser. It will be available in Nightwatch as soon as possible. The Selenium website will keep you updated on its progress.

Many new command APIs

Nightwatch v2 will also include a new API,.ensure assert, which will mirror the Selenium till APIs, global elements(), expect() and by() and browser objects. This will improve the experience of writing tests, as well as provide greater flexibility.

Test runner improvements

Nightwatch v2 will also include some enhancements to the test runner such as the ability to rerun failed tests and better support for parallel execution.

This list is not exhaustive and Nightwatch v2 has a host of new updates. Visit nightwatch.org to learn more and upgrade to the latest version.

Nightwatch

Nightwatch was released in the first quarter of 2014. It was designed to be a complete, integrated framework that engineers could use to quickly create end-to-end testing and requires minimal configuration and maintenance.


Comments

Post a Comment

Popular posts from this blog

Cross Browser Visual Testing on Real Mobile Devices

Image
We are proud to announce that Percy, the only visual testing platform, supports cross-browser testing on real, physical mobile devices.   We're starting with iOS on Safari, and Chrome on Android. More combinations will be added soon.   You can test on mobile devices by upgrading your plan to Percy Mobile or booking a demo  to experience it in action. Percy's new mobile plan announced A separate Percy Mobile plan is also being launched.   To use mobile browsers, you will need to upgrade.   All Percy Mobile customers have access to Safari on iPhone (Beta) and Chrome on Android(Beta).   For more information , please visit our pricing page. Mobile browsers can be turned on You can activate mobile browsers by either one of these two methods if you've purchased the Percy Desktop & Mobile Plan: Page Settings : This page allows you to change your browser coverage for Percy projects. Turning on mobile browsers from the browser management page Project s...
Read more

Targeting the layers – Test automation strategy paradigm

Image
Why is test automation strategy so important? My experience has shown that software teams can have different automation strategies, while others may have no strategy at all.   It is a good idea to have an automation strategy in place for your software development team.   A test automation strategy will help testers work more effectively together. Richard Bradshaw's automation strategy was a great example of this.   To make the information more widely available, I decided to post it as a blog entry. The test pyramid is a great test automation strategy. Mike Cohn introduced the test pyramid, describing how different teams have been performing the test automation in the software industry.   The test pyramid was not intended to be used for test automation.   Companies and teams have started to use the test pyramid as an automated strategy. This is wrong. It is crucial to testability All testing efforts must be based on testability.   Teams can easily test the s...
Read more