Test Management

Test management is how a team organises the testing effort: where test cases live, how they map to requirements, how runs are tracked, and what you report. The tool is secondary to the discipline — but the right tool makes the discipline cheap. Pair this with the Test Case Writing sheet for authoring individual cases.

What test management covers

Organising test cases into suites and a maintainable library
Linking tests to requirements/user stories (traceability)
Executing tests in runs/cycles and recording results
Reporting coverage, pass/fail trends and quality signals
Integrating with the issue tracker (usually Jira) so failures become defects

The core artifacts

Artifact	What it is
Test case	A single check: steps, data, expected result
Test suite	A grouped set of cases (by feature, type, risk)
Test plan	What will be tested, by whom, when, and to what exit criteria
Test run / cycle	One execution of a suite against a build/environment, with results
Defect	A failure linked back to the case and the requirement

Traceability

Traceability ties each requirement to the test cases that verify it, and each failure to the requirement at risk. It answers the two questions stakeholders actually ask:

Coverage: is every requirement tested? (gaps = untested risk)
Impact: if this test fails, what requirement/feature is affected?

A requirements-traceability matrix (RTM) is the classic artifact; modern tools maintain it automatically via links.

Test runs and cycles

A test case is a definition; a run is an execution of it against a specific build and environment. Keep them separate: the same case runs many times across cycles, and the history (when it last passed, how often it flakes) is as valuable as the latest result. Tie runs to a build/version so a result means something.

Metrics that matter

Metric	Signal
Requirement coverage	Untested risk
Pass/fail rate per cycle	Build health and trend
Test execution progress	Are we on track for the exit criteria?
Defect density / by area	Where the risk concentrates
Flaky/blocked rate	Trust in the suite and environment

Report trends, not single numbers — a 90% pass rate falling cycle over cycle is worse than a steady 85%.

Jira-native vs standalone tools

Approach	Tools	Fits when
Jira apps (live inside Jira)	Xray, Zephyr Scale, Appsvio Test Management	Your team runs on Jira and wants tests beside issues
Standalone platforms	TestRail-style: qTest, PractiTest, Qase, Testmo, TestPlanIt	You want a dedicated tool, multi-tracker, or non-Jira stack
Open-source	TestLink, Squash TM	Budget-constrained or self-hosting is required
Automation-first / DevOps	Allure TestOps	Heavy automated suites you want managed alongside manual
Enterprise/regulated	OpenText ALM/Quality Center	Large, compliance-heavy programmes

Choosing a tool

On Jira? A Jira app (Xray/Zephyr) keeps tests, issues and traceability in one place — usually the path of least resistance.
Automation-heavy? Pick a tool that ingests automated results (Allure TestOps, qTest) so manual and automated coverage live together.
Budget-led / self-host? TestLink or Squash TM.
Regulated/enterprise? A platform with audit trails and formal traceability (OpenText ALM/Quality Center).
Weigh integration with your tracker and CI above feature checklists — a tool nobody updates is worse than a spreadsheet.