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

Summary

In this chapter, you have learned about the different levels of testing and their respective strengths and weaknesses. Unit tests are simple and quick to write but require detailed knowledge of the code and cannot find classes of bugs that only appear when the whole system works together. System tests are the only way to find that class of bug, but they are harder to write, which is why this book focuses on them.

We looked at what a test case should include – its prerequisites, setup, procedure, and result. These are obvious enough to list, but it takes discipline to document them all consistently. You will save valuable time by being clear about what a test requires and what results you should see, so make sure they are a part of your test plans.

Prescriptive tests define precisely what steps you should run, but it can be more powerful to use descriptive tests, which allow variations within given parameters. Those tests should be run on a carefully chosen environment...