SQLAuthority News – Book Review – A Practitioner’s Guide to Software Test Design

A Practitioner’s Guide to Software Test Design (Hardcover)
by Lee Copeland (Author)

SQLAuthority News - Book Review - A Practitioner's Guide to Software Test Design SoftwareTest

Link to Amazon

Short Summary:
A Practitioner’s Guide to Software Test Design is one book containing all the important latest test design approaches. This book makes life of software tester very easy. Software tester can find all the information in this book instead of searching through hundreds of books, periodicals and websites.

Detail Summary:
In large system it is very important to choose test cases as well carefully find defect which can result in significant losses to organization. A Practitioner’s Guide to Software Test Design is one book which only focuses on software test design. This book avoids all the distractions of less important topics such as test planning, test management, test team developments etc and focuses on core concept of software test design. This book contains detailed examples and step by step instructions about how to design efficient test designs.

Some of the techniques used in this book are classics and well known throughout the testing and developing community. Many of the techniques are not widely used but should be more in practice as they are very effective as well. The balance of breadth and depth of all this techniques makes this one book must read by all software testers.

Each test design technique is approached from practical view point as well it contains important theories along with it. Simple example following with in depth details is what makes this book a true page turner for readers. Each chapter contains summary of its key points, exercises and references. A typical user of this book will be able to start on project right after reading this book.

What makes this book a must read is it’s extremely fluid and interesting methods to explain concepts. Author gets his point through using humor in many areas. Let us see one example from Chapter 16th – When to Stop Testing.

When to stop testing:
You have met previously defined coverage goals
The defect discovery rate has dropped below a previously defined threshold
The marginal cost of finding the “next” defect exceeds the expected loss from that defect
The project team reaches consensus that it is appropriate to release the product
The boss says, “Ship it!”

Rating: 5 Starts

Summary:
This book very well achieves what its goal is about analyze, design and choose such subsets, to implement those tests that are most likely to discover defects and help identify potential pitfalls.

Reference : Pinal Dave (https://blog.sqlauthority.com)

, , ,
Previous Post
SQLAuthority News – Download Microsoft SQL Server 2000/2005 Management Pack
Next Post
SQLAuthority News – Thank You to Blog Readers

Related Posts

Leave a Reply

Menu