A test run is one execution of one test case. A plan run is one execution of a bundle of tests. Both reports follow the same pattern: pass rate at the top, filterable list in the middle, drillable detail on the right.
A single pass rate number is a snapshot. A pass rate over 30 days is a trend. Text2Test surfaces both, so you can answer "are we getting better or worse?" in one glance.
Every dashboard compares the current window to the previous one. +4.1% pass rate this month versus last. Catch direction, not just position.
30 daily bars on each card. Spot the bad day, the bad week, the moment something broke. Hover for the exact run count.
A single donut at the top of every report. 30 days, every run included. The number that goes in your sprint review or board update.
Every plan run opens to its test list. Every test opens to its step timeline. Every step opens to its AI request, AI response, and screenshot.
No tab-hopping. No log files. No "let me check the CI build."
A failed test is not always a real failure. Sometimes the test runs the same flow twice, fails the first time, passes the second. Most teams either ignore the flake or rerun the whole suite. Both lose time.
From any test row, mark it as flaky. The system tags the test, surfaces it in analytics, and keeps a flake count over time. You see which tests need fixing versus which tests are catching real bugs.
From the test row menu, mark as flaky. Single action, no separate workflow.
Flaky tests appear in a dedicated view. Sort by flake count. See trends per test, per environment, per executor.
A flake is logged the moment you tag it. Once you ship a fix, you can verify the same test passes consistently across runs.
Filter by:
See how Text2Test reports turn raw test runs into something your team can act on. Live demo, your stack, your tests.
Request a Demo
