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

Prescriptive and descriptive test steps

When writing manual tests, you can choose how precise your descriptions are. Either you can specify exactly what to do and how to do it, or you can only say what to do, leaving the details for each tester to decide.

For instance, a descriptive test might say: “On the user settings page, upload an avatar .jpeg image between 100 KB and 5 MB in size.”

Note that while there are instructions on what to do, the tester can use any image they like that matches those criteria. In contrast, a prescriptive test might say exactly which file to use: “On the user settings page, upload /fixtures/image1.jpeg as an avatar image.”

Here, image1.jpeg is a suitable image within that size range. If you are testing a text input, you can specify the exact strings to try or just describe what contents they should have.

Prescriptive tests are also known as low-level test cases, with complete detail on what to do and how to do it...