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)
1
Part 1 – Preparing to Test
6
Part 2 – Functional Testing
13
Part 3 – Non-Functional Testing
17
Conclusion
Appendix – Example Feature Specification

Determining what to check

So far in this chapter, we have considered many different tests to run, but we haven’t covered the vital next step in the test process—what should you check to ensure the test passed? There are many levels to consider. Most superficially, you can tell whether the application continues to work as described. In our example of a signup web page, does the user receive an email after entering their address? For everything written and saved, you can check where it is subsequently displayed to the user. Is it correct in all those places?

For changes that transition your program into a new state, does it make that transition correctly in all cases? For inputs that trigger other changes in the application, do you have a complete list of those changes so you can check them all?

The feature specification should include the user experience for each output, so you’ll need to refer back to that extensively for these checks. If anything is missing...