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)
1
Part 1 – Preparing to Test
6
Part 2 – Functional Testing
13
Part 3 – Non-Functional Testing
17
Conclusion
Appendix – Example Feature Specification

Performing systematic testing

The first step for functional testing is to systematically work through the feature specification, expanding each requirement into all the test cases required to cover it. When well-written, with sufficient detail, and each independent of the others, many requirements should need only a single test case to cover them. However, some, especially around error cases or freeform inputs such as textboxes, will require many tests to check all the possible valid and invalid cases.

The feature specification is vital here since it describes all the core functionality. By carefully writing and reviewing the specification, the test plan becomes a secondary document that is easy to prepare. Make sure you use the specification to guide the testing. This section concentrates on the happy path cases and the working routes that exercise the entire feature without hitting errors. Other sections will build on this by adding invalid cases, the performance under load, or...