QA tools that run in your browser
Open test reports, find flaky tests, split CI shards and design test inputs. Every tool runs on this page: files are read by your browser and never uploaded.
Read test reports
Open the result files your CI already writes, see what failed and why, and check the file itself.
Test report viewer
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.
JUnit XML viewer
Paste or drop the JUnit XML your test runner wrote to see failures grouped by message, the slowest tests and per-suite totals.
TRX viewer
Open a .trx file from dotnet test or Visual Studio without Visual Studio: outcomes, error messages, stack traces and timings.
NUnit XML viewer
Read the TestResult.xml that the NUnit console or adapter writes: failures with stack traces, ignored tests and slow fixtures.
Playwright JSON report viewer
Open the file Playwright's JSON reporter writes: failed and flaky tests per project, every retry, and error messages with the terminal colour codes removed.
CTRF report viewer
View a Common Test Report Format (CTRF) JSON file from any framework: status counts, flaky tests, retries and suites.
JUnit XML validator
Check a JUnit XML file for the problems that make CI dashboards, test gates and the run itself disagree, with the line of each one.
Fix slow and flaky CI
Compare runs to find flaky tests, and split a suite into shards that finish together.
Flaky test finder
Drop reports from several runs of the same suite on the same code. Tests that pass in one run and fail in another, or pass only on a retry, are flaky.
Test shard balancer
Split tests or spec files into CI shards that finish at about the same time, from a test report or a list of durations.
Design test cases
Pick the inputs worth testing: boundaries, pairwise combinations and timestamps that break parsers.
Pairwise test generator
List the parameters and their values. The generator returns a small set of test cases in which every pair of values appears at least once.
Boundary value calculator
Enter the valid range and the smallest step the input accepts. You get the boundary values to test, the equivalence partitions and a ready test table.
Timestamp validator
Paste timestamps, one per line, to see whether each is RFC 3339, ISO 8601 or neither, and which instant in UTC it names.