testland/junit-xml-analysis
Parses JUnit-format XML reports (the de-facto interchange format every CI ingests - Jenkins, GitHub Actions, GitLab, Buildkite, CircleCI) into structured, machine-readable per-suite and per-case metrics tables (passed / failed / errored / skipped, time, classname, message, stack), groups failures by classname for trend analysis, and distinguishes "new failures vs flakes" by cross-referencing the `flakyFailure` and `rerunFailure` rerun elements. Use when the downstream consumer is a dashboard, script, or aggregator - not when the goal is a human-readable prose summary (use test-run-summary-author for that). Single-run, in-XML aggregation only; for cross-run cross-environment roll-ups, use a cross-run test-suite aggregator.
90
90%
Does it follow best practices?
Impact
—
Average score across 10 eval scenarios
Passed
No findings from the security scan
Evaluation results
"renders" is the worst test in the company and nobody can find it
Finance asked why a two-minute test suite needs four more runners
Merged shard totals report more tests than the repo contains
On-call gets paged for eight failures that are not eight failures
Quarantine list keeps muting tests that fail every single time
Release channel gets one line per build and the line has been wrong twice
Release gate reported a clean run on a night something threw
Slowest-test board is all backend tests and the backend team says it is wrong
The board says 95% green while the mobile team says nothing of theirs runs
Two dashboards read the same report and disagree about how many tests ran
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6