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)
1
Part 1 – Preparing to Test
6
Part 2 – Functional Testing
13
Part 3 – Non-Functional Testing
17
Conclusion
Appendix – Example Feature Specification

Using decision tables

To capture complex interactions between dependent variables and system behavior, it can be helpful to write out the possibilities in a table. This provides a basis for writing test cases and ensures that all conditions are covered. By expanding out the variables in a systematic way, you confirm you haven’t missed any combinations.

Consider a web application with basic or advanced support depending on the operating system and web browser it runs on. The advanced mode isn’t a replacement for the basic mode; some users may choose the basic mode even though the advanced mode is available.

The specification states the following:

  • Chrome supports basic and advanced modes on Windows and macOS
  • Edge supports only basic mode on macOS
  • Safari only supports basic mode and only on macOS
  • Edge supports basic and advanced modes on Windows

Do those requirements cover all possible cases? They do, although that isn’t immediately...