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

Mapping dependent and independent variables

Glaring bugs that happen under a wide range of circumstances are easy to find, even with exploratory testing. If the Logout button never works, you will see that the first time you log out. However, if it usually works but only fails on a certain web browser, a certain browser version, or only after you have changed the browser window size, you might not find the issue. If you don’t test those situations, the Logout button will work in your test. Bugs that only occur under certain circumstances, are much harder to find: you can do X, and you can do Y, but you can’t do X and Y together.

Bugs that depend on multiple variables are challenging to find because the test plan you need is huge. First, you have to identify the variables affecting your system. Some essential variables will have far-reaching effects, such as the operating system you’re running on or the web browser you are using. Those are common, but also consider...