Book Image

Software Test Design

By : Simon Amey
Book Image

Software Test Design

By: Simon Amey

Overview of this book

Software Test Design details best practices for testing software applications and writing comprehensive test plans. Written by an expert with over twenty years of experience in the high-tech industry, this guide will provide you with training and practical examples to improve your testing skills. Thorough testing requires a thorough understanding of the functionality under test, informed by exploratory testing and described by a detailed functional specification. This book is divided into three sections, the first of which will describe how best to complete those tasks to start testing from a solid foundation. Armed with the feature specification, functional testing verifies the visible behavior of features by identifying equivalence partitions, boundary values, and other key test conditions. This section explores techniques such as black- and white-box testing, trying error cases, finding security weaknesses, improving the user experience, and how to maintain your product in the long term. The final section describes how best to test the limits of your application. How does it behave under failure conditions and can it recover? What is the maximum load it can sustain? And how does it respond when overloaded? By the end of this book, you will know how to write detailed test plans to improve the quality of your software applications.
Table of Contents (21 chapters)
Part 1 – Preparing to Test
Part 2 – Functional Testing
Part 3 – Non-Functional Testing
Appendix – Example Feature Specification

Countering arguments against specifications

I’ve encountered various reactions to specification documents over my years in the software industry. Usually, people’s reactions are positive, or at least hopeful. Most people would love to have a clear description of the feature under development, but between changing priorities and a lack of time, specifications can be challenging to produce in practice. Other people are more actively negative and argue for spending valuable project time elsewhere. As you can tell, I am firmly in favor of specifications, so here are some anti-specifications arguments and some counterarguments against them.

“This feature is too small to be specified”

Sometimes, a feature is so small that it hardly seems worth writing a specification for it. If a feature is obvious and everyone seems to know what it does, why spend the time writing that down? Some changes are so small that there seems to be nowhere for surprises to hide...