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

Understanding equivalence partitioning

It is impossible to test every possible input into your system, so we have to group them into categories demonstrating the behavior of a whole class of inputs. You are undoubtedly already doing that within your test plans, and its official name is equivalence partitioning. By considering it in the abstract, you can learn how to identify possible test cases quickly and completely.

For instance, to test whether a textbox can handle inputs including spaces, we could use the string “one two”. This string is an example of all possible strings that include a space between words. They are all equivalent, so we have partitioned them together, and that example is our single test to check the whole group. The following example strings test other partitions:


Example test

Strings including spaces