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 2, Functional Testing

Part 2, Functional Testing, has considered the behavior of your application in a wide range of situations, from security to usability to core application functions. These are all functional tests: when you do X, your application does Y. In that simple view, you check if your program's output is correct for all the relevant inputs.

That may sound exhaustive, but there are still types of testing we have not covered yet. In Part 3, Non-Functional Testing, we will consider destructive testing, in which you deliberately disable part of the working system to check its resilience and ability to recover. Load testing ensures that your application performs consistently within its specified limits, with no unexpected latency or intermittent errors.

Finally, stress testing checks what happens when your system is pushed beyond its limits and its ability to protect its core functions even when asked to do unreasonable workloads. Some of...