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

Goals of maintainability

The maintainability of your product includes three main use cases, which we will discuss in this chapter:

  • To quickly know if your system is suffering from degraded performance, for example:
    • Checking on hardware health
    • Checking on system resources
    • Identifying patterns in software issues
  • To easily maintain and improve your system, for example:
    • Seeing the current running state
    • Performing upgrades and improvements
    • Enabling new features and capabilities
  • To debug specific failures, for example:
    • Why didn’t a user receive their password reset email?
    • Why did a web page fail to load?
    • Why did the application fail to update to the latest version?

Maintainability is closely tied to observability because you can only make improvements if you thoroughly understand your product’s current running state. This section considers these three use cases in more detail.

Tools for observability

Complex products with multiple interacting systems will...