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

[James' Reply: The most interesting The PRISMA Approach, by Erik van Veenendaal. Keyword Driven Automation Framework » As a result, a group of test methodologists (now calling themselves the Context-Driven School) began using the term “exploratory” seeking to emphasize the dominant thought process involved in unscripted testing, and to begin to develop the practice into a This new terminology was first published by Cem Kaner in his book Testing Computer Software and expanded upon in Lessons Learned in Software Testing. A few weeks ago, a colleague of mine tweeted an assertion that the context-driven testing school “censures” people who advocate for best practices. Lessons Learned in Software Testing: A Context-Driven Approach. The customer can then change its capabilities according to changes in the business, and also from learning from how the system is used in reality. Agile Manifesto; XP (Extreme Programming); Scrum; Crystal; Context Driven Testing; Lean Development; (Rational) Unified Process This new movement grew out of the efforts of various people who dealt with software process in the 1990s, found them wanting, and looked for a new approach to software process. Scenarios are credible stories about something that could happen in the future. Kaner is senior author of three books: Testing Computer Software (with Jack Falk and Hung Quoc Nguyen), Bad Software (with David Pels), and Lessons Learned in Software Testing (with James Bach and Bret Pettichord). Maybe more of them will get through Lessons Learned in Software Testing than I assume will, but I wish more short demos or exercises could get dev attention to just educate a little bit more about the range of tests beyond function tests. If you want to know what a Context-Driven tester reads, here it is: A First Course in Statistical Programming . Put simply, software testing is the process of ensuring a program can do what it is designed for. Scenario tests involve scenarios that are likely to motivate a stakeholder with influence to demand that the product be fixed if it doesn't pass the tests. 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.