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

Setting the correct version, configuration, and environment

One of the biggest wastes of time when testing is using the wrong version or configuration. Testing can go quickly when everything is working as planned. As soon as something goes wrong, you must stop and investigate, which should be reserved for genuine bugs. Anything you can fix yourself, you should do first.

Before it can run the correct version, your product must have proper versioning. If your development team lets you test whatever code happens to be in the repository, that is the first thing that has to change. The test team needs to use a stable, numbered build. That isn’t required for exploratory testing and lower-level tests, such as component and integration tests, which can run on every build and use nothing more than a build number. However, by the time you come to run the comprehensive functional tests, you need to know which version of code you were running.

Within fully Continuous Integration/Continuous...