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

Uncovering hidden defects

Often, testing can be carried out in parallel, with many parts of the test plan conducted simultaneously. As long as they are independent, the only limit on the number of tests you can run at once is the availability of test systems or testers to carry out the tests. When two tests interact, for instance, by requiring mutually exclusive settings, they either need separate test systems, or you need to run them serially, one after another. Testing serially is much slower, and you should avoid it wherever possible.

Another case where testing has to be run serially is when a bug blocks further testing. That first bug must be fixed before you can run tests and find bugs in the remaining functionality. Any issues that couldn’t be tested are hidden behind the first bug.

For example, if signing up new users doesn’t work, then you won’t be able to find bugs when multiple users sign up simultaneously. The bugs with multiple users are hidden...