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


In this chapter, you learned how to run a successful feature specification review. We looked at the advantages and disadvantages of a meeting dedicated to reviewing the specification and some alternatives. No other meeting gives the same coverage and flexibility as a specification review, making it the best way to finalize and agree on feature specifications.

To run a successful review, you need to invite the right people, including the product owner, lead developer, tester, and user experience designer, for any customer-facing features. System architects, senior developers, and testers may also come along, especially if junior engineers have developed this feature. The project manager can also attend to check on scope changes and their effect on timescales. They should be invited with sufficient time to read the specification and prepare. In the meeting, step through each requirement, either agreeing on it or debating what changes it needs. Keep the tone open and friendly...