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

Defining test cases

You will be running many test cases as part of your testing, so it’s important to be clear about exactly what they entail. Each test comprises four elements:

  • Prerequisites
  • Setup
  • Procedure
  • Result

First, you must set up the necessary prerequisites: are you running the correct services with the correct version and configuration? It’s obvious, but it’s easy to miss a critical step and waste test time. The upcoming Setting the correct version, configuration, and environment section describes testing prerequisites in more detail. Those only need to be prepared once for a whole series of tests.

For each test, you need to make sure the setup is correct. Do you need a user or a particular set of data, or is the requirement explicitly to start without any information? Consider the initial state you need for your test and make it explicit. The trick is to make your assumptions clear. There are an infinite number of variables...