Lessons Learned in Software Testing: A Context-Driven Approach Bret Pettichord, Cem Kaner, James Bach, Brett Pettichord
Publisher: Wiley, John & Sons, Incorporated

In this process you will also learn a lot more lessons that is not possible in any other way. Name your favorite book on Software Testing? Lessons learned in software testing: a context-driven approach 2. Put simply, software testing is the process of ensuring a program can do what it is designed for. Koen (a winner of ASEE's Sterling Olmsted Award) writes about the pervasiveness of heuristics in all areas of engineering: see his books: Discussion of the Method: Conducting the Engineer's Approach to Problem Solving (2003) and Bret, James and I wrote Lessons Learned in Software Testing. At this point, I think the list is more a collection of fans of Bach & Bolton's Rapid Software Testing approach than of context-driven testing. Lessons Learned in Software Testing: A Context-Driven Approach. A few weeks ago, a colleague of mine tweeted an assertion that the context-driven testing school “censures” people who advocate for best practices. We worked on a number of things, but the principal outcome was a statement of the premises on which Rapid Software Testing—our classes and our methodology—are based. You can find an extensive list of presentations and courses that I've taught, including the slides and speaker notes for many of them, here. Cem Kaner, James Bach, and Brett Pettichord published the first context-driven testing textbook Lessons Learned in Software Testing. Note that the team includes the product owner 6.