Registry / testing / jest-jenkins-reporter

jest-jenkins-reporter

library1.0.2jsnpmunverified

The `jest-jenkins-reporter` package provides a Jest test results processor designed to generate XML reports compatible with Jenkins's JUnit plugin. As of version 1.0.2, this specific package is no longer actively maintained, with its last publish date being over eight years ago. Its core function is to transform Jest's comprehensive test output into a standardized XML format, which then allows Continuous Integration (CI) servers, particularly Jenkins, to parse and display test results within their dashboards. This reporter operates by creating a static XML file after the test suite completes, rather than offering real-time reporting during execution. The original development team (pilipa-cn) has explicitly stated the project is out of maintenance, directing users to a community-maintained fork. Consequently, this package lacks a regular release cadence and has received no updates for an extended period. Developers are strongly encouraged to use actively maintained alternatives like `@digitalroute/jest-jenkins-reporter` or `jest-junit` for modern Jest setups.

testing devops

npm install jest-jenkins-reporter

github ↗package ↗

INSTALL

IMPORT

SIG · JEST-JENKINS-REPOR

jest-jenkins-reporter

testingjavascriptv1.0.2

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

jest-jenkins-reporter

✓ "testResultsProcessor": "jest-jenkins-reporter"

✗ import { JestJenkinsReporter } from 'jest-jenkins-reporter';

This package is not imported as a JavaScript module; it's specified as a string path in Jest's configuration.

This quickstart demonstrates how to configure `jest-jenkins-reporter` in `package.json` for generating an XML report suitable for Jenkins, alongside a basic Jest test file.

{ "name": "my-jest-project", "version": "1.0.0", "description": "A sample project using jest-jenkins-reporter.", "main": "index.js", "scripts": { "test": "jest", "test-jenkins": "NODE_ENV=test jest --colors" }, "jest": { "testResultsProcessor": "jest-jenkins-reporter", "collectCoverage": true }, "jestSonar": { "reportPath": "./reports", "reportFile": "jest-report.xml", "indent": 4 }, "keywords": [], "author": "", "license": "MIT", "devDependencies": { "jest": "^29.0.0", "jest-jenkins-reporter": "^1.0.2" } } // example.test.js describe('Example Test Suite', () => { test('should add two numbers correctly', () => { expect(1 + 2).toBe(3); }); test('should subtract two numbers correctly', () => { expect(5 - 2).toBe(3); }); });

Debug

Known issues

breakingThis `jest-jenkins-reporter` package (pilipa-cn) is no longer maintained and has not received updates for over 8 years. It is officially abandoned, and continued development was moved to a different repository. Using this version may lead to compatibility issues with newer Jest or Node.js versions, security vulnerabilities, or unaddressed bugs.

fix

Migrate to an actively maintained alternative like `@digitalroute/jest-jenkins-reporter` or `jest-junit`. Ensure you update your `package.json` and Jest configuration accordingly. For example, change `testResultsProcessor` to `@digitalroute/jest-jenkins-reporter` after installing the new package.

affects: >=1.0.2

gotchaJest's `testResultsProcessor` option, while functional, is largely superseded by the `reporters` array in modern Jest configurations. The `reporters` array offers more flexibility for integrating multiple reporters and custom options, and it's generally the recommended approach for new projects.

fix

Consider refactoring your Jest configuration to use the `reporters` array. For example: `"jest": { "reporters": ["default", "jest-jenkins-reporter"] }`. Note that some reporters might require different configuration syntaxes when used in the `reporters` array.

affects: >=1.0.0

gotchaThis package only *generates* an XML report file. For Jenkins to display these test results, you must install and configure the 'JUnit Plugin' (or a similar test results parser) within your Jenkins job configuration. Without the Jenkins plugin, the generated XML file will not be automatically processed or displayed.

fix

In your Jenkins job configuration, add a 'Publish JUnit test result report' post-build action. Specify the path to the generated XML file (e.g., `reports/jest-report.xml`) in the 'Test report XMLs' field.

affects: *

Errors

Common errors & fixes

Cannot find module 'jest-jenkins-reporter' from 'package.json'

The package `jest-jenkins-reporter` was not correctly installed or is not resolvable in the project's node_modules.

fix

Ensure the package is installed as a dev dependency: `npm install --save-dev jest-jenkins-reporter` or `yarn add --dev jest-jenkins-reporter`. Verify the name in `package.json` matches the installed package name exactly.

TypeError: Cannot read properties of undefined (reading 'testResultsProcessor')

Jest configuration for `testResultsProcessor` is misplaced or malformed within `package.json` or a `jest.config.js` file.

fix

Ensure the `testResultsProcessor` entry is directly under the `jest` key in `package.json` or correctly exported in `jest.config.js`. For example: `"jest": { "testResultsProcessor": "jest-jenkins-reporter" }`.

Upgrade

Version history

1.0.2latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

4 hits · last 30 days

node

Resources

githubhttps://github.com/pilipa-cn/jest-jenkins-reporter ↗

packagehttps://www.npmjs.com/package/jest-jenkins-reporter ↗