What is a test plan?
A test plan lists what to test, how, on which systems and what result counts as a pass, so anyone can repeat it.
1. Each test case is a recipe
A test plan is a set of test cases. Like a recipe, each gives the setup, steps, expected result and pass rule, so anyone can tell a pass from a fail.
2. Every promise gets a test
Each test comes from a promise in the feature's design, called a requirement. Every promise links to at least one test.
3. Which systems to cover
The plan lists the test computers (systems), settings and software versions to cover. Laptops are tested plugged in (AC power) and on battery: they behave differently.
4. Test it off, test it hard
A baseline run with the feature off shows what the feature changes. Stress tests push hard, such as heavy work for hours or 1,000 restarts.
5. Experts check it first
Chip designers and firmware engineers review the plan before testing starts. They catch missing or wrong tests early.
Words to know
- Test case
- One test, with its setup, steps, expected result and pass rule.
- Requirement
- A written promise of what a feature must do.
- Expected result
- What should happen when everything works.
- AC power
- Power from a wall socket, through the charger.
- Baseline
- The same test with the feature off, to compare against.
- Stress test
- A test that pushes a system hard, with heavy work for hours or one step repeated many times, to find rare failures.
- Firmware
- Software built into the hardware that runs it from inside.
Where you meet it at work
Writing, reviewing and running test plans is a core part of the job. A clear expected result makes every later debugging step easier.
Check yourself
Why does every test case need an expected result?Think first, then tap to see the answer.
Without it, nobody can tell if the test passed or failed.