Plan before code

You will learn

How a verification plan is a checklist that a command can sweep and sign.

A test plan written after the code is a description of what the code does; written before, it is a claim the code must live up to. In this repo the plan is a spec, and a command sweeps it. The widget is that sweep for the bench tools: 14 of 14 pass their own self-tests in one run -- decode 18/18, repin 17/17 -- and any tool that cannot check itself is listed, not waved through. The lesson's spec is build_verify: the checklist of what a build must show before anyone calls it done.

Open the interactive lesson →