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

What we learned from Part 1, Preparing to Test

Part 1, Preparing to Test, has covered the necessary preparation for testing. In an ideal world, every feature would have a detailed written description of exactly what it does. In that case, you could skip Part 1, Preparing to Test, entirely and jump straight to Part 2, Functional Testing, where we consider how to test features.

However, in my experience, the test team isn’t always provided with feature specifications, and those that exist aren’t in sufficient detail. It’s almost always up to testers to ask further questions and fill in the gaps in the description. We saw three important stages to achieve that.

Using exploratory testing you map out a feature’s behavior, considering the many approaches described in this book: functional testing, error handling, usability, security, maintainability, and non-functional testing. Exploratory testing also lets you quickly find issues that would block more...