Information packed
Rating:
5 / 5
Most texts on software testing have a chapter or two which describe test design techniques. This is the first text that is devoted exclusively to this subject. There is little in the way of theory. The text is practical and provides the software test professional with clear explanations and examples of test techniques that have been proven to be effective.
Although Copeland covers both black box (behavioral) and white box (developer oriented) test techniques, the majority of the test design techniques described are black box. Each technique is explained along with its applicability, advantages/disadvantages, along with references for more information.
For what can be a dry subject, Copeland effectively used humor to make this book very readable.
I also appreciated the chapter summaries, key points in the margins, and a thorough works cited -- including several web articles. Highly recommended.
A Critically Important Read for Software Test Engineers
Rating:
5 / 5
Lee Copeland's book, "A Practitioner's Guide to Software Test Design" provides an easily read introduction into a critical but often ignored subject. As those familiar with the IEEE Standard for Software Test Documentation (IEEE-Std-829) know, Test Design is the first step in turning the "What" of the Test Plan into the "How" of test execution. The IEEE Test Documentation lifecycle is Test Plan - Test Design - Test Case Development - Test Procedure Development - (Test Execution) - Test Summary Report creation. Many test engineers proceed directly from Test Planning into Test Procedure creation, and do Test Design implicitly as opposed to explicitly. This can have a negative impact on an effective test program. This book clearly shows how to implement the test design process described in Drabick's book "Best Practices for the Formal Software Testing Process".
Lee's book provides a concise description based on excellent Case Studies of Black-Box (Requirements Focused) test techniques, moving from the simple (Equivalence Class and Boundary Value testing) to the more complex (Domain Analysis and Use Case testing). He provides the best description I've seen of test case development using orthogonal arrays. Lee then addresses White-Box (Structural Focused) testing, showing how to approach Control Flow and Data Flow testing. Again, he has the best description with illustrative examples of Data Flow testing that I've ever seen.
Lee then describes two Test Paradigms: Scripted Testing and Exploratory Testing that appear to be significantly different, and shows how the two can be used together for even more effective testing. That's the way I've always done testing, by the way.
His Defect Taxonomies chapter provides valuable insight on how to use such information in test design (I never thought of that), and he concludes with a short chapter that addresses the critical question When to Stop Testing.
The Case Studies on "Brown & Donaldson" and "Stateless University Registration" are effectively used to provide valuable insight into the techniques.
This book would be a good read in combination with the book from Rick Craig and Stefan Jaskiel, "Systematic Software Testing".
In summary, this book is well done, is an easy read, and should be read by every test engineer.
Page turner tech book? You bet!
Rating:
5 / 5
The top two software testing books that I recommend are Systematic Software Testing (ISBN 1580535089), and this gem. Whereas the first book gives a complete process and accompanying practices, this one focuses on a collection of highly effective techniques that every test professional should have in his or her toolbox.Copeland starts off with an overview of testing as a process, followed by case studies. These lay the foundation for the techniques for which a chapter is devoted to each technique. The chapters on the techniques are divided into collections of techniques that are most effective for blackbox (seven) and whitebox (two) testing. The next chapters are devoted to scripted testing with an emphasis on IEEE 829, exploratory testing, and test planning. The book wraps up with an outstanding chapter on software defect taxonomies, advice on when to stop testing, and case studies. So why did I state this book is a page turner? Copeland has masterfully used humor, statements that catch you off guard, and a warm conversational style to hold your attention. Among the priceless gems of humor are the off-the-wall quotes that he uses in front of each chapter. One of many examples of how he holds your attention by catching you off guard is in Chapter 6 on pairwise testing: 'Why does pairwise testing work so well? I don't know', which he then follows up with one of the most cogent explanations of the technique I've had the pleasure of reading. As an aside, his treatment of pairwise testing - and the power of that technique - is reason enough to read this book. Another aspect of this book I like is the thoroughness with which he presents techniques. This includes citing the work of other well known practitioners, using case studies, summaries, practice scenarios, and additional references for each chapter. Copeland also has a talent for clearly articulating and conveying complex topics and concepts, adding to this book's value as both courseware and a working reference. If you are a software testing professional, or you are responsible for teaching this discipline this is one of the top books in my opinion. It is not as wide in scope as Software Testing: A Craftsman's Approach (ISBN: 0849308097), but it makes up for that by covering the essentials in the clearest possible manner.
|