liveBook · Manning

Manual testing

As explained in Vibe Engineering

Manual testing is the evaluation of software behavior by a human executing and inspecting test procedures rather than automated test code.

Manual testing is focused human exploration of running software. Its distinctive value is pattern recognition: a person can notice that an output violates an expectation they never explicitly encoded as a test. section 8.3.1

A malformed heading reveals an unknown edge case

A markup converter may correctly turn # Header into <h1>Header</h1> and ## Header into <h2>Header</h2>. Trying #### exposes <h3># Header</h3>, prompting investigation of a failure that predefined tests might not include. section 8.3.1

Use manual testing as reconnaissance before committing to automated verification:

  • Spend roughly 10–15 minutes exploring each significant piece of AI-generated code. section 8.3.1
  • Start with the happy path to establish whether the basic behavior works. section 8.3.1
  • Try unusual inputs, inspect the output, and follow unexpected results until the behavior becomes understandable. section 8.3.1
  • Use the resulting mental model to choose automated tests that cover meaningful edge cases and failure modes. section 8.3.1

Manual testing is neither a complete verification strategy nor disposable overhead. It does not scale like automated tests, but it helps reveal what the tests should specify. Tests then express behavioral contracts rather than merely confirming implementation details. section 8.3.1 section 8.3.7

UI work is especially vulnerable when coverage is weak: human involvement may be needed during migration, while generating controller and UI tests reduces continued reliance on manual checking. section 2.7

How Vibe Engineering covers it

How deep it goes
Explains rationale, timing, happy-path and edge-case exploration, then stops short of treating manual testing as scalable verification.
Examples
Uses markup-heading inputs and UI migration with limited coverage as concrete cases for exploratory human checking.
What you can do after
Practice/perform focused exploration, recognize unexpected behavior, and turn observations into stronger automated tests.
How it connects
Connects manual testing to automated testing, unit tests, test-driven prompting, coverage, snapshot testing, and behavioral contracts.

Also explained in

Compare how 5 books explain manual testing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.