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 to check during load testing

You should watch for monitoring alarms during all your tests, but especially with load testing, which is designed to exercise uncovering system issues. If there are memory leaks or leaks of other resources, this is the test to find them. Load testing has to be performed by automated scripts, but writing the checks is at least as much work as generating the load. A single command to change the system’s state may need many tests to verify it. Write a generic check function that you can expand for whatever tests you are performing, and use your system monitoring; see Chapter 10, Maintainability.

At the most basic level, you can run load testing and check for any catastrophic events – the application crashing or unhandled exceptions. The next level of checking is verifying that each operation is successful. For every user creation command, for instance, check that a user exists. You should also routinely check the logs for error messages...