Lessons learned in software testing

What Hacker News says

1. GrumpyYoungManOct 2022
   Probably my favorite book on software testing would be "Lessons Learned In Software Testing", which is more a discussion about the people and process aspects of software testing instead of specific techniques. If you're interested in testing as a profession rather than merely as a job, it's worth a read.
   thread
2. conjecTechFeb 2018
   There is a class at Georgia Tech I colloquially referred to as "making sure your coworkers don't hate you." It covered design patterns, software testing, and project management. I'd tack on a basic knowledge of databases to that. These are things you can gain a true functional knowledge of in a couple of weeks, and which not knowing might make senior engineers hate working with you.

   So to mimic the class:

   The Mythical Man Month

   Design Patterns - Even if some of the particulars are not as relevant, it still provides a useful framework for thought.

   Lessons Learned in Software Testing: A Context-Driven Approach

   I'd also add Harry Potter & The Methods of Rationality. A lot of engineers can think empirically, but its not their first reaction. Going through this book helped make it second nature for me. Can't remember if a certain data structure is immutable? Now I'll write a couple of lines of code to see rather than go looking for documentation. A lot of big problems start as false assumptions. Having the instinct to think to test them and knowing how to will prevent a lot of wasted effort, regardless of your role.

   How to Solve It by Polya also gets an honorable mention for similar reasons.

   Show morethread
3. MorendilOct 2015
   Point him to "Lessons Learned in Software Testing" by Bach, Kaner and Pettichord: http://www.amazon.com/dp/0471081124

   Also, "manual testing" is a slightly unfortunate monicker for the activity we are discussing. It is bound to generate some degree of incomprehension or even hostility on the part of some people, for no foreseeable benefit. "Testing" will do. It is something you do with your head primarily, your hands being involved to pretty much the same degree that they are in programming (and we don't usually call that "manual programming").

   Show morethread
4. el_benhameenOct 2015
   While other commenters are correct that manual QA is a mindset, there are readings that can help develop that mindset.

   I have new QA engineers read the first five or six chapters of "Testing Computer Software":

   http://www.amazon.com/Testing-Computer-Software-2nd-Edition/...

   to get a feel for the mindset and methodologies and to help them understand what testing can and can't accomplish.

   "Lessons Learned in Software Testing", mentioned by another commenter, is another good resource. Lots of good anecdotes:

   http://www.amazon.com/Lessons-Learned-Software-Testing-Conte...

   Both are a bit dated in some ways ("Testing" has a section on filing paper bug reports), but the lessons and thinking are still highly relevant.

   Show morethread
5. linsomniacMay 2024
   From Wikipedia:

   In Lessons Learned in Software Testing, Cem Kaner, James Bach, and Brett Pettichord provided the origin of the term: "The phrase smoke test comes from electronic hardware testing. You plug in a new board and turn on the power. If you see smoke coming from the board, turn off the power. You don't have to do any more testing."

   https://en.wikipedia.org/wiki/Smoke_testing_(software)

   thread
6. prerokMay 2024
   > In Lessons Learned in Software Testing, Cem Kaner, James Bach, and Brett Pettichord provided the origin of the term: "The phrase smoke test comes from electronic hardware testing. You plug in a new board and turn on the power. If you see smoke coming from the board, turn off the power. You don't have to do any more testing."

   Source: https://en.m.wikipedia.org/wiki/Smoke_testing_(software)

   thread