Software testing books
Six that come up again and again, with an honest line on who each one is actually for.
No links here, deliberately. Editions vary, prices vary wildly by region, and several of these are worth buying second-hand. What follows is what each book is for, so you can pick one rather than acquire five.
Books are the slowest resource on this site and the only one that changes how you think rather than what you can do by Friday. Documentation tells you how a tool behaves; a good book tells you which question you should have been asking before you opened the tool. The six below have survived a decade of the industry reinventing its tooling, which is the closest thing to evidence this category can offer.
The failure mode with reading lists is buying four books and finishing none. Every entry below has been recommended by working testers for years; any one of them, read closely, is worth more than the whole list skimmed.
If you have to pick one
2 entries-
Agile Testing — Lisa Crispin and Janet Gregory
BookHow testing fits into a team that ships continuously, rather than a phase at the end. The agile testing quadrants come from here. The right first book for anyone whose real problem is organisational rather than technical.
-
Explore It! — Elisabeth Hendrickson
BookThe best practical book on exploratory testing: charters, heuristics, how to keep notes, and how to report what you found so somebody acts on it. Short and immediately usable, which is rare in this field.
For the craft
3 entries-
Lessons Learned in Software Testing — Cem Kaner, James Bach, Bret Pettichord
BookTwo hundred and ninety-three short lessons, each a page or less. Open it anywhere. The closest thing the field has to a book of aphorisms that are actually useful.
-
Perfect Software and Other Illusions About Testing — Gerald Weinberg
BookShort, human, and honest about what testing can and cannot tell anyone. The book to read when a manager asks why you did not catch something.
-
Specification by Example — Gojko Adzic
BookWhere the BDD material on this site ultimately comes from: case studies of teams using concrete examples as the specification. Read it before adopting Gherkin, not after.
For testers who read code
1 entry-
Growing Object-Oriented Software, Guided by Tests — Steve Freeman and Nat Pryce
BookHow tests shape a design when they come first. Dense, and the long worked example in the middle is the part that teaches. Best read with an editor open.
Reading is the slow way to learn how a suite behaves. Record one against your own app, free, and watch what the report says.