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

Setup versus ongoing usage

Your product is likely to have two very different classes of user stories: those associated with setting the product up and those with its ongoing usage. In terms of total use, the ongoing cases vastly outnumber the setup ones – that is, unless you’re experiencing massive customer growth and turnover simultaneously.

Despite being the minority of interactions with your product, getting users onboarded takes a disproportionate amount of design time relative to other features. When first using your product, users will know the least but also have some of the most challenging tasks to perform around getting your product ready. Unless they can overcome that barrier, they’ll never become regular users.

You should devote similar proportions of time to testing onboarding tasks as setup tasks. On the plus side, this form of testing needs very little test data or equipment. The whole point is that you are a new user with no prior history...