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

Evaluating different test environments

For system testing, you need a test environment. Unit testing and some integration testing can be carried out on individual modules and components, but to perform system testing, you need a system to test, as the name suggests. That cannot be development machines where the developers may be making constant changes and it cannot be the live environment, by which time it’s too late to prevent the damage bugs cause. You need a test environment between the development and live installations to perform your testing. If you don’t have one, setting that up is your first task before you can do any testing.

The test environment could be a blank installation that you spin up as needed, picking up the latest code. Alternatively, you could have a staging area or beta environment that constantly runs. Both approaches have different benefits, considered next.

Using temporary test environments

This table shows the advantages and disadvantages...