AI-Augmented QA & Modern Tooling · Lesson 2 of 5

Critique and Prune — Where AI-Generated Tests Go Blind

Getting the AI to generate cases is the easy part. The skill interviewers actually care about is what you do next — reading the output with a critical eye and cutting what's weak.

By Shahriyar · Updated

The idea, in one line

Treat every AI batch as a rough draft, not a finished answer. Your value is knowing, from memory, the exact places AI reliably goes blind — and filling those gaps yourself.

The four blind spots AI keeps missing

AI drafts strong happy-path and simple-negative cases, then skips the ones that catch real production bugs. Learn these four by heart:

See it work

One practical move: tag each generated case with the angle it claims to cover, then check the batch against a required list. Anything missing is a gap a human must fill.

▸ try it
# The angles every batch should cover.
REQUIRED = {"happy", "boundary", "negative",
            "security", "locale", "timezone", "multi_tenant"}

def coverage_gaps(cases):
    covered = {c["angle"] for c in cases}
    return REQUIRED - covered   # what's still missing

def test_ai_batch_has_no_blind_spots():
    ai_cases = load_generated_cases("reset_password.json")
    gaps = coverage_gaps(ai_cases)
    # Fail loudly so a human fills the gaps in
    assert not gaps, f"AI missed angles: {sorted(gaps)}"

Read it top to bottom: you list the angles you expect, subtract the angles the AI actually covered, and whatever is left over is your to-do list.

Advanced — the gap list is your story

The Thoughtworks study found roughly a quarter of generated cases were ambiguous, and the harder, non-functional angles were skipped unless demanded. So write down what the AI missed. That gap list is the concrete proof of your judgment — and it's the exact story you tell an interviewer about how you review AI work.

Grounded in Thoughtworks' study on AI-generated test cases and industry guidance on validating them

All lessons in AI-Augmented QA & Modern Tooling

  1. Turn a User Story Into Test Cases — Prompt It Like an Engineer
  2. Critique and Prune — Where AI-Generated Tests Go Blind
  3. AI Coding Assistants — What to Hand Off, What to Review
  4. Self-Healing Locators — and the False-Pass Risk
  5. Ship an AI-in-the-Loop Suite Through CI — and Tell the Story