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

Filtering load test errors

Load testing is messy. This is the most challenging form of testing, requiring all functions and logging to work reliably and a stable, robust system from which to run tests. If functional testing is a scalpel carefully probing your application, load testing is a rugby tackle, using brute force to take it down. When you run load testing, many operations coincide, and the system runs in ways it never usually does. While this may trigger genuine issues, you’ll also hit a large class of problems that are only ever seen under loading conditions. These aren’t useful to find or fix; so, the best option is often to work around them.

Real-world example – Users left behind after load testing

When we started load testing in one company I worked at, one of our first tests was to load user creation. We ran a simple loop that created and deleted thousands of users and instantly hit a problem: a small percentage of delete operations failed, leaving...