What Is Test Management?
Test management is the planning, scheduling, estimating, monitoring, reporting, controlling, and completing of test activities. That is the ISTQB definition. It names a function, and the function has different owners: in one organization a test manager holds it, in another a team lead, and in agile teams the team itself often does.
Without that function, testing stays a set of activities and never becomes a process. Many projects show the same symptoms: tests run ad hoc, nobody can compare results, risks stay uncontrolled, and at the end nobody can say with confidence what the team tested and what it skipped. Test management makes quality decisions possible in the first place, instead of leaving gut feeling to argue with the release date.
Seven Core Responsibilities, from Planning to Closure
The responsibilities span the whole test process, from the first planning idea to the formal close-out:
- Planning: define test scope, test strategy, schedule, and resource needs.
- Estimating: size the testing effort realistically, based on experience, project size, and risk analysis.
- Organizing: build the test organization: staff the team, clarify roles, select tools, provision test environments.
- Monitoring: track test progress continuously and spot deviations early.
- Controlling: step in when plan and reality drift apart, and initiate corrective action.
- Communicating: keep stakeholders informed about test status, risks, and quality signals.
- Closing: formally conclude test activities, document the outcome, capture lessons learned.
Listed like this, the seven look sequential. In practice they overlap. Monitoring and controlling run for as long as testing runs, and planning continues throughout the project, because reality departs from the plan in every project I have seen.
The Test Process: What Management Steers at Each Step
The test management process sits as a steering layer on top of the test process itself. The ISTQB syllabus describes that process with seven activities: test planning, test monitoring and test control, test analysis, test design, test implementation, test execution, and test completion. Management takes part in each of them, leading some and only setting priorities and boundaries for others.
Planning and completion belong to test management entirely. This is where the test plan, the effort estimate, and the entry and exit criteria come from, and at the end the test completion report and the lessons learned. Monitoring and control run alongside everything else, from the first day to the last. Test analysis, design, implementation, and execution are the test team’s craft. Management sets the priorities there, provides the environment and the test data, and makes sure the test basis arrives in time.
In practice this rarely runs as a chain. Iterations turn the process over every two weeks, test levels overlap, and a finding from execution changes the plan for the next round. Seen from management, the test process is a cycle with fixed reporting points in every round.
What Questions Must a Test Plan Answer?
The test plan is the document that test management steers by. It records what gets tested, how, with which resources, and in what time frame. A usable test plan answers at least these questions:
- What is in scope, and what is explicitly out?
- Which test levels will be run?
- Which entry and exit criteria apply?
- Who is responsible for which test activities?
- Which test data, environments, and tools are needed?
- How are risks handled?
Planning includes estimating the effort. The estimate rests on experience from comparable projects, on the complexity of the systems under test, and on the results of the risk analysis. Techniques such as three-point estimation or function point analysis help turn that into realistic numbers rather than a figure chosen to please the deadline.
One mistake recurs more than any other: writing the test plan once and never touching it again. When scope changes, resources shift, or new risks appear, the plan needs the same update. Otherwise it stops steering anything. An outdated test plan is an archive, and nobody steers a project from the archive.
Risk Decides the Testing Effort
The test strategy describes the overall approach one level above the plan: which test levels are used, which test types matter, how risks are handled, and where the emphasis lies. A test plan stays project-specific. A test strategy can apply across a whole organization and give every project the same frame.
Good test management is risk-based, because features differ in risk and risks differ in how much testing they justify. Risk analysis looks at two dimensions, the likelihood that a defect occurs and the damage it does when it occurs. Features that score high on both receive intensive testing. Low-risk areas deliberately receive less. Risk-based testing concentrates the test effort where the risk is highest; teams that use the label to shorten testing across the board have misread it. The approach only works when someone identifies, assesses, and writes down the risks, instead of carrying them around in the test manager’s head.
How Do Monitoring, Control, and Reporting Fit Together?
Test monitoring means watching the running test process and comparing it against the plan, continuously. Test control means actually intervening when the two diverge. Both last as long as testing lasts. Typical control actions: reassigning people, adjusting test priorities to the current risk picture, revising test objectives after requirements changed, or checking the entry criteria for the next test level before running into it.
Reporting makes the test status visible to stakeholders. A useful status report contains the current progress, open and resolved defects by severity, risk coverage, deviations from plan, and a clear assessment of the quality situation. A report that shows only green lights for months deserves scrutiny. Either the project has no risks, or the report leaves them out, and the second case is far more common.
Two reports are worth keeping apart. The test progress report appears regularly during testing and shows status, deviations, and risks as of a given date. The test completion report appears once, at the end of a test level, an iteration, or a release. It summarizes what the team tested, what remains open, which defects are unresolved, and what the project takes away. The test log sits one level below both. It is the raw record of execution: which test case ran when, with which result. Reports condense those logs for readers who do not know every test case.
Which Metrics Count, and Which Mislead?
Metrics make the test process measurable and give discussions a shared reference point. The ones that matter most in test management:
- Test case progress: planned versus executed versus passed test cases.
- Defect metrics: defects found by severity, ratio of found to fixed defects, age of open defects. These numbers show how fast the backlog shrinks, not how good the tests are.
- Test coverage: requirements coverage, and code coverage for automated tests. Requirements coverage presupposes traceability: every requirement points to at least one test case, every test case points to the requirement it checks.
- Test effectiveness: defects per executed test case, and defect detection percentage, the share of defects found in testing out of all defects known later.
- Risk coverage: the share of identified risks addressed by test activities.
As useful as these figures are, they are indicators, and each one needs interpretation. High coverage does not mean the tests exercised the critical scenarios. A low defect count can mean two things: the software is good, or the tests are too weak to find anything. Metrics need their context, which is why a test manager reports the number together with the story behind it.
Strategic Test Management: Beyond the Next Release
Most of what this page describes happens inside a project. Strategic test management works on a longer horizon. It asks how an organization wants to test across projects and releases, and what has to be in place so that no project starts from zero. The organization-wide test strategy is the visible part. Behind it sit a tool landscape that fits the process, people with the skills the strategy assumes, metrics that are comparable from one project to the next, and the habit of feeding lessons learned back into the strategy rather than into a folder.
That long-term view is also where test process improvement lives. A project team optimizes for its release. Someone has to look at the pattern across releases: the same late test start, the same missing exit criteria, the same tool bought before the process existed. This part of the job names those patterns and changes the conditions behind them. In most organizations it has no owner, which is why the same patterns return release after release.
Agile Teams without a Test Manager: Who Manages Testing?
In agile environments several people share the classic test management tasks, because Scrum defines no test manager role. Planning happens in Sprint Planning, retrospectives take the place of formal lessons-learned sessions. The Daily Scrum deserves a precise word: it is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. It is no reporting slot for test metrics. Blocking test findings surface there, of course, but the actual test monitoring runs alongside, through dashboards and the conversations in the team. Test management stays; agile teams distribute its tasks differently.
The ISTQB Foundation syllabus says the same in its own words: the agile team can handle parts of the test management role, and tasks that span several teams or the whole organization can sit with test managers outside the development team. Whoever holds those tasks needs three abilities above all: coordinating without formal authority, communicating across team silos, and making quality risks visible while they are still risks and not yet incidents. Tools such as Azure DevOps or Jira with Xray support managing test cases and defects in iterative work. They keep the test status visible across sprints and teams, which nobody manages from memory at a two-week cadence. Deciding what that status means, and what to do about it, stays with people.
Five Pitfalls, Regardless of Industry
Some mistakes show up in test management with a certain regularity, whatever the domain or project size.
Starting too late: When test planning begins only once implementation is running, the test basis for the early test levels is missing. Development hands over components before test cases exist. That creates time pressure in exactly the phases where thorough testing would make the biggest difference.
Missing exit criteria: Without clear criteria for when testing is done, teams simply keep testing until the time runs out. Exit criteria belong at the start of the project, agreed with the stakeholders who later sign the release, and they lose their value once the week before the release has started.
Optimizing for metrics: The moment a test team optimizes for high test case counts instead of defect detection, its metrics lose their meaning. Many shallow tests that find little are a good-looking number without substance.
An isolated test team: Testing as a control gate at the end of the chain finds defects too late and too expensively. Test management has to be integrated into the development process, with testers in refinement and planning and the test basis available before the handover, instead of operating as a downstream filter that everything passes through because nobody looked earlier.
Tool before process: Buying test management software first and bending the process to fit it afterwards. Jira with Xray or Zephyr, Azure DevOps, and similar tools manage test cases, defects, and reports. The process they are supposed to manage does not come in the box. Without one, the license buys a tidier form of disorder.
From Practice
What I see again and again in projects is less a lack of documents than a lack of use. The test plan exists, but nobody opens it anymore. Someone presented the test strategy at the kickoff and nobody has touched it since. The team dutifully collects metrics and never discusses them. That is document production, and the difference between producing documents and steering by them decides whether the work changes anything or only fills a folder.