Vibe Coder · Unit 13: Testing and Security · Lesson 1 of 11
A test plan
A test plan is a list of things your product must do, written so anyone can check them. Build it from your "done" sentences.
Read the short notes and pictures.Do everything inside a blue frame.
A list you can run
Testing is not a feeling that things seem fine. It is a written list of steps and expected results that you, or anyone, can run in the same way each time. For a first product, a page of manual tests is enough.

Writing it
Start from "done"
One test per must-have.
Write steps and the expected result
"Sign in, create an invoice for 300, press Send. It appears in the list as Sent."
Add unhappy paths
What should happen when things go wrong.
Ask Claude for what you missed
Give it the brief and your list.

Running it
Before every release
All of it.
On a phone and a laptop
And a second browser.
Record failures
As bugs, in your four-part format.
Write your test plan
Create "Test plan" with one test per must-have and at least five unhappy paths. Run it once and log every failure as a bug.
Done when
You will add to this list in every lesson of the unit.
Keep these
- A test plan lists steps and expected results.
- Build it from your done sentences.
- Include unhappy paths.