Registry / testing / jest-multi-test-result-processor

jest-multi-test-result-processor

library1.0.0jsnpmunverified

The `jest-multi-test-result-processor` package enables Jest to use multiple `testResultProcessor` modules for generating diverse test reports from a single test run. Prior to Jest's native support for multiple reporters, this package filled a gap by allowing composition of various output formats like JUnit XML and HTML. It operates by delegating the final test results to a list of specified processors in sequence. The package's current stable version is 1.0.0, last published in February 2018. Its release cadence is effectively inactive, as it has not been updated in over eight years. While historically useful, Jest's built-in `reporters` array (introduced around Jest 20 in May 2017) largely superseded the need for this package for most common reporting needs, and the `testResultsProcessor` option itself is now considered a legacy feature by many reporter packages.

testing

npm install jest-multi-test-result-processor

package ↗

INSTALL

IMPORT

SIG · JEST-MULTI-TEST-RE

jest-multi-test-result-processor

testingjavascriptv1.0.0

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.

Configuration

✓ { "jest": { "testResultsProcessor": "jest-multi-test-result-processor" }, "jest-multi-test-result-processor": { "processors": ["jest-junit", "html-jest-reporter"] } }

✗ import multiProcessor from 'jest-multi-test-result-processor'

This package is not imported as a JavaScript/TypeScript module. It is configured via the `package.json` or `jest.config.js` as a string path to a test result processor. The actual processors it orchestrates are listed under its dedicated `package.json` key.

This quickstart demonstrates how to configure `jest-multi-test-result-processor` in `package.json` to process test results using both `jest-junit` and `jest-html-reporter`. It includes a sample `package.json` with dev dependencies and the necessary Jest configuration, alongside a basic test file to generate output for the specified processors.

{ "name": "my-jest-project", "version": "1.0.0", "devDependencies": { "jest": "^29.0.0", "jest-junit": "^16.0.0", "jest-html-reporter": "^4.0.0", "jest-multi-test-result-processor": "^1.0.0" }, "scripts": { "test": "jest" }, "jest": { "testResultsProcessor": "jest-multi-test-result-processor" }, "jest-multi-test-result-processor": { "processors": [ "jest-junit", "./node_modules/jest-html-reporter" ] } } // example.test.js describe('My Example Tests', () => { test('should pass a basic assertion', () => { expect(1 + 1).toBe(2); }); test('should fail a basic assertion (for report demo)', () => { expect(2 + 2).toBe(5); }); });

Debug

Known issues

breakingThe `testResultsProcessor` configuration option in Jest, which this package relies on, is considered a legacy feature and is actively deprecated by many popular reporters (e.g., `jest-junit`, `jest-trx-results-processor`). Jest's native `reporters` array (e.g., `reporters: ['default', 'jest-junit', 'jest-html-reporter']`) provides equivalent functionality and is the recommended, modern approach for using multiple reporters.

fix

Migrate your Jest configuration to use the `reporters` array instead of `testResultsProcessor`. Install desired reporters (e.g., `jest-junit`, `jest-html-reporter`) directly and list them in the `reporters` array in `jest.config.js` or `package.json`.

affects: >=1.0.0 (all versions)

gotchaThis package was last published in February 2018. It is not actively maintained, and its functionality has been largely superseded by built-in Jest features. Using an unmaintained package may lead to compatibility issues with newer Jest versions or other ecosystem tools, and potential security vulnerabilities.

fix

Strongly consider replacing this package with Jest's native `reporters` array. If unique functionality is required, evaluate other actively maintained community solutions or custom Jest reporters.

affects: >=1.0.0

gotchaWhen configuring the processors, you might need to use relative paths for local modules, especially if they are not directly discoverable by name. For example, './node_modules/jest-html-reporter' instead of just 'jest-html-reporter'.

fix

Ensure that processor paths are correctly resolved by Jest. For modules installed via npm, the module name is often sufficient, but for specific or custom processors, a full or relative path might be necessary (e.g., in `package.json` config: `"processors": ["jest-junit", "./node_modules/jest-html-reporter"]`).

affects: >=1.0.0

Errors

Common errors & fixes

Validation Error: Options: Unknown option "testResultsProcessor" with value "jest-multi-test-result-processor" was found.

This error typically indicates an outdated Jest version that does not recognize the `testResultsProcessor` option, or a misconfiguration where Jest expects a reporter array but finds a processor.

fix

Ensure you are using a Jest version that supports `testResultsProcessor` (though it is deprecated in newer versions). If on a modern Jest version, switch to using the `reporters` array configuration instead.

Cannot find module 'jest-multi-test-result-processor' specified in the 'testResultsProcessor' option.

The package `jest-multi-test-result-processor` is not installed or Jest cannot resolve its path.

fix

Install the package: `npm install --save-dev jest-multi-test-result-processor` or `yarn add --dev jest-multi-test-result-processor`. Verify the path if configured explicitly.

Upgrade

Version history

1.0.0latest on npm

Audit

Dependencies

jestrequiredRuntime dependency for test execution and processing test results.

jest-junitoptionalCommonly used test result processor that this package orchestrates. Other Jest reporters/processors are also expected.

Agent activity

4 hits · last 30 days

node

Resources

packagehttps://www.npmjs.com/package/jest-multi-test-result-processor ↗