01 Tests
Know exactly what to test, and what is covered
TestPlum keeps every test as structured steps with an expected result per step, in folders you shape, with a version for every edit. Tests link to requirements, and coverage is worked out from the latest real results, so you can see which promises are verified, failing, not run yet or not covered at all.
What's included
Structured steps, versions, folders, templates, requirements coverage and imports from other tools.
- 01.1
Steps with expected results
Each step has an action and what should happen, so a tester records exactly which step passed or failed instead of a single verdict for the whole test.
- 01.2
A version for every edit
Every save makes a new version you can compare with any other. Runs keep the version they ran, so past results always refer to the steps that were really executed.
- 01.3
Folders, keys and saved views
Organise tests in folders and subfolders. Every test gets a short key such as MOB-C12 to paste into commits and chats. Search, filter and save views for the team.
- 01.4
Coverage from real results
Link tests to requirements. Each requirement is passing, failing, partly passing, not run or not covered, worked out from the latest results, and a matrix traces requirement to test to result to open bug.
- 01.5
Suggested tests (optional AI)
With AI switched on, TestPlum drafts tests from a requirement for a person to review. AI-written tests count only partly in the release verdict until someone reviews them.
- 01.6
Bring your tests with you
Import TestRail and Xray exports or any CSV. The file is checked first, nothing is written unless every test is valid, large files import in the background with progress, and importing a newer export updates the same tests.
Coverage, traced from requirement to result
In practice
How it goes
Shape the folders
Create folders for areas of the product and subfolders for features or screens.
Write or import tests
Write steps with the keyboard, start from a template, or import a TestRail, Xray or CSV export.
Link requirements
Connect each requirement to the tests that prove it; coverage updates as results come in.
Automate when ready
Turn a manual test into a Playwright test file, or export a selection to your repository as a patch or branch.
Can I bring my tests from TestRail or Xray?
Yes. TestPlum imports TestRail XML and CSV exports and Xray tests as JSON or CSV, including Jira's CSV export. You see what will happen before anything is saved, and each test keeps its TestRail ID or Jira key, so importing a newer export later updates the same tests instead of adding copies.
Does TestPlum keep a history of changes to a test?
Yes. Every save creates a new version, and you can compare any two. Runs remember the version they ran, so results always refer to the steps that were executed.
How is requirement coverage worked out?
From the latest recorded result of every linked test. A requirement is passing when its tests pass, failing when any fails, partly passing, not run yet, or not covered when no test is linked.
The rest of the loop
Decide whether to ship
A ready or not-ready verdict from agreed checks, a trusted pass rate, and verdicts for every project.
Release in detail 02 · RunsTest it
Suggested selections, keyboard-first execution, live progress, cycles, and Playwright and CI results.
Runs 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 minRequirements traceability matrix: what it is and how to build one
A requirements traceability matrix maps each requirement to its tests, results and defects. The columns to include, a worked example and how to keep it current.
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.