Technical requirements
The best way to get value out of this chapter is to consider the ideas while considering an actual, recent software project. By thinking about how the work was done (the accident) versus what needed to be done (the essence), you will be able to do a thought experiment about what could have been done. This means you will be able to achieve a higher level of cognitive work by analyzing testing ideas. Without that, you will be stuck more at the knowledge and comprehension levels. While there are no hardware or software requirements for this chapter, the ability to read simple software code will be helpful for the Coverage – did we test the right things well enough? section. The longest program in that section is nine lines of code, and we will provide a comprehensive explanation.
Our journey begins with understanding recipes.