Free tools

Test Report Viewer: JUnit, TRX, NUnit and Playwright

Drop one or more test result files to see what failed, grouped by cause, which tests are slowest and what the runner retried. It reads JUnit XML, TRX, NUnit, Playwright JSON and CTRF.

Runs in your browserNothing is uploadedNo sign-up

Paste the file, or choose or drop one or more files. Reads JUnit XML, TRX (Visual Studio / dotnet test), NUnit 3 XML, Playwright JSON, CTRF JSON.

Or drop files on the box. Nothing is uploaded.

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:

  • A summary: tests, passed, failed, errors, skipped, flaky, pass rate and duration. The pass rate is passed tests over tests that ran, so skipped tests don't lower it. When the test times add up to more than the run took, the tests ran in parallel, and the viewer says so.
  • Failures by cause: failures and errors grouped by the first line of their message. Twenty tests failing on one Connection refused is one problem, not twenty.
  • The slowest tests, with each one's share of the total test time.
  • Suites: tests, failures, skips and time per class, fixture or file.
  • Every test, filtered by result or searched by name and message. Select a test to read its message and stack trace.

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.

FormatUsually written byWhat to know
JUnit XMLpytest, Maven Surefire, Jest with jest-junit, Playwright, Go with gotestsumNo single official schema; each writer adds its own attributes. See the JUnit XML viewer.
TRXdotnet test, vstest.console, Visual StudioOutcomes such as Timeout and Aborted count as errors here. See the TRX viewer.
NUnit 3 and NUnit 2 XMLNUnit console and adapterThe label attribute says whether a failure was an error. See the NUnit XML viewer.
Playwright JSONnpx playwright test --reporter=jsonEach test runs once per project, with every retry recorded. See the Playwright JSON viewer.
CTRF JSONCTRF reporters for many frameworksOne 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 development

Automated 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