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

Testing maintenance operations

While only internal staff perform maintenance operations, they are often among the riskiest on your system. Upgrades and configuration changes are the sources of most outages, in my experience. You’ll need to test the content of each modification, but this section considers changes in the abstract – what should you try for every upgrade?

Real-world example – Which version is that?

I once tested a minor plugin that supported our main product, which was installed locally on a desktop. We shipped the first version, then a couple of maintenance releases. Only after a couple of versions did we realize there was a piece of functionality that we’d missed. Users kept reporting issues that we thought we’d already fixed. Were our fixes failing, or had the user not upgraded? The first question that the support team asked was what version they were running.

Unfortunately, the plugin didn’t report its version number...