jest-junit is a Jest reporter that generates compatible JUnit XML files from Jest test runs. It is useful when you need CI tools or other systems to consume Jest test results as standard JUnit XML, and it can be configured via Jest reporter options, a package.json key, or environment variables.
Project status
- Actively maintained: The project shows recent activity, with a latest GitHub push on 2026-06-08 and a most recent update v17.0.0 on 2026-04-24, which indicates ongoing maintenance rather than dormancy.
- Update cadence: There was a long gap between v16.0.0 (2023-04-15) and v17.0.0 (2026-04-24), but updates appear to be resuming with another push in mid-2026.
AI summary generated
Recent updates
v17.0.0
v17.0.0 primarily modernizes the package dependencies (notably upgrading uuid). The code changes also introduce async behavior into the reporter/testResultsProcessor flow and update the testing toolchain to newer Jest and Node versions.
Breakingv16.0.0
v16.0.0 introduces support for adding custom properties to individual JUnit `<testcase>` elements by loading a user-provided JS module. The implementation adds new reporter options (and corresponding environment variables) to point to that module, then injects the resulting key/value pairs into the generated XML.
Featuresv15.0.0
v15.0.0 updates jest-junit to ensure JUnit XML output is valid when test failure messages contain illegal ANSI escape sequences. The main code change is in how failure text is sanitized before being embedded into XML.
v14.0.1
Release v14.0.1 makes Jest JUnit XML generation more accurate by avoiding creating extra failing testcases when the underlying Jest report indicates no error. The release notes only mention preventing unnecessary duplicate test cases.
v14.0.0
v14.0.0 primarily improves how jest-junit gathers configuration from package.json across different platforms and how it reports failures that occur in Jest test hooks. It also extends the junit result generation logic to cover additional “testExecError” scenarios seen when hook code crashes.
v13.2.0
v13.2.0 adds improved monorepo support by introducing a new filePathPrefix option that is applied to generated JUnit test suite file paths. The release also drops support for Node 10.x and updates CI configuration accordingly. The code diff additionally reveals other behavior and dependency changes that are not mentioned in the release notes.
BreakingFeaturesv13.1.0
v13.1.0 extends jest-junit to allow locating the custom testsuite properties file from a configurable directory. The implementation adds new option plumbing and a path-resolution helper so the properties file path can be resolved using the Jest root directory.
Featuresv13.0.0
v13.0.0 updates jest-junit by bumping strip-ansi, adding support for omitting stack traces from failure reports, and fixing output path handling related to rootDir. The code changes are primarily in output generation (buildJsonResults and getOutputPath) plus option wiring in constants and README.
Featuresv12.3.0
This release fixes how Jest suite displayName is handled when generating output. Specifically, it adjusts displayName processing to support cases where suite.displayName is not a plain string.
v12.2.0
Release v12.2.0 primarily bumps the uuid dependency from the 3.x line to 8.3.2. The code change updates how uuid is imported to match the newer uuid package API.