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

Improving requirement content

Now that we’ve seen how to format the requirements and the best style to write them in, we can consider what they should say. The rest of this book describes the different aspects of testing you should consider and capture within the specification, while this section covers the general principles you should apply to the content of the requirements.

Keep it obvious, cover everything

The first requirements to track are the most obvious ones: the main functionality of this new feature. The product owner should cover these requirements, but even here, there can be gaps. There is an art to identifying your assumptions and saying them out loud. Never be shy about being obvious – every so often, something that was obvious to you will be the source of disagreement and confusion. You can only resolve that confusion by asking precise questions, starting with the easy ones.

Real-world example – The vote counter

I once worked on a...