jest-tap-reporter
v1.9.0
Published
Jest TAP reporter
Downloads
12,111
Readme
jest-tap-reporter
- Outputs valid TAP
- Highlights similar to Jest default reporter, see Mac and VS Code examples
- Highlights line and column of errors
- Shows progress while running tests
Installation
yarn
yarn add --dev jest-tap-reporter
npm
npm install --dev jest-tap-reporter
Usage
Add to your Jest configuration
In package.json
file:
{
"jest": {
"reporters": [
"jest-tap-reporter"
]
}
}
Options
You can add an optional configuration object:
{
"jest": {
"reporters": [
["jest-tap-reporter", {
"logLevel": "ERROR",
"showInternalStackTraces": true,
"filePath": "filename.tap"
}]
]
}
}
Options:
logLevel
- specifies the log level. By default jest-tap-reporter usesINFO
log level, which will log the suite path and a summary at the end of a test run. If you want to reduce the reporting to bare minimum you can set thelogLevel
parameter toERROR
. available log levels are:ERROR
,WARN
,INFO
.filePath
- specifies a file to write the results. If not supplied it will useprocess.stdout
.showHeader
- whether to show starting message on startup, defaults totrue
.showInternalStackTraces
- shows stack traces from "internal" folders, like/node_modules
and/internal
, defaults tofalse
.showProgress
- whether to not show intermediate test result summary while testing is in progress. In general, defaults totrue
. When writing to file or in CI environment, it is forced to befalse
.
Example: writing to file
You can write test results to a file with the following config:
{
"jest": {
"reporters": [
["jest-tap-reporter", {
"logLevel": "ERROR",
"filePath": "test.tap"
}]
],
}
}
License
MIT.