Whitepaper and Slides: Open-Book Testing

By Jon Bach, Managing Test Lead, Quardev, Inc.

No matter what the time and budget of a software development project, testers must understand what the software is supposed to do in order to test it. There are several ways they can do that: attend design meetings, read specifications, talk with the Product Support team, and review the manual, to name a few. Exploring the software is another way to build a model of functionality, but what if two testers have vastly different ways of exploring the software? How do you maintain consistency in how testers build product knowledge? Open-Book Testing means to give testers an open-ended series of questions to aid and coordinate their exploration, much like how college students are given an open-book exam.

Read more about Jonathan's latest testing technique, Open-Book Testing.

Read the paper

See the slides

< More Articles