{"id":13375,"library":"jest-jenkins-reporter","title":"Jest Jenkins Reporter","description":"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.","status":"abandoned","version":"1.0.2","language":"javascript","source_language":"en","source_url":"ssh://git@github.com/pilipa-cn/jest-jenkins-reporter","tags":["javascript","jest","jenkins","reporter"],"install":[{"cmd":"npm install jest-jenkins-reporter","lang":"bash","label":"npm"},{"cmd":"yarn add jest-jenkins-reporter","lang":"bash","label":"yarn"},{"cmd":"pnpm add jest-jenkins-reporter","lang":"bash","label":"pnpm"}],"dependencies":[],"imports":[{"note":"This package is not imported as a JavaScript module; it's specified as a string path in Jest's configuration.","wrong":"import { JestJenkinsReporter } from 'jest-jenkins-reporter';","symbol":"jest-jenkins-reporter","correct":"\"testResultsProcessor\": \"jest-jenkins-reporter\""}],"quickstart":{"code":"{\n  \"name\": \"my-jest-project\",\n  \"version\": \"1.0.0\",\n  \"description\": \"A sample project using jest-jenkins-reporter.\",\n  \"main\": \"index.js\",\n  \"scripts\": {\n    \"test\": \"jest\",\n    \"test-jenkins\": \"NODE_ENV=test jest --colors\"\n  },\n  \"jest\": {\n    \"testResultsProcessor\": \"jest-jenkins-reporter\",\n    \"collectCoverage\": true\n  },\n  \"jestSonar\": {\n    \"reportPath\": \"./reports\",\n    \"reportFile\": \"jest-report.xml\",\n    \"indent\": 4\n  },\n  \"keywords\": [],\n  \"author\": \"\",\n  \"license\": \"MIT\",\n  \"devDependencies\": {\n    \"jest\": \"^29.0.0\",\n    \"jest-jenkins-reporter\": \"^1.0.2\"\n  }\n}\n\n// example.test.js\ndescribe('Example Test Suite', () => {\n  test('should add two numbers correctly', () => {\n    expect(1 + 2).toBe(3);\n  });\n\n  test('should subtract two numbers correctly', () => {\n    expect(5 - 2).toBe(3);\n  });\n});","lang":"javascript","description":"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."},"warnings":[{"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.","message":"This `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.","severity":"breaking","affected_versions":">=1.0.2"},{"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.","message":"Jest'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.","severity":"gotcha","affected_versions":">=1.0.0"},{"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.","message":"This 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.","severity":"gotcha","affected_versions":"*"}],"env_vars":null,"last_verified":"2026-04-19T00:00:00.000Z","next_check":"2026-07-18T00:00:00.000Z","problems":[{"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.","cause":"The package `jest-jenkins-reporter` was not correctly installed or is not resolvable in the project's node_modules.","error":"Cannot find module 'jest-jenkins-reporter' from 'package.json'"},{"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\" }`.","cause":"Jest configuration for `testResultsProcessor` is misplaced or malformed within `package.json` or a `jest.config.js` file.","error":"TypeError: Cannot read properties of undefined (reading 'testResultsProcessor')"}],"ecosystem":"npm","meta_description":null,"install_score":null,"install_tag":null,"quickstart_score":null,"quickstart_tag":null,"pypi_latest":null,"cli_name":"","cli_version":null}