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

Understanding different levels of testing

Consider the following simplified architecture of an example system as shown in Figure 4.1. It has two user-facing inputs: a web interface and an API, labeled A and B on the left-hand side of the diagram, respectively. Those requests are processed by Module 1, which has several functions, before being passed over an internal API, labeled C, to Module 2. Module 2 also comprises several functions. It communicates with Module 3 using a backend API, labeled D. Module 2 also has two external, read-only interfaces: a web report, labeled E, and automated emails, labeled F:

Figure 4.1 – Diagram of an example system, showing unit, integration, and system tests

Unit tests are the lowest test level, breaking the code into the smallest testable entities. That means trying individual functions and classes to ensure they correctly respond to inputs. As shown in the diagram, that would mean testing Function 2 of Module 3 independent...