Gathering detailed insights and metrics for nightwatch-gui
Gathering detailed insights and metrics for nightwatch-gui
npm install nightwatch-gui
Typescript
Module System
Node Version
NPM Version
52.7
Supply Chain
75
Quality
71.3
Maintenance
25
Vulnerability
79.9
License
CSS (74.23%)
JavaScript (24.31%)
HTML (1.47%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
3,663
Last Day
1
Last Week
3
Last Month
25
Last Year
213
9 Stars
49 Commits
2 Forks
3 Watchers
1 Branches
3 Contributors
Updated on Jan 21, 2025
Latest Version
1.2.0
Package Id
nightwatch-gui@1.2.0
Unpacked Size
45.53 MB
Size
11.54 MB
File Count
9,211
NPM Version
6.4.1
Node Version
8.12.0
Cumulative downloads
Total Downloads
Last Day
0%
1
Compared to previous day
Last Week
0%
3
Compared to previous week
Last Month
-19.4%
25
Compared to previous month
Last Year
-19.6%
213
Compared to previous year
A simple, browser based, GUI (Graphical User Interface) to run test cases written in Gherkin to be run with Nightwatch.js thanks to nightwatch-cucumber.
Install the module from the npm registry either globally:
npm install -g nightwatch-gui
or as a dependecy of your project:
npm install --save-dev nightwatch-gui
Then in the main folder of your nightwatch-cucumber project run:
nightwatch-gui
The module assumes the standard nightwatch-cucumber foldering, where the main project folder contains both the nightwatch.conf.js
file and the features
folder containing the test cases written in Gherkin.
If your setup is different, you can customise all the paths in the config
key in the package.json
file:
"config": {
"featuresParentFolder": "", //default current folder
"featuresFolderName": "", //features 'features'
"nightwatchConfigJsFolder": "", //default current folder
"excludeFolders": "['step_definitions']",
}
or, if you don't want to mess up with the package.json
file (for instance because you have installed the module globally), or if you want to manage these settings on a per project basis you can create the file nightwatch-gui-config.json
with the same content of the config
key seen above:
{
"featuresParentFolder": "", //default current folder
"featuresFolderName": "", //features 'features'
"nightwatchConfigJsFolder": "", //default current folder
"excludeFolders": "['step_definitions']"
}
It reads the nightwatch.config.js to get the enviroments defined, and it scrapes the "features" folder to get the features definitions. Then it displays both the environments and the features available on a web page where is possible to select the features to run by a combination of tags, folders and files. Finally it runs nightwatch-cucumber with the selected options.
For any issues: https://github.com/fbedussi/nightwatchGui/issues
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 4/25 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
121 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-17
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More