Series

Manual QA that still matters.

The judgement automation can't replace — written for testers, not for an audit. Automation replaced regression checking, not testing. This series is the manual-QA craft that still carries a release: writing test cases people read, testing vague requirements, scoping regression, and exploratory testing done deliberately.

Who it's forManual QAQA analystsAnyone new to testing

// overview

Automation replaced regression checking — running the same path over and over. It did not replace testing. This series is about the manual-QA craft that still carries a release: the judgement, the exploration, and the communication a machine can't do for you.

It moves from the fundamentals outward: writing test cases people actually read, testing a story when the requirements are vague or missing, scoping a regression pass so it doesn't waste two days, and doing exploratory testing deliberately rather than as “random clicking”.

If you're a manual tester wondering where you fit on an automation-heavy team, this is the answer: the half of testing that was never automatable in the first place.

// reading order

  1. Tutorials·13 June 2026 · 7 min read

    How to write test cases developers actually read

    Test cases that get read are short, scannable, and written for the person who has to act on them. Here is the format I use.

    manual-qatest-casesdocumentation
  2. Tutorials·13 June 2026 · 7 min read

    How to report bugs developers can fix quickly

    A bug report exists to get the bug fixed. Specific title, minimal repro steps, explicit expected-vs-actual, evidence, and environment — the format that prevents "can't reproduce".

    manual-qabug-reportsdocumentation
  3. Field notes·13 June 2026 · 7 min read

    How to test when requirements are unclear

    A field-tested approach for testing a story when the acceptance criteria are vague, missing, or contradictory.

    manual-qarequirements
  5. Opinions·21 October 2025 · 9 min read

    Manual exploratory testing isn't dead — it's underused

    What automation replaced was regression checks — running the same path repeatedly. What it didn't replace, and can't replace, is human intuition trying to break a product.

    manual-qaexploratory-testingopinionculture
  6. Tutorials·13 June 2026 · 7 min read

    A one-hour exploratory test session template

    A charter-driven, time-boxed template for exploratory testing: 5 minutes to charter, 35 to test, 10 to debrief — and notes someone can read.

    manual-testingexploratory-testingtemplatetest-charter

// RELATED QA.CODES RESOURCES

Template

Practice Project

Next seriesRelease readiness