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

Loading messages between modules

Load testing involves firing many messages at an application’s external interfaces, but internal messaging will also have high usage when the system is busy. Another class of issues arises from overloading those communication flows.

Do your internal messages have suitable queues, retries, back-offs, and failure modes? This is another class of issue best probed with load testing to ensure there are no hidden bottlenecks within your system.

This section is hard to describe because both the causes and effects are indirect and can be difficult to trigger with system testing. You will have to check with the development team which operations will cause the highest rate of internal messaging within your system; this is an area where you need white-box insights. It won’t be clear what symptoms internal message failures might produce. Operations could time out or fail; the system might be left in an inconsistent state, with some processes...