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

Enabling new features

How do you enable new functionality? Some features are simple and stateless, such as a new command in an API, a new button, or a new interface for existing functionality. The current system can continue without these features, and enabling them has little effect on the rest of the system. Stateless features are simple, and you can just enable them and begin testing.

Other features are more complex and stateful, such as database migrations or new forms of data storage. Some require several steps, such as enabling a new system, migrating users onto it, then disabling the old system. Breaking changes on interfaces need all downstream systems to be ready for the change. This section considers the complexities around enabling and disabling such stateful features.

Stateful features might be enabled with a feature flag or be available immediately after an upgrade. For this discussion, these two methods are equivalent: all you need is a way to enable the feature...