You’re coming home after a hard day at work. You throw your bag on the couch and grab the two slices of cold pizza left over since last night (you hope), barely feeling the taste of it. With the last bit of energy you throw the box on top of the pile of other boxes from food delivery you have lying around in your room, next to the pile of dirty clothes. It used to be a nice room and you were proud of it, decorated it yourself, and you had friends over for a beer, but now, you’d not invite their dogs over. You promise yourself you’ll clean all that in the morning, and fall asleep.
So you are the person in charge of a software project. It may be something small, an MVP (Minimum Viable Product) or a large enterprise project.
You want it quickly, cheap, and without bugs. I’m not even going to say the “pick two” cliche (there, I said it), but the truth is that too often in the industry, not even two of those boxes are being ticked.
There are many variables affecting the quality of the delivered product. Testing, which is my focus here, is one of the important ones.
How much effort should be spent on testing? There is no silver bullet answer.