Gathering detailed insights and metrics for jest-nunit-reporter
Gathering detailed insights and metrics for jest-nunit-reporter
Gathering detailed insights and metrics for jest-nunit-reporter
Gathering detailed insights and metrics for jest-nunit-reporter
npm install jest-nunit-reporter
Typescript
Module System
Node Version
NPM Version
78.4
Supply Chain
78.6
Quality
74.3
Maintenance
100
Vulnerability
99.6
License
JavaScript (100%)
Total Downloads
1,396,018
Last Day
304
Last Week
5,411
Last Month
38,162
Last Year
468,396
3 Stars
63 Commits
3 Forks
3 Watching
1 Branches
2 Contributors
Minified
Minified + Gzipped
Latest Version
1.3.1
Package Id
jest-nunit-reporter@1.3.1
Size
26.73 kB
NPM Version
3.10.10
Node Version
6.12.0
Publised On
21 Dec 2017
Cumulative downloads
Total Downloads
Last day
-82.5%
304
Compared to previous day
Last week
-45.2%
5,411
Compared to previous week
Last month
-6.6%
38,162
Compared to previous month
Last year
14.9%
468,396
Compared to previous year
2
A NUnit test reporter for Jest.
1$ npm i -D jest-nunit-reporter
In your package.json
file include a "jest"
config section and specify the "testResultsProcessor"
:
1{ 2 "jest": { 3 "testResultsProcessor": "./node_modules/jest-nunit-reporter" 4 } 5}
For your Continuous Integration you can simply do:
1jest --ci --testResultsProcessor="./node_modules/jest-nunit-reporter
The reporter will generate a test-report.xml
file in the project root. If you need to specify a different location(e.g., for a CI server) then set the paths in the package.json
jestNunitReporter
property:
1"jestNunitReporter": { 2 "outputPath": "reports/", 3 "outputFileName": "custom-report.xml", 4}
There are other options for naming test suites:
testSuiteNamePrefix
: Add prefix to test-suites namestestSuiteNameFromAncestors
: Use ancestors root title (describe
)No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 2/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
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
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
56 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-12-23
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