Module 02 · Running a campaign · 10 min
Where do we stand?
The figures that describe a campaign, what each one hides, and why the answer always starts with what is not done.
Review
From the previous lesson: a defect is marked fixed. What closes it, and what happens to the case afterwards?
The course's answer
A new run that passes, on a build containing the fix. The case then stays in the suite as a regression case, so the defect cannot come back unnoticed.
Four figures
"Where are we?" is the question every campaign gets, several times a day near the end. The Testing Agent's method answers it with four figures. Other methods use other names, and the definitions vary from team to team; these are the ones used here, and the point is that each one is defined, so nobody reads into it more than it says.
| Figure | Definition | It answers |
|---|---|---|
| Preparation coverage | Testable requirements with at least one designed case, over testable requirements | Have we planned to test everything we can? |
| Execution coverage | Testable requirements with at least one case run Passed, Failed or Settled, over testable requirements | How much of what we can test has actually been tested? |
| Progress | Planned cases executed (Passed, Failed, Not applicable, Settled), over planned cases | How far through the campaign are we? |
| Quality | Passed, over Passed, Failed and Settled | Of what ran, how much worked? |
Two details carry most of the weight:
- A blocked case is not executed. It counts in neither progress nor quality: it is still to do.
- A settled case is not a success. It ran, it failed, and someone accepted the deviation. It counts against quality, because the product did not do what was required.
What each figure hides
Each figure, quoted alone, misleads in a predictable way. Preparation coverage at 100% says every requirement has a case, not that any of them ran. Progress at 90% says nothing about whether those cases passed. Quality at 100% on three executed cases out of forty is three cases.
That is why the answer to "where are we?" never starts with a percentage. It starts with what is not done:
- what remains to run, by importance, and which of it needs a person;
- the requirements with no case, and those not testable;
- the open defects, worst first;
- the actions waiting on someone, and how late they are;
- then the figures, side by side, never one alone.
After two days, a campaign reports quality at 100%. What do you need to know before you repeat that figure to anyone?
The course's answer
How many cases it is computed on, and therefore what progress and execution coverage are. Quality is a ratio over executed cases only: 100% can mean three passed cases out of forty planned, with the requirements that matter most not run yet. And whether anything was blocked, since blocked cases are in neither side of the ratio.
| A | How many cases it covers, progress and execution coverage next to it, and what is blocked | ✅ |
| B | "Whether the tests are good" | ⚠️ A fair worry, and it does not tell you what the figure leaves out |
| C | Nothing, 100% is 100% | ❌ It is 100% of whatever ran, which may be almost nothing |