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

Understanding usability and the feature specification

You, and everyone on the development team, spend your working lives on this product and devote orders of magnitude more time thinking about it than your customers. They are teachers, entrepreneurs, or bankers who just happen to use your product, and if they can’t work out how to use it in 2 minutes, they’ll give up. They’ll complain your product is a piece of rubbish and get on with their actual job.

UX testing can be broken down into two different sections. First, you need to ensure that the product conforms to the specification – are the user-facing elements present, do they look correct, and is the text as described? This is objective and automatable – does the implementation match the specification? If a button is missing or the color is incorrect, that can be found and fixed.

More often, problems are due to the specification, which is the second class of issues. Your feature might be...