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

Review meeting checklist

The goal of the review meeting is to agree on all the requirements in the feature specification so that detailed testing is possible and the development team knows exactly what to deliver. To achieve that, before you let everyone go at the end of the meeting, make sure you have covered all the following points:

  • Has the team agreed to all the requirements in the feature specification?
  • What questions are outstanding? Who will answer them, and who will check they’ve been answered?
  • Have you asked the developers for any code paths they had to add to cover special cases?
  • Are there any configuration options that aren’t listed in the specification?
  • Has the team agreed to all the cases where you proposed a requirement or behavior? (That includes any requirements you wrote aiming to be precisely wrong rather than vaguely right.)
  • Have you prioritized different areas of the specification? Which sections should you test first?
  • ...