No test runner plugin
Your runner writes a JSON or JUnit XML report — a flag or one line of config. Nothing hooks into your tests.
Test reporting for CI and local runs
Your tests write a report file, the EasyTrace CLI uploads it when they finish. See failures, new failures, flaky tests and coverage for every run.
Private preview: until the CLI is on npm, install it from GitHub.
$ easytrace run -- pnpm test Test Suites: 1 failed, 11 passed, 12 total Tests: 1 failed, 214 passed, 215 total Uploaded 1 failed, 2 flaky, 212 passed from 1 file (suite unit) · coverage 82.4% lines → https://app.easytrace.dev/app/runs/…
Reads the report your runner already writes
Your runner writes a JSON or JUnit XML report — a flag or one line of config. Nothing hooks into your tests.
Upload problems are warnings. easytrace run exits with your tests’ exit code, so it can replace pnpm test anywhere.
Each run is compared with the latest finished run of the same suite on your default branch, so regressions stand out.
A test that fails and then passes on retry is counted as flaky, not passed, so you can see which ones to fix.
Line, statement, function and branch coverage for Vitest and Jest, with the change against the baseline and per-file details.
CI uploads with a project token; developers sign in once with easytrace login. Local runs carry a Local chip.
pnpm add -D @easytrace/cli
pnpm exec easytrace loginRead more →pnpm exec easytrace init
# writes easytrace.config.jsonRead more →pnpm exec easytrace run -- vitest run \
--reporter=json --outputFile.json=…Read more →Works with the test runner you already use, from CI or from your machine.
Start the quickstart