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

Fixing incorrect requirements

You have to get feedback on any requirements you weren’t sure of. For any load limits you plan to measure and any failure modes that could be handled differently, you have to ask for confirmation explicitly. As a tester, you need an answer to those questions, but you might not be best placed to make those decisions. The user experience team and product owner will have a better idea, so ask them the specific questions you need.

As previously noted, reviewers may object to choosing a limit for system metrics. They may say there’s no point stating that the system can only support 1 million users, for instance, when in all likelihood it could do many times that number successfully, or conversely, it might not get anywhere near that number in reality. While there may be no difference between 1 million and 10 million users for the development team, there is a large difference in what you have to test and support, so you need to agree on that...