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

Requirement priority

All requirements are not equal, and the product owner should assign a priority to each one. That will let the development team know their relative importance so that they can make informed choices when they have to make inevitable tradeoffs.

I won’t describe that process here; instead, I focus on what you need for testing. Once the priorities have been decided and the technical limitations and opportunities have been explored, you need a final description of what will be shipped in this release. As a tester, your job is to make the specification binary – whether a requirement is included or not. Product owners and developers work in the gray areas of deadlines and feature estimates, so it’s your job to make the outcome black and white.

Feature prioritization and estimation are skills in their own right, but they are beyond the scope of this book. Here, I will concentrate on describing the features that made the cut by being clear on...