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.

A 3D scene of coloured blocks and cards. Each test says: what to do, what should happen.
What to do and what should happen.

Writing it

  1. Start from "done"

    One test per must-have.

  2. Write steps and the expected result

    "Sign in, create an invoice for 300, press Send. It appears in the list as Sent."

  3. Add unhappy paths

    What should happen when things go wrong.

  4. Ask Claude for what you missed

    Give it the brief and your list.

A 3D scene of coloured blocks and cards. Unhappy paths: wrong input, no internet, an empty list.
Wrong input, no internet, an empty 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.

ActivityBuild stepA tested, locked-down app

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.