02 Runs
Run the right tests, record results fast, keep them honest
A TestPlum run starts from a suggestion: tests that failed or were blocked last time, never ran, changed since they ran, or are critical. Testers record results step by step from the keyboard, everyone sees progress live, and automated results from Playwright and CI land in the same append-only history.
What's included
Suggested selections, keyboard-first execution, live progress, cycles, and Playwright and CI results.
- 02.1
Suggested selections
New runs start with the tests that need it: failed or blocked last time, never ran, changed since they ran, or critical. Everything, a filter or a hand-picked list are one click away.
- 02.2
Keyboard-first execution
Press 1 to 9 to record a result, J and K to move between tests, and switch to focus mode to hide everything but the test in front of you.
- 02.3
Results that cannot be rewritten
Results are append-only. A run keeps the test versions it was created with, and signing off a run locks its results until someone reopens it.
- 02.4
Live progress
Every open run page updates as results come in. The run barcode shows each test's result at a glance, and progress charts show who is doing what.
- 02.5
Playwright on your own runners
Point a runner you start on your own machine or CI box at a repository and run its Playwright tests on demand, on a schedule or for every pull request. Screenshots, videos and traces come back with the results.
- 02.6
CI results in the same place
The Playwright reporter records every attempt, including retries, and any CI system can upload JUnit XML. Manual and automated results share one history and one verdict.
New runs start from what needs testing
In practice
How it goes
Start from the suggestion
Name the run, check the suggested tests, assign people and set a due date.
Record results
Work through the tests step by step, from the keyboard, with comments and attachments.
Bring in automation
Runners and CI add their results to the same run or to runs of their own.
Sign off
Signing off completes the run and locks its results; rerun the failures as a new run in one click.
How does TestPlum choose which tests to suggest?
A test is suggested when its latest result failed, was blocked or asked for a rerun, when it has never run, when it changed since the version that last ran, or when it is critical. You can switch to everything, a filter or a hand-picked list at any time.
Can automated test results go into TestPlum?
Yes. A runner you start on your own machine runs Playwright tests from your repository, the Playwright reporter records each attempt with its evidence, and any CI system can upload JUnit XML results.
Can someone change a result after a run is finished?
Results are append-only: a new result is added, never overwritten. Signing off a run locks it, and it accepts no new results until someone reopens it.
The rest of the loop
Know what to test
Structured steps, versions, folders, templates, requirements coverage and imports from other tools.
Tests in detail 03 · FailuresUnderstand failures
Failures grouped by cause and sorted with reasons, one bug per cause, and fixes proven before approval.
Failures in detailRelated guides
What is test management?
Test management is how a team plans, writes, runs and reports on software tests. Learn the core building blocks, the metrics that matter and how to choose a tool.
Guide · 7 minRelease readiness: six checks that tell you if a build can ship
A release readiness checklist for QA teams: scope, completion, pass rate, critical failures, open critical defects and verified requirements.
Guide · 7 minFlaky tests: how to detect, measure and fix them
A flaky test passes and fails without a relevant change. A simple formula to measure flakiness from test history, common root causes and a triage process that works.
Guide · 6 minRisk-based testing: prioritise the tests that matter most
Risk-based testing orders tests by the likelihood and impact of failure. A transparent scoring model built from priority, recent failures, changes and coverage gaps.
Find out whether your next release is ready
Create a workspace, import your tests or write a few, and record a run. Everything on this site is in the product today.