Running Your First Test With NightWatchJS

Posted by Harita Ravindranath | December 11, 2020
Automation • JavaScript •

140310 Views | 17 Min Read

Running-First-Test-With-NightWatchJS

In the world of automation testing, Selenium continues to be the most sought after tool. With shorter development cycles and faster releases backed by Agile and DevOps, companies are keen on adopting the right automation testing strategy on par with the development and ensure a high-quality end product. Speeding up automation testing means choosing a plan that aids in handling repetitive work and optimizing tasks with minimal maintenance and effort. And herein lies the importance of implementing the right test automation framework.

Various test automation frameworks are available in the market to choose from. Nightwatch.js is one such well-favored JavaScript-based framework since its release in 2014. This blog will be your guide to everything you need to know to kickstart your journey in Nightwatch.js automation.

Starting with a brief overview, our primary focus in this Nightwatch.js tutorial would be setting up and configuration of Nightwatch.js into your system. And by the end, you will be able to write your first test in Nightwatch.js Selenium.

Let’s get started!

What Is Nightwatch.js?

Nightwatch.js is an open-source automated testing framework for browser-based web applications and websites. It is written in Node.js runtime and uses the W3C WebDriver API (formerly Selenium WebDriver) for interacting with various browsers to perform commands and assertions on DOM elements.

Why Is Nightwatch.js So Popular?

The reason behind Nightwatch.js popularity is its out of the box features. Some of the noteworthy features that make Nightwatch.js so popular are:

  1. Easy To Use – with a clean and simple syntax, code can be written swiftly and efficiently.
  2. In-Built Test Runner – comes with an inbuilt command-line test runner suite with Grunt support for executing Selenium automated tests.
  3. Page Object Model – supports CSS and XPath locators making browser automation more manageable.
  4. Flexibility – enables unit, integration as well as end-to-end testing.
  5. Selenium Server Support – it can automatically control the standalone Selenium server or various browser web drivers.
  6. Integrations – provides a single integrated solution for application testing, eliminating the dependency on third-party software.
  7. Support For Cloud Services – compatible with cloud-based testing platforms like LambdaTest.
  8. Continuous Integration – supports software like Jenkins, TeamCity, etc., assisting developers in continuously building and testing software.

Do check out the Best JavaScript Testing Frameworks!

Nightwatch.js Installation & Local Set Up

It is time to proceed with the installation and environment set-up for Nightwatch.js automation. We will be going step by step from the beginning. But, before installing Nightwatch.js, make sure your system is pre-equipped with the following.

Prerequisites:

a) Java

Check whether Java is already installed in your system using the following command:

java-version

If not, install the latest JDK appropriate to your machine from here.

b) Node.js & NPM

Check whether Node.js is already installed in your system using the following command:

nodejs

If not, install the latest LTS version from here.

Note: NPM will be installed along with Node.js. So no need for separate installation.
After installation, verify the version of Node.js and npm using these commands:

Nodejs1

c) Visual Studio Code

Here, we are using Visual Studio Code as the IDE. You can choose any other IDE of your choice.

If not already installed, you may download VSC from here.

Installing Nightwatch.js & Project Setup

Now let’s proceed with Nightwatch.js installation and basic project configuration. As promised, we will go step by step.

Step 1: Create a folder for your project in the desired location in your system. Open the folder in your IDE.

Step 2: Now, let us initialize our project with the package.json file.

  • Open the terminal in Visual Studio Code.
  • Verify that it is pointing to the project folder location.
  • Give the command:

    npm init

  • You will be asked to fill in project details. You may fill them or leave them blank as of now.

    fill project details

  • You will also notice the package.json file is created in your project folder, containing all the project configuration details.

Tip: Save some time by using the following command in order to generate a default package.json file without any questions being asked.

npm init -y

Here y stands for “yes”.

  • We have successfully created the package.json file.
  • package json file

Step 3: Let’s install Nightwatch.js to our project.

npm install --save-dev nightwatch

This command will add the “node_modules” folder in your directory and download Nightwatch.js to save it as devDependency in package.json.

You will also notice that the “package-lock.json” file has been created as well. This file is used to lock all the dependencies with the version number so that it will be easier to set up the code in another system.

Tip: You may also install Nightwatch.js globally so that it is accessible for all the projects located anywhere within the system.

Here g stands for “global”.

Step 4: Now let us install our browser web driver.

a) ChromeDriver

b) GeckoDriver (Firefox)

Or why not install them all in one go?

Tip: Alternatively, we can combine steps 4 and 5 into a single step. Use the command:

It is to be noted that, while the Selenium Server was required with older Nightwatch versions (v0.9 and prior), starting with version 1.0 Selenium is no longer necessary.

The setup is now completed! Let’s run some demo tests now!

Running A Demo Test

Do you know Nightwatch.js comes with some sample tests? Shall we try running that? That’s what this section of our Nightwatch.js tutorial is all about.

Let us begin-

Step 1: Go to the folder “node_modules/nightwatch/examples/tests/”.

Step 2: Under the ‘tests’ folder, you can find some sample tests.

nightwath folders

Step 3: Let us run the first sample test “ecosia.js”.

ecosiajs sample tests

This is a simple, straightforward program which-

  1. Launches the default browser
  2. Opens the search engine “Ecosia”
  3. Inputs “nightwatch” in search field
  4. Verifies the search result.

Let’s go for it!

Step 4: In the terminal run the command:

Here, “./node_modules/.bin/nightwatch” represents the path of nightwatch.js executable.

“node_modules/nightwatch/examples/tests/ecosia.js” gives the path of the test file.

Step 5: The code gets executed, and the test starts running. Default browser will get launched, and the test gets executed successfully.

NightwatchJS gets executed

Step 6: Observe the test run result in your terminal.

test run results in terminal

Congrats! Nightwatch is now successfully configured in your system.

Nightwatch.js Tutorial For Test Automation Beginners – With Examples

Writing Your First Nightwatch.js Automation Test Script

In the previous section, we were able to run a demo test successfully. But we need to write our own scripts, don’t we?

Now that we have got a basic hand-on, it’s time to get our hands dirty. In this session, we will be writing and running our very first test file using Nightwatch.js automation. Let’s check out the configurations that need to be done.

Configurations

Our goal is to run our test files using the “npm test” command from the project’s base directory. Also, we are setting Chrome as our default browser in the example. But feel free to use the browser of your choice.

Now let’s start step by step.

Step 1: Let us create two folders in our root directory – “tests” for keeping test files and “reports” where reports will get stored after each test run.

(You can provide any folder name of your choice. However, it should be properly mapped in the nightwatch.json file about which we will discuss in step 3.)

Step 2: In your package.json file, replace “scripts – test” to “nightwatch”.

Step 3: In root, create a “nightwatch.json” file. Paste the following snippet.

The “nightwatch.json” is the configuration file which the nightwatch test runner binary expects.

Let’s have a close look into the above code structure of “nightwatch.json”.

  • src_folders: indicates the location that contains the test suites. You can also give an array of folders. If not specified, we should pass the test location inline as the second argument to the test runner, as we did in our demo test.
  • output_folder: indicates the location where test reports get saved, i.e., JUnit report files, XML reports, test logs, selenium log, screenshots, video logs, network logs, etc.
  • webdriver: an object containing WebDriver related configuration options.
    • start_process: a boolean value that indicates that, once we start our test, the nightwatch will automatically start/stop the webdriver instance in the background as a child process.
    • server_path: Here, we are giving the path of the chrome driver executable. Only useful if start_process is enabled.
    • host: We are using localhost for running our test. Mainly needed when the WebDriver service is running on a different machine.
    • port: The port number on which the WebDriver service will listen and/or on which Nightwatch will attempt to connect.
  • test-settings: Defines the browser we want to use.

You may also create “nightwatch.conf.js” for configuration. If both these files are present in the project, the nightwatch.conf.js file will be given more precedence over nightwatch.json.

Step 4: Configurations are done. Now let us write our first test.

Subscribe to Coding Jag and get the best news around the testing world delivered to your inbox every Thursday morning.

Writing Nightwatch.js Automation Tests?

We have already created a “tests” folder. Now we will be creating test files inside this folder. Each file inside it will be loaded as a test suite by the Nightwatch test runner. Let’s start!

Step 1: Create a test file and name it as – testfile1.js

Step 2: Let’s create the test structure.

Step 3: Inside each file, the test runner will look for different keys that are exported. The key is basically the test case name. Each key is mapped to a function in which the browser instance will be passed as an argument.

Step 4: Inside this function, we write our test code. Let’s see the snippet below:

Here we are trying to launch Google and verify that the title and URL of the output page match the expected result. Simple and straightforward.

Let’s understand the code now.

  • url() – navigate to a specific URL.
  • urlContains() – checks if the current URL contains the given value.
  • title() – checks if the page title equals the given value.
  • pause() – suspends the test for the given time in milliseconds.
  • assert – when an assertion fails, the test ends, skipping all other assertions.

Step 5: Now it’s time to run the code. Go to the terminal. Verify you are in the project base directory. Give the following command:

The test will start running, and the browser will be launched.

Browser Launch

Test Suite

All assertions are passed. Congrats, you have successfully written your first test code!

Step 6: Check out the reports generated in your “reports” folder.

In this sample test case, we have explored only a few commands. Feel free to explore more by visiting the official API documentation.

Parallel Testing Using Nightwatch.js

We can enable parallel testing in Nightwatch.js using a quick and simple configuration in our “nightwatch.json” file.

By enabling “test_workers” to be true, we are enabling parallel testing. Let’s look into the steps now:

Step 1: Add the above code in your “nightwatch.json” file.

Step 2: Create an additional test file in the “tests” folder for running in parallel with the first test file.

Step 3: In the Terminal, give the command:

Step 4: Two browser windows get launched, executing the test files in parallel.

Step 5: After execution, observe the reports generated.

Cross Browser Testing & Test Coverage Across Devices

We came to a detailed understanding of Nightwatch.js setup and test execution in our local machine through the previous sections of this Nightwatch.js tutorial. We have also created our first test file, did parallel testing, and generated reports.

But to stay ahead in a highly competitive market, it is our duty as testers to ensure the quality of the application in all scenarios, i.e, the app should behave as expected across all platforms, browsers, and devices without crashing. This is where the terms test coverage and cross browser testing comes into the picture.

To leverage the test coverage, cloud-based solutions are widely adopted by companies due to various merits like:

  • Low investment cost compared to buying the infrastructure.
  • Provides access to hundreds of device and platform combinations.
  • Extends supports to old and outdated browser versions and OS devices
  • No set-up or installation, or maintenance needs to be done locally.
  • Scalability.

When it comes to distributed test execution, Selenium Grid is always a good call. It has the capability to run test cases on different versions of browsers and different operating systems simultaneously.

Hence, using a combination of Selenium Grid with the right cloud-based solution provider for cross browser compatibility testing is the optimum strategy that you can deploy to assure quality. Now let us see how we can perform automated browser testing using a remote Selenium Grid provided by LambdaTest.

Test Execution With Selenium Grid Cloud

LambdaTest is trusted by 100,000 companies worldwide as a reliable online Selenium Grid provider to fulfill their cross browser testing needs. LambdaTest provides you access to 2000+ browsers for both mobile and desktop to help you gain the maximum test coverage during the automated browser testing.

You can even leverage parallel testing with Selenium automation testing, along with our open Selenium API to help you extract test reports of your Selenium script execution over LambdaTest, effortlessly.

Now, let us try and execute the above test case using the remote WebDriver for LambdaTest’s Selenium Grid cloud. You can achieve this using a few simple and easy steps with few changes in your existing script for local setup. Let’s look into it step by step.

Step 1: We need to pass browser and environment details to the LambdaTest Selenium Grid via the desired capabilities class. Unlike in local setup, now we have the flexibility to choose the precise settings we want.

There is a helpful tool provided by LambdaTest to generate desired capabilities based on the combination we want. Visit LambdaTest Desired Capabilities page to generate them.

LambdaTest Desired Capabilities

In this case, the desired capabilities class in nightwatch.json will look like this:

Step 2: Now you need to fetch your unique Access token and username.

Step 3: Log in to LambdaTest or create your account. A unique access token will be created for you.
This token is used as a secret key to link your local scripts with the LambdaTest platform.

There are 3 ways to find it:

  1. If already logged in, from the Capabilities generator page, you can fetch it.

    Capabilities generator

  2. You can also fetch the details from the Profile section.

    Access Token

  3. Or from the Automation dashboard page, by clicking the key button in the top right corner.

    LambdaTest Automation Dashboard

Step 4: Paste the following snippet in your nightwatch.conf.js file. (If not created already, you can create this file in your root)

Here we are declaring the user configuration for an access key, username, host, and port for the test.

Step 5: Configure your nightwatch.json file. Since we are using LambdaTest, why don’t we go for cross browser testing across multiple platforms?

In this code, we are configuring for the script to run across 3 browsers – Chrome, Firefox, and Safari on 2 different platforms – Windows and macOS.

Check out the code below and let’s look into the required changes and additions to be made on your existing file:

  1. Pass your Access Token and User details.
  2. Provide Desired Capabilities for all the browsers.
  3. Set the Hostname corresponding to LambdaTest.
  4. Optionally we have also enabled report formats like video recording, console, network logs, etc., to be true.

A more detailed explanation is given below but feel free to skip to Step 6.

We have used additional parameters to configure “nightwatch.json” for cloud-based cross browser testing. They are:

  • selenium – an object containing Selenium Server related configuration options. If “selenium” is not used, “webdriver” options should be set instead (as we did in our local set up). Starting with Nightwatch 1.0, Selenium is only required when testing against a grid setup or a cloud testing service such as LambdaTest.
    • cli_args – list of CLI args to be passed to Selenium process, basically browser drivers.
  • test_settings:
    • silent – whether to show the extended HTTP traffic command logs from the WebDriver or Selenium server.
    • desiredCapabilities – an object to specify browser name for instance along with other capabilities.
    • username and access_key – Usually only needed for cloud testing Selenium services. In case the server requires credentials these values will be used to compute the Authorization header.

Step 6: In package.json, change the “ scripts – test” argument value.

This is important as it is here where we are specifying the browsers where we need to run our test.

Step 7: Execute the test.

npm test

The code starts running and logs can be observed in the terminal.

nightwatchJS code execution

To observe live running status go to your Automation dashboard in LambdaTest.

Test Automation dashboard

We can analyze individual test run reports from Automation Logs.

Automation Logs

We have successfully run our test cases using an automated cross browser testing solution provided by LambdaTest through a hassle-free experience!

Conclusion

Nightwatch.js is one of the most in-demand Selenium Javascript-based automation testing frameworks known for its simplicity and integrated features. In this blog, we have looked into Nightwatch.js installation and setup, along with a detailed walkthrough on configurations. Additionally, we have also leveraged our automation testing by adopting test coverage concepts and cross browser testing.

Hopefully, this Nightwatch.js tutorial will enable you to kickstart your journey in Nightwatch.js automation. If you wish to optimize your web application quality by unlocking coverage in a wider variety of platforms or browsers or versions, feel free to explore the LambdaTest platform.

Happy testing!

Frequently Asked Questions

How do you run the Nightwatch test?

There are some basic prerequisites that are required to get started with this Nightwatch JS tutorial for testing with Selenium and JavaScript.

  1. Node.js
  2. Node Package Manager (npm)
  3. Java – SDK
  4. Selenium Server
  5. Chrome Driver

Nightwatch.js offers an in-built test runner that expects a JSON configuration file to be passed. The default configuration file is nightwatch.json, which should be present in the project’s root directory. Alternatively, the nightwatch.conf.js configuration file can also be used and will be loaded from the root directory of the project for Nightwatch testing.

Continued at https://www.lambdatest.com/blog/nightwatch-js-tutorial-for-test-automation-beginners/

How do I use Nightwatch JS?

Nightwatch.js works by communicating with WebDrivers of different browsers, like ChromeDriver for Chrome or GeckoDriver for Firefox. Nightwatch.js offers an in-built test runner that expects a JSON configuration file to be passed. The default configuration file is nightwatch.json, which should be present in the project’s root directory.

Alternatively, the nightwatch.conf.js configuration file can also be used and will be loaded from the root directory of the project for Nightwatch testing.

Is Nightwatch open source?

Yes. Nightwatch.js is an open-source automated testing framework for browser-based web applications and websites. It is written in Node.js runtime and uses the W3C WebDriver API (formerly Selenium WebDriver) for interacting with various browsers to perform commands and assertions on DOM elements.

What is end to end testing?

The technical definition of end to end testing is – a type of testing to ensure that the behavioral flow of an application works as expected by performing complete, thorough testing from the beginning to end of the product-user interaction to realize any dependency or flaw in the workflow of the application.

Written by

Related Articles

TDD vs. BDD: Choosing The Right Framework

111029 Views | 19 Min Min Read

Leave a Reply

Your email address will not be published. Required fields are marked *