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

How to Run Successful Specification Reviews

“He who knows only his own side of the case knows little of that.”

- John Stuart Mill, On Liberty

In the previous chapter, you learned how to develop an excellent feature specification from a short description given by a product owner. However, even with all those details added, your test plan is incomplete. So far, the only inputs into the test plan have been that initial draft and your exploratory testing and ideas. You also have to hear from the developers to understand their choices, the configuration options they added, and the areas they are worried about. From the product owner, you need clarification on any unspecified user-facing questions. The specification review meeting is the place to gather that information.

This chapter will show you how to run a successful review meeting. As with the functional specification, this may be carried out by someone else, but if it isn’t, it’s up to you, as a...