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

Testing error feedback

Testing the user interface for errors is simultaneously far less frequent and far more critical than that of your primary use cases. It is less important because, hopefully, users encounter error conditions far more rarely. However, once they’ve hit an error, they will rely on your interface to correct them and help them achieve whatever goal they were aiming for. While these might be rarer cases, handling them well is vital for users who need assistance. This section considers how to present errors and internal failures, how to find spurious errors, and how to avoid displaying errors in the first place.

Preventing errors

As described in Chapter 7, Testing of Error Cases, your application should catch problems as early and as specifically as possible. If there are problems in the user input, then let the customer know exactly what is wrong – is the entered text too long, or does it contain invalid characters? Is a number field too high or...