Skip to content
All books
Stage 5 · Quality

The second pass: catch the bugs your QA can't

Why a fully tested release still ships an obvious bug, and the 30 to 60 minute second pass that catches it.

About the book

Some escaped defects are not caused by weak formal testing. They survive because the people closest to the product become fluent in its assumptions.

The Second Pass adds one fresh person, thirty focused minutes and five unscripted moves after formal QA and before release.

The method was born in production work at Cisco and is designed to complement a strong QA process, not replace it.

What you get

  • Why familiar testers miss obvious things, and the five shapes of a human-factor escape
  • The five moves of a second pass: box the time, aim at one thing, throw away the script, play the bad user, report fast and cheap
  • Who runs it and when, with two worked walkthroughs
  • Three numbers to measure the drop in escaped defects
  • A one-page field guide and a first-pass worksheet

A page from the book

Copied as printed, so you can judge the format before you buy.

A second pass, start to finish, page 17

The spreadsheet import

One more, shorter, so you can see the method flex to a different target. A release includes a new "import contacts from a spreadsheet" feature. Formal QA has signed off with clean test files. The likely shapes this time: real-world input, because import features live and die on filthy data, and the interrupted flow, because imports take time and time invites interruptions. The fresh tester builds the ugliest spreadsheet they can in five minutes: a name with an apostrophe and an accent, a row in another alphabet, a cell holding an entire pasted paragraph, a duplicate email, a blank line in the middle. Then they start the import and close the browser tab halfway through. Result, in the walkthrough I have in mind: the ugly rows imported fine, which was a pleasant surprise, but the interrupted import left half the contacts in the list with no record that the job had died, so a real user would have trusted a half-empty import without knowing it. Ten minutes, one report, one quiet Monday saved. Different feature, different shapes, same five moves.

What is inside

  1. The bug that passed every testp. 6
  2. Your QA isn't broken. It's tired.p. 8
  3. The human factor, up closep. 10
  4. The five moves of a second passp. 12
  5. Fresh eyes, right timingp. 14
  6. A second pass, start to finishp. 16
  7. Measuring the dropp. 18
  8. Rolling it out without threatening anyonep. 20
  9. The one-page field guidep. 22
  10. Your first pass, this weekp. 23
  11. Notes and sourcesp. 24

What readers say

  • “Very detailed explained, thank you!”

    Marina S.
    Gumroad verified purchase

Reader reviews from Gumroad, word for word.

Who this is for

This is for you ifHappy-path review passes while interruption, retry and release failures remain invisible.

  • Engineering Manager
  • QA Lead
  • Head of Product
  • Hands-on tester

Not for

  • Have no first QA layer
  • Want to replace formal testing
  • Need another automation framework
The library pathWhere this fits
  1. 01Get foundThe Silent Rejection
  2. 02Build the record and negotiateThe iOS Engineer playbook · Leverage
  3. 03InterviewThe iOS interview blueprint · The senior signal · Top 300 React Native interview questions · 500 Flutter interview questions · The senior SDET interview handbook
  4. 04Answer practice and live roundsThe 24-hour iOS interview answer book · The 24-hour Android interview answer book · Share your screen
  5. 05Architecture and qualitySwiftUI under load · Mobile System Design blueprint · Security is a feature · The second passYou are here
  6. 06Staff systems and ownershipAltitude · Ticket taker, outcome owner
  7. 07Build with AIBuild with your brain on (coming soon)
  8. 08LeadLeadership blueprint (coming soon)
  9. 09ArchitectArchitect blueprint (coming soon)
Portrait of Mike Salari

About the author

Mike Salari

Staff Mobile Engineer · Mobile Architect · Technical Author

I wrote this from a lightweight practice I watched work at Cisco on top of an already strong QA system. The value came from fresh eyes, not more ceremony.

15 years building production mobile software, with experience across Apple, Adobe, Cisco, Mastercard and Visa. 500+ technical interviews from the hiring side.

Read the full story

Before or after you buy

Not ready yet? Use the second-pass field card →

Already own it? Turn the repeated second-pass finding into a team standard or automated check.

Run one second pass before the next risky release.

Give a fresh pair of eyes thirty minutes to find what familiarity made invisible.

Share this book