01What test management covers
A test management tool typically holds:
- A test case repository — every test you might ever run, organised in folders or sections, with metadata like priority, owner, and status.
- Test runs — execution records of a subset of test cases against a specific build, environment, or release.
- Cycles or milestones — groupings of runs across a period (e.g. "v1.4 release regression").
- Exploratory sessions — unscripted testing with logged charters and findings.
- Results and reports — the audit trail of what passed, what failed, what's blocked.
02Why it matters
The alternative is a spreadsheet. Spreadsheets work fine until you have more than one tester or more than 50 cases. Then they fall apart: cases drift, status gets stale, nobody trusts the "current" version.
Test management exists to answer one question on demand: what did we actually test before this release went out, and what was the outcome?
03Related
04Frequently asked questions
Is test management the same as test automation?
No. Test management is the structured surface where test cases, runs, and results live. Test automation is one way of executing tests. A mature team uses both — automation runs scripted cases, the test management tool tracks coverage and outcomes.
Do small teams need test management?
Once you have more than ~50 cases or more than one tester, spreadsheets stop scaling. A test management tool replaces them at that point.