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

Running the meeting

The meeting format is simple enough – step through the feature specification, read each requirement to see if there are any disagreements, and sign it off. Was it the behavior the product owner wants? Has the developer implemented it (or have they agreed to implement it)? This is a form of static testing – testing without running the code. This lets team members step through design documents, technical specifications, or, in this case, functional specifications to look for errors or issues. This contrasts with dynamic testing, where you run the code to see how it behaves in practice. Only this chapter, Chapter 2, Writing Great Feature Specifications, and parts of Chapter 6, White-Box Functional Testing cover static testing; the remainder of this book focuses on different types of dynamic testing.

With a large specification that you are already familiar with, you may find it tempting to breeze through the requirements quickly. Don’t. Take...