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

Why do we need a specification review?

The goal of the specification review meeting is to agree on all the requirements for this feature. By the end of the meeting, you should know exactly what the feature specification should say, even if it’s not fully written up yet. Armed with that agreement, the test and development teams know exactly what they should deliver.

The specification review requires getting the right people to the meeting and giving them sufficient time to prepare. They may or may not take advantage of that time, but it’s important to offer it.

Of course, you can have many other discussions during the feature development aside from the review meeting. Keep communicating before and after review; this meeting isn’t a replacement for that. However, the review meeting serves as a final, systematic check that the specification is complete and ready to go.

In my experience, developers are only too happy to have a tester checking that their feature...