Gathering detailed insights and metrics for cypress-circleci-reporter
Gathering detailed insights and metrics for cypress-circleci-reporter
Gathering detailed insights and metrics for cypress-circleci-reporter
Gathering detailed insights and metrics for cypress-circleci-reporter
cypress-slack-reporter
A slack reporter for mochawesome reports generated by Cypress or other test frameworks using Mocha, for runs generated on CircleCI
cypress-mochawesome-reporter
Zero config Mochawesome reporter for Cypress with screenshots
cypress-image-snapshot
Cypress bindings for jest-image-snapshot.
cypress-junit-reporter
A JUnit reporter for mocha.
npm install cypress-circleci-reporter
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
44 Stars
37 Commits
5 Forks
2 Watching
19 Branches
2 Contributors
Updated on 12 Nov 2024
TypeScript (78.26%)
JavaScript (21.74%)
Cumulative downloads
Total Downloads
Last day
2.7%
24,136
Compared to previous day
Last week
6.1%
113,329
Compared to previous week
Last month
13.4%
468,758
Compared to previous month
Last year
144.4%
5,051,369
Compared to previous year
2
1
Cypress test reporter for CircleCI based on mocha-junit-reporter. Helps with test parallelization.
1$ npm install cypress-circleci-reporter mocha --save-dev
1$ yarn add cypress-circleci-reporter mocha --dev
After installing the reporter, you'll need to modify your config to use it:
run_cypress_tests:
parallelism: 3 # or any other number that suits your needs
steps:
# some previous steps
- run:
name: Run cypress tests
command: yarn cypress run --spec "$(circleci tests glob "./cypress/integration/**/*.spec.js" | circleci tests split --split-by=timings | paste -sd "," -)" --reporter cypress-circleci-reporter
- store_test_results:
path: test_results
- store_artifacts:
path: test_results
First test run with this config should create and store reports for each test file. These will be used during next runs to determine timings of each test. CircleCI will then split the test files between available containers to speed up the process.
Options can be passed to the reported by adding --reporter-options
parameter to the CLI command.
Example: --reporter cypress-circleci-reporter --reporter-options "resultsDir=./results/cypress,resultFileName=result-[hash]"
Parameter | Default | Effect |
---|---|---|
project | undefined | If you use Cypress' project parameter, this should be set to the same value. |
resultsDir | ./test_results/cypress | Name of the directory that reports will be saved into. |
resultFileName | cypress-[hash] | Name of the file that will be created for each test run. Must include [hash] string as each spec file is processed completely separately during each cypress run execution. |
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Reason
Found 1/15 approved changesets -- 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
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
38 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
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