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

Improving the handover from the product owner

I have seen features handed to the test team with nothing more than a name and a few notes tracking the required code changes. I was supposed to pick the testing up with no details about the feature’s function, appearance, or implementation. If you’re in that state, then have a word with the product owner and developers. Throwing features over the fence to test in that way is massively counter-productive; the communication needs to be much better.

A note on naming

I refer to the person who prioritizes the features and describes their functionality as the product owner. They go by different names in different organizations, such as product managers or project managers, so you’ll have to translate it for your situation. The important point is that this is the person who advocates for the customer’s needs, prioritizes features, and decides their behavior. That may be an individual or an entire team, depending...