Gathering detailed insights and metrics for vue-cli-plugin-e2e-nightwatch-browserstack
Gathering detailed insights and metrics for vue-cli-plugin-e2e-nightwatch-browserstack
Gathering detailed insights and metrics for vue-cli-plugin-e2e-nightwatch-browserstack
Gathering detailed insights and metrics for vue-cli-plugin-e2e-nightwatch-browserstack
npm install vue-cli-plugin-e2e-nightwatch-browserstack
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (86.74%)
Dockerfile (9.52%)
Shell (3.75%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
3 Stars
117 Commits
5 Branches
2 Contributors
Updated on Sep 09, 2020
Latest Version
4.0.1
Package Id
vue-cli-plugin-e2e-nightwatch-browserstack@4.0.1
Unpacked Size
18.00 kB
Size
7.03 kB
File Count
16
NPM Version
6.14.2
Node Version
12.16.1
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
2
1
5
@vue/cli plugin for automated testing with Vue + Nightwatch + BrowserStack
Note: this depends on @vue/cli-plugin-e2e-nightwatch
From an existing Vue cli application run:
vue add e2e-nightwatch-browserstack
This will install a /browserstack_config
folder
with a nightwatch.conf.js
file
and adds several scripts to the package.json
to run the tests in different browsers.
This differs from npm:vue-cli-plugin-e2e-nightwatch-browserstack
by integrating better with the e2e-nightwatch plugin.
This package assumes that @vue/cli-plugin-e2e-nightwatch
has already been installed.
If you installed this one first, I advise deleting all traces of this and installing the nightwatch plugin first.
As a fallback, if the normal Vue installation does not work, try:
npm install -save-dev vue-cli-plugin-e2e-nightwatch-browserstack
and
vue invoke e2e-nightwatch-browserstack
node_modules
browserstack_config
vue-cli-plugin-e2e-nightwatch-browserstack
from
package.json
test:browserstack
... commands from package.json
.If the expected files are not created (or you installed through npm install),
try vue invoke e2e-nightwatch-browserstack
BROWSERSTACK_USERNAME
and BROWSERSTACK_ACCESS_KEY
are required to be set.
These can be retrieved from your account settings at:
https://www.browserstack.com/accounts/settings
BROWSERSTACK_PROJECT
can be configured to split tests by project.
The default name is "default_project"
This setting is unique and uses an ENV var so CircleCI can build this to the correct project for BrowserStack's Open Source project requirements.
This plugin uses its own Nightwatch config file. It does not inherit from package.json or from any other Nightwatch config files in the root directory.
All BrowserStack and NightwatchJS configurations can be set in the
browserstack_config/nightwatch.conf.js
file.
npm run test:browserstack:chrome
or replace chrome with firefox
, safari
, ie
, android
, ios
--url
flag is used to specify a url. This flag skips the dev server
and passes the url to browserstack as part of the config.
Further Nightwatch commands could change the starting URL, but this is the one which will show up in the Browserstack UI.
asset.elementCount()
is a sample custom-assertion.
Make sure you set the custom assertions path in whichever nightwatch.conf.js
you are using
If you are using a previous version of @vue/cli such as
"@vue/cli-plugin-e2e-nightwatch": "^3.8.0",
which uses a version of Nightwatch
before the Nightwatch CLI was implemented in 1.0.0
, then there will be issues
such as test runner inconsistencies or critical vulnerabilities.
Follow the instructions here. Most of this information will be required to fully understand how Vue plugins work
For committing, you may be required to be logged into docker for changes to the hello-world image.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
Found 0/25 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
11 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
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