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

Using cause-effect graphing

In the preceding example, application support depended on which operating system and web browser you were using. This can be visually presented in a cause-and-effect graph, which lets you visually display relationships between different variables and specific outcomes. These use standard logic operators of AND, OR, and NOT. The following diagram displays an AND relationship:

Figure 5.1 – AND relationship between two variables and an effect

These diagrams use traditional symbols representing the logical operators:

Figure 5.2 – OR relationship between two variables and an effect

The AND and OR operators can take two or more inputs and have their usual truth table outputs. The following diagram displays a NOT relationship:

Figure 5.3 – NOT relationship between variable A and an effect

Using this technique, you can map complex relationships between inputs and outputs...