A formal testplan is a short list of obligations, each with its evidence, not a pile of assertions. It says which requirements get a proof and which stay with simulation, in which order the harness is built so every stage can be checked, and what counts as done per row. This topic makes those three decisions on the register block and the skid stage, both small enough to check by hand and real enough to hurt when they are wrong.
Lesson | After it you can... |
|---|---|
Sort requirements into formal-shaped and simulation-shaped, and defend the split. | |
Bring a harness up stage by stage, with a checkable gate at each stage. | |
Write a complete plan with owners and evidence, and check it mechanically. |
Suggested order: top to bottom. Selection first, then the staged build, then the full worked plan. The later topics assume the harness order and the evidence vocabulary from here.
The requirement, the property that checks it, the trigger cover that shows it can fire, the owner, and the evidence expected at signoff.