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


In this chapter, you have learned the key considerations when performing black-box functional system testing. This is the core of the testing since it ensures that all the main behavior of this new feature is correct, and further testing will build on these results. If the feature doesn’t work correctly even once, then you can’t check the complete user experience or its behavior under load.

Black-box testing needs to systematically cover the entire feature specification while also extending it by trying out ad hoc cases that weren’t explicitly listed. You should also maintain a sense of curiosity to see what happens as you step through the feature’s different states. You find all the best bugs when you go off the test plan, so always extend the cases as written to try new combinations and check other outputs.

This chapter reviewed the various ways to approach black-box testing, from API and CRUD testing, negative testing, and identifying worst...