Issue encountered when attempting to run specific Nightwatch.js tests individually

Question

Issue encountered when attempting to run specific Nightwatch.js tests individually

I'm encountering an issue where I can only run individual nightwatchjs tests when using the absolute path of the test script.

For instance, if I execute my test from the following directory;

/Users/darrenharley/Documents/Git/uk-content-parkers/Tests/Functional/tests

using the command;

npm run test:live /Users/darrenharley/Documents/Git/uk-content-parkers/Tests/Functional/tests/current_functionality/gamAds/PAR-5139.js

It runs successfully.

However, I require running this test without relying on my local file structure (as it will eventually be triggered via a Jenkins build so the absolute path cannot be used).

If I try to run the test with the following command;

npm run test:live ./current_functionality/gamAds/PAR-5139.js

It fails and returns the error message;

Error: ENOENT: no such file or directory, stat './current_functionality/gamAds/PAR-5139.js'

Am I making an obvious mistake here?

As a reference, in my nightwatch.conf.js file, I have specified this;

 src_folders: [
    'tests/',
  ],

and in my package.json file, the relevant script is defined as;

"test:live": "nightwatch --config config/nightwatch.conf.js --env live --suiteRetries 3",

Any assistance would be welcome, as I find it frustrating that something so basic is causing such trouble.

Thank you in advance.

javascript nightwatch.js

Answer 1

Answer №1

Initially, the lack of information about your Jenkins job makes it difficult to provide an accurate solution (Where is the NPM command initiated from? What is the project root directory?). It would be advisable to insert a pwd command before executing the NPM call to identify the project root location and adjust the command accordingly.

NOW ...

For your current task, the simplest (and most organized) method involves utilizing NightwatchJS test groups & test tags.

❒ Employing test tags:

module.exports = {
  '@tags': ['PAR-5139', 'live', 'smoke'],
  'This is the PAR-5139 test': function (browser) {
     // > your code here <
  }
};

To implement this logic, update your command to:

npm run test:live -- --tag PAR-5139

(Please ensure to add -- before additional NightwatchJS switches for proper parameter separation between npm command and script parameters.)

❒ Using test groups:

Consider the following tests structure:

tests/
  ├── current_functionality
  |   └── PAR-5139.js
  ├── critical_functionality
  |   └── PAR-5140.js
  |   └── PAR-5141.js
  └── dated_functionality
      ├── OLD-90210.js
      └── OLD-NO7-BRAND-SOUR-MASH.js

To apply the concept, modify your command to:

npm run test:live -- --group current_functionality

.

The group switch accepts multiple folders in one command:

npm run test:live -- --group current_functionality,critical_functionality

!Note: Remember, you can utilize the --skipgroup switch (to exclude certain test folders) or disable specific tests with the 'disabled' attribute set to true:

module.exports = {
  '@disabled': true, // Prevents this test module execution.
  'Skipping this PAR': function (browser) {
    // > your code here <
  }
};

Answer 2

Initially, the lack of information about your Jenkins job makes it difficult to provide an accurate solution (Where is the NPM command initiated from? What is the project root directory?). It would be advisable to insert a pwd command before executing the NPM call to identify the project root location and adjust the command accordingly.

NOW ...

For your current task, the simplest (and most organized) method involves utilizing NightwatchJS test groups & test tags.

❒ Employing test tags:

module.exports = {
  '@tags': ['PAR-5139', 'live', 'smoke'],
  'This is the PAR-5139 test': function (browser) {
     // > your code here <
  }
};

To implement this logic, update your command to:

npm run test:live -- --tag PAR-5139

(Please ensure to add -- before additional NightwatchJS switches for proper parameter separation between npm command and script parameters.)

❒ Using test groups:

Consider the following tests structure:

tests/
  ├── current_functionality
  |   └── PAR-5139.js
  ├── critical_functionality
  |   └── PAR-5140.js
  |   └── PAR-5141.js
  └── dated_functionality
      ├── OLD-90210.js
      └── OLD-NO7-BRAND-SOUR-MASH.js

To apply the concept, modify your command to:

npm run test:live -- --group current_functionality

.

The group switch accepts multiple folders in one command:

npm run test:live -- --group current_functionality,critical_functionality

!Note: Remember, you can utilize the --skipgroup switch (to exclude certain test folders) or disable specific tests with the 'disabled' attribute set to true:

module.exports = {
  '@disabled': true, // Prevents this test module execution.
  'Skipping this PAR': function (browser) {
    // > your code here <
  }
};

Answer 3

Answer №2

The issue lies in the path provided. It is essential for the path to be relative to the root directory. Relative paths are referenced based on the root directory (where the package.json file is located at the top level).

Consider the following directory structure:

root
--tests
----PAR-5139.js
----
--src
--config
----nightwatch.config.json
--package.json

To run the command, use

npm run test:live ./tests/PAR-5139.js

, regardless of whether you execute it from within the tests folder or the root directory.

In your scenario, although the command is executed from the tests folder and the path is specified relative to that folder, the command is searching for the file relative to the root directory rather than the tests folder.

I hope this explanation clarifies things for you. Feel free to reach out if you have any questions.

Answer 4

The issue lies in the path provided. It is essential for the path to be relative to the root directory. Relative paths are referenced based on the root directory (where the package.json file is located at the top level).

Consider the following directory structure:

root
--tests
----PAR-5139.js
----
--src
--config
----nightwatch.config.json
--package.json

To run the command, use

npm run test:live ./tests/PAR-5139.js

, regardless of whether you execute it from within the tests folder or the root directory.

In your scenario, although the command is executed from the tests folder and the path is specified relative to that folder, the command is searching for the file relative to the root directory rather than the tests folder.

I hope this explanation clarifies things for you. Feel free to reach out if you have any questions.

Issue encountered when attempting to run specific Nightwatch.js tests individually

Answer №1

Answer №2

Similar questions

How can I retrieve information from an object using Mongoose queries?

Guide: Passing and reading command line arguments in React JavaScript using npm

Having trouble converting Buffered Byte Array into Image in Browser

Is there a way to handle two separate ajax requests located within different script tags?

Tips for querying orchestrate.io

Oops! We encountered an issue trying to find the "list" view in the views directory

Exploring Nashorn's capabilities in parsing TypeScript

Issue with Node Webpack identifying the "Import" statement

Deleting a child in Three.js: A step-by-step guide

Error: Module not located or Image unable to load in React JS

Solution for handling pointer events in Safari iOS when they are not supported

My Node/Express service seems to be generating a span in the logs, but I am unable to locate my service in the Ja

Retrieving values of objects based on array keys

Building Your Own Array Object in JavaScript

Expand the width of the div by a specified amount with each click

Correctly managing variables in HTML

JavaScript: Update missing values in an array by assigning the average of its neighboring values

Error code E401 is being encountered with npm, indicating either an incorrect password has been provided or the

Generating hidden form fields dynamically with AngularJS

JSON has encountered an unconventional string at position 41 that was not anticipated