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

Test prioritization

The ideas in this section, and all the following chapters of this book, describe a gold-plated, exhaustive test plan that will comprehensively test your product or new feature. You should definitely consider all the test cases described here, but that doesn’t mean you should perform them all. You will be constrained by the available time and resources, which will vary depending on how critical the software is.

Test management is beyond the scope of this book, for instance, how to organize a test team, which roles should perform which tasks, how testing should fit into release cycles, and many other considerations. Here, I am solely concerned with designing test plans and the tests to run. That means I will list many tests you should consider, many more than you will be able to run in practice. You must choose which to carry out.

Even if you don’t run tests, it’s important to be aware of those you have left out and consciously decided not...