For software developers testing their own code or designs; indepdendent testers testing someone else's code; and testers or developers testing bug fixes and other maintenance changes.
This reference presents, in detail, an effective, step-by-step, cost- effective approach to software testing that is based on common practice―with improvements inspired by academic testing research and practial experience. The approach is designed to be gradually adoptable, so that it does not disrupt current work, and it scales down gracefully under schedule pressure. Outlines a systematic process/strategy of software testing that incorporates test design, test implementation, and measurements of test quality. Explains solid testing techniques in detail and shows how to apply them to testing tasks. Answers such questions as: How do I design tests? What are common tester errors, and how do I avoid them? How do I implement tests? How do I know how good my tests are? How do I know when I've tested enough? Features unique coverge of testing bug fixes and other changes.
Brian Marick learned Ruby in 2001 because Dave Thomas and Andy Hunt, original authors of "Programming Ruby," wouldn't let him off a shuttle bus until he said he would. He's been programming in it ever since, and he's made a special effort to teach it to software testers. His previous book is "Everyday Scripting with Ruby," which began as a tutorial for those very testers. He's not a Ruby programmer by trade. He makes most of his money as a consultant in the Agile methodologies. (After getting off the shuttle bus, he was one of the authors of the "Manifesto for Agile Software Development.")