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

Using curiosity and feedback

Stepping through the test cases that the feature specification suggests may sound like a dull, robotic task, but expanding them into detailed test cases requires curiosity and investigation. As described later, it’s impossible to consider every possible combination of inputs, so you must constantly pick and choose which particular options you will try. It’s also always possible to extend tests – once you’re in a given state, you can vary conditions and perform checks that the specification and test plan don’t mention.

Throughout the entire test design and execution, maintain the inventiveness and curiosity you needed during the exploratory tests. Constantly be on the lookout for other interactions, other things to try, and other things to check. Once you are running manual tests or coding automated tests, you are spending longer examining this feature’s behavior, with more information, than anyone else in the...