Gathering detailed insights and metrics for jest-stare-2
Gathering detailed insights and metrics for jest-stare-2
Gathering detailed insights and metrics for jest-stare-2
Gathering detailed insights and metrics for jest-stare-2
jest-stare
jest html reporter (results processor) to view HTML jest results, save raw JSON, and invoke multiple reporters
bespoken-jest-stare
jest html reporter (results processor) to view HTML jest results, save raw JSON, and invoke multiple reporters
jest-sonar-reporter
A Sonar test reporter for Jest.
@jest/types
This package contains shared types of Jest's packages.
npm install jest-stare-2
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
263 Stars
1,407 Commits
31 Forks
7 Watching
18 Branches
14 Contributors
Updated on 02 Aug 2024
TypeScript (94.27%)
HTML (3.45%)
CSS (2.18%)
JavaScript (0.1%)
Cumulative downloads
Total Downloads
Last day
-42.9%
4
Compared to previous day
Last week
-48.9%
24
Compared to previous week
Last month
27.9%
197
Compared to previous month
Last year
302.8%
1,998
Compared to previous year
16
This is a Jest HTML reporter. It takes summary test results from jest and parses them into an HTML file for improved readability and filtering.
Run tests or a test with jest and specify jest-stare
on the --reporters
option:
jest --reporters default jest-stare
jest --testResultsProcessor=jest-stare
Alternatively, in your jest
config within package.json
set reporters
to jest-stare
:
"reporters": ["default", "jest-stare"]
"testResultsProcessor": "./node_modules/jest-stare"
jest-stare
when used as a reporter updates the HTML report on each completed test run. You can use this to view test output
that is incomplete (before each test suite completes). Refresh your browser to see new tests as each suite completes.
By default, after a report is generated, output will go to ./jest-stare
and will contain:
index.html
- html reportjest-results.json
- raw jest json data/js
- javascript render files/css
- css stylingsYou can configure custom reporters by passing the jest-stare
config as a second argument:
1 "reporters": [ 2 "default", 3 [ 4 "jest-stare", 5 { 6 "resultDir": "results/jest-stare", 7 "reportTitle": "jest-stare!", 8 "additionalResultsProcessors": [ 9 "jest-junit" 10 ], 11 "coverageLink": "../../coverage/lcov-report/index.html", 12 "jestStareConfigJson": "jest-stare.json", 13 "jestGlobalConfigJson": "globalStuff.json" 14 } 15 ] 16 ]
Note:
testResultsProcessor
will not use config options specified in the way above
Or, do so by adding a jest-stare
object to your package.json, for example:
1jest-stare: { 2 ... 3}
You can also configure each option via environmental variables instead. Environmental variables take precedence over values in package.json. CLI options take precedence of environmental variables and configuration.
Within the configuration object you can specify the following fields:
Field | Environmental Variable | Default | Description | Example |
---|---|---|---|---|
resultDir | JEST_STARE_RESULT_DIR | jest-stare | set the results directory | "resultDir": "results/jest-stare" |
resultJson | JEST_STARE_RESULT_JSON | jest-results.json | indicate the raw JSON results file name | "resultJson": "data.json" |
resultHtml | JEST_STARE_RESULT_HTML | index.html | indicate the main html file name | "resultHtml": "main.html" |
log | JEST_STARE_LOG | true | specify whether or not jest-stare should log to the console | "log": false |
jestStareConfigJson | JEST_STARE_CONFIG_JSON | undefined | request to save jest-stare config raw JSON results in the file name | "jestStareConfigJson": "jest-stare-config.json" |
jestGlobalConfigJson | JEST_STARE_GLOBAL_CONFIG_JSON | undefined | request to save global config results in the file name | "jestGlobalConfigJson": "global-config.json" |
report | JEST_STARE_REPORT | undefined | boolean, set to false to suppress creating a HTML report (JSON only retained) | "report": false |
reportTitle | JEST_STARE_REPORT_TITLE | jest-stare! | string, indicate the title of the report | "reportTitle": "my title" |
reportHeadline | JEST_STARE_REPORT_HEADLINE | jest-stare | string, indicate the headline of the report | "reportHeadline": "my headline" |
reportSummary | JEST_STARE_REPORT_SUMMARY | undefined | boolean, shows the report summary | "reportSummary": true |
additionalResultsProcessors | JEST_STARE_ADDITIONAL_RESULTS_PROCESSORS | undefined | add additional test result processors to produce multiple report | "additionalResultsProcessors": ["jest-junit"] |
coverageLink | JEST_STARE_COVERAGE_LINK | undefined | link to coverage report if available | "coverageLink": "../../coverage/lcov-report/index.html" |
disableCharts | JEST_STARE_DISABLE_CHARTS | undefined | hide the doughnut charts in the HTML report | "disableCharts": true |
hidePassing | JEST_STARE_HIDE_PASSING | undefined | hide passing tests in the report on page load | "hidePassing": true |
hideFailing | JEST_STARE_HIDE_FAILING | undefined | hide failing tests in the report on page load | "hideFailing": true |
hidePending | JEST_STARE_HIDE_PENDING | undefined | hide pending tests in the report on page load | "hidePending": true |
You can programmatically invoke jest-stare and provide jest response data via:
1// require jest-stare 2const processor = require("jest-stare"); 3 4// load some jest results JSON data 5const simplePassingTests = require("../__tests__/__resources__/simplePassingTests.json"); 6 7// call jest-stare processor, passing a first parm of the jest json results, 8// and optionally a second parm of jest-stare config 9processor(simplePassingTests, {log: false, resultDir: __dirname + "/output"});
Use the jest-stare
CLI to create or recreate an HTML report. You only need to supply an input JSON
file containing the jest test results.
You can invoke jest-stare
as a CLI after installing globally via npm install -g jest-stare
.
Or if jest-stare is a local dependency you can invoke the CLI via npx jest-stare...
Assuming that you have a relative file to your current location in a folder "data" and "simplePassingTests.json" contains saved JSON output from a jest test invocation, you can run the CLI providing a single positional input jest JSON file:
jest-stare data/simplePassingTests.json
Optionally you can control where the report will be stored using a second positional:
jest-stare data/simplePassingTests.json c:/users/myId/desktop/output
The command response takes a form of:
jest-stare was called with programmatic config
** jest-stare: wrote output report to c:/users/myId/desktop/output/index.html **
Because jest-stare writes *.js files when generating a report, you may get an infinite loop when using
jest-stare
and jest --watch
. Samples of the problem are documented here:
To get around this problem, consider excluding jest-stare
*.js files from watch via something like this:
1 "watchPathIgnorePatterns": [ 2 ".*jest-stare.*\\.js" 3 ],
See contributing.
Thanks to dogboydog and others for additions!
This project is based on:
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
8 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 1
Details
Reason
Found 0/8 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
security policy file not detected
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2024-11-25
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