JUnit Release Triage

RELEASE EVIDENCE WORKSPACE

Review the change.
Keep the evidence.

Bring your CI shards together, verify test identities, then build a triage packet.

Audit JUnit XML and compare release evidence

Audit multi-shard JUnit XML, review stable test identities, compare release evidence, and export a local triage packet. No report uploads.

How to use it

Import candidate shards and an optional baseline. Review identities and declared totals before comparing transitions and writing a triage note.

Limits to check

Missing records, unknown durations and empty runs are not passing releases. The tool does not infer flakiness or authorize a release.

The steps and limits describe this tool. Review the in-app instructions and use the included synthetic example, where available, before importing your own work. Browser data stays specific to the origin and browser you used; keep a recovery export before switching addresses.