What the viewer shows
Paste a report or drop one or more files on the box above. The viewer reads them on this page and shows:
Drop several files at once, such as one report per CI shard, and the viewer merges them into one run and lists the files with their own totals.
Formats it reads
The viewer detects the format from the file itself, so the extension doesn't matter.
| Format | Usually written by | What to know |
|---|---|---|
| JUnit XML | pytest, Maven Surefire, Jest with jest-junit, Playwright, Go with gotestsum | No single official schema; each writer adds its own attributes. See the JUnit XML viewer. |
| TRX | dotnet test, vstest.console, Visual Studio | Outcomes such as Timeout and Aborted count as errors here. See the TRX viewer. |
| NUnit 3 and NUnit 2 XML | NUnit console and adapter | The label attribute says whether a failure was an error. See the NUnit XML viewer. |
| Playwright JSON | npx playwright test --reporter=json | Each test runs once per project, with every retry recorded. See the Playwright JSON viewer. |
| CTRF JSON | CTRF reporters for many frameworks | One JSON shape across languages. See the CTRF viewer. |
Why two tools show different numbers for one run
A report states its counts twice: once in attributes such as tests="40" failures="2" on <testsuite>, and once in the test cases themselves. Tools that read the attributes and tools that count the cases disagree when the two drift apart, which happens when a writer crashes mid-file or a script edits the file. The viewer counts the test cases and warns when the declared counts differ. The JUnit XML validator lists every such problem with its line.
The other common cause is skipped tests. Some dashboards count a skip as a pass, some leave it out of the rate, and some count it against you. Compare pass rates only between tools that define them the same way.
Your files stay on your computer
The page reads files with the browser's File API and parses them in JavaScript on this page. No request carries the report anywhere, and there is no account, so reports with internal hostnames, stack traces or customer data in test names are safe to open.
Sources
Testland for teams
In developmentAutomated test reports, manual test runs and regression tracking in one workspace. A separate product, built on the same skills.
One email when it opens, nothing else. Privacy policy