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

Opening the black box

The most valuable part of the specification review is quizzing the developers on the extra work they had to do. Which special cases did they have to write additional code for? Explicitly ask that question because it may not be evident from either the product owner requests or your exploratory testing what work has been necessary.

You can invite the developers to present the architecture to discuss how the different sections work together and how this feature was implemented. This loses the naivety that was helpful during exploratory testing but, at this stage, it’s much more important to be an expert in the workings of the feature.

Understanding the architecture helps explain which variables are independent of each other and can be tested individually and which you should expand out to test the entire matrix of possibilities. It also helps show areas of the test plan that need to be covered in detail and which can be checked with a single test. This...