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

Part 2 – Functional Testing

Once you have gathered detailed information about the new feature from exploratory testing, feature specifications, and test plan reviews, testing can begin in earnest. The first tests to write and perform are those assuming no knowledge of the system – black-box testing – in which the tester naively attempts to use the feature like a new user. That is followed by white-box testing, which is informed by knowledge of the underlying code to ensure that all code paths have been checked.

As well as the working cases, testing always needs to consider the error cases, invalid inputs, and internal failures, followed by user experience testing. Even though a feature may work, it may be difficult for users to learn or use. It’s a tester’s job to highlight those weaknesses, which have a different set of considerations. The feature must be tested for security weaknesses, and you need to check the logs and event metrics. With all...