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

Improving requirement statements

There is an art to writing requirement statements. It’s easy to write vague or useless requirements, so you need to be strict and follow a particular style. Specifically, your requirements should have the following properties:

  • Specific
  • Measurable
  • Agreed
  • Realistic
  • Complete
  • Consistent
  • Independent
  • No implementation details

This section will examine each of those qualities in turn. The first four come from the SMART acronym for management objectives and are a great guide to writing goals in general. The T in SMART stands for timed, and that’s one aspect that these requirements don’t need to cover. Project planning is a skill that is beyond the scope of this book, but it isn’t necessary for the functional requirements. It only records what the product should do, not when. Let’s compare two requirements to illustrate the qualities that requirements need to have:

A. Reading the...