We asked on Twitter âWhat 3 testing books would you recommend to a tester?â Here are some of the replies - maybe a few to add to your reading list?
The Testability Book by Ash Winter and Rob Meaney is shaping up very nicely!
The Phoenix Project
Agile Testing - Lisa Crispin/Janet Gregory
Explore It! - Elisabeth Hendrickson
Perfect Software, And Other Illusions about Testing - Jerry Weinberg
âDesigning Deliveryâ by Jeff Sussna.
Thinking, Fast and Slow
50 Quick Ideas to Improve Your Tests
Writing Great Specifications: Using Specification By Example and Gherkin
How Google Tests Software
Antifragile by Nassim Nicholas Taleb
Test Design by Dr Cem Kaner
Dear Evil Tester
Lessons Learned in Software Testing
More agile testing by Lisa Crispin & Janet Gregory
A Practical Guide to Testing in DevOps by Katrina Clokie
Art of Deception
Art of Intrusion
Ghost in the Wires
âIgnorance: How it drives scienceâ by Stuart Firestein
âLateral Thinkingâ by Edward De Bono
âInfluence: The psychology of persuasionâ by Robert Cialdini
Perfect Software - And Other Illusions About Testing
How to test by Mike Talks
Thinking in Systems - a primer (meadows)
âThe Invisible Gorillaâ by Christopher Chabris/Daniel Simons
âThe Design of Everyday Thingsâ by Donald A. Norman
âHow to Read a Bookâ by Mortimer Adler
âPerfect Software: and other illusions about Testingâ by Gerald Weinberg
An Introduction to General Systems Thinking, Gerald M.Weinberg
Exploratory Software Testing, James A. Whittaker
Lessons Learned in Software Testing: A Context-Driven Approach, Bret Pettichord, Cem Kaner, James bach
Pragmatic Software Testing: Becoming an Effective and Efficient Test Professional
Donât Make Me Think
âHands-On Mobile App Testingâ by Daniel Knott
Beautiful Testing
Pragmatic programmer by Andrew Hunt and David Thomas.
âA practitionerâs guide to software test designâ by Lee Copeland
Thank you for arguing
Patterns of enterprise application architecture
Agile testing a practical guide for testers and agile teams
Itâs nice to see a list of recommended books but It would be even better to hear why people are recommending specific books and what value it brought to them in practice. As a relatively new tester, there is a wealth of information out there and I just donât know what to focus on.
Good question! The answers may be as diverse as the list. People new to testing may benefit from books by other testers (e.g., authors such as Crispin, Kaner, Hendrickson, et al). People who have been in testing for a while may venture into books that focus on the experience of testing (e.g., authors such as Chabris/Simons, Weinberg, Kahneman, et al).
Perhaps you might choose one or two from this spectrum to determine what else you want to read; perhaps you may see yourself in at a certain point in your career and make a selection. Regardless of how you choose, I encourage you to take a reading journey!
For me, I found The Efficiency-Thoroughness Trade-Off to be really useful in giving a mindset of how deep to test and how to define âenoughâ.
Evil by Design really helped me to advocate for users. E.g. is a customer likely to return to our site if they feel that they have been tricked into spending money or giving personal details? Probably not
Thanks @heather_reid the moderator, thatâs two on my list I can initially look into and focus on. Looked on goodreads and The Efficiency-Thoroughness Trade-Off is only 150 pages which is nice and short. I will definitely get back to you if I put any of that into practice. Defining âenoughâ is definitely important to save time in testing.
I recommended the Lessons Learned in Software Testing: A Context-Driven Approach (Bret Pettichord, Cem Kaner, James Bach) book for the reasons below:
It is written for folks who have been in software testing for a while, which is the case with me
There is little hand-holding, i.e. the book is low on fluff, itâs about as terse a book as you can read, but in a good way, i.e. it is all the more readable and powerful because of it
It is written by authors who are vastly experienced in software testing and it is literally the collected wisdom of their experiences
It has a wide spread of knowledge, not specific to any one aspect of software testing, so itâll give me ideas on stuff that despite me being in software testing for a while I may not have come across so much, e.g. test strategy and growing the team
âLeading Quality: How Great Leaders Deliver High-Quality Software and Accelerate Growthâ
by Ronald Cummings-John and Owais Peer
I feel like this is a book that everybody in the software industry should read at some point in their career