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

Understanding the requirements format

I don’t care how you format the feature specification document. Feel free to have an overview and an introduction, state the scope and the stakeholders, or add versioning tracking every change. If you find those useful for the time they take to prepare, add that information. If not, don’t.

Many tools let you track requirements more flexibly than having a single document. They have features such as reusing requirements between projects and mapping requirements onto the test cases that cover them. While I’ll refer to the specification as a document here, I recommend that you use these tools since they give you greater control to move requirements around and tie them into your development team’s processes.

If you’re stuck with wiki pages or shared documents until you persuade everyone to change, a few formatting rules will make everyone’s lives easier. The other improvements listed here apply to the...