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

Test Types, Cases, and Environments

A tourist asks a local, “Which way is it to Dublin?”

The local answers, “Well, if I were going to Dublin, I wouldn’t start from here.”

– An old joke

Before we can start detailed considerations of test cases and plans, we must be clear about what each test case should include and evaluate the different approaches to writing them. Should they explicitly prescribe every action to take or merely describe the intended test, leaving individual testers to implement the details?

You have to choose your test environment. You could test on developer’s machines, where new code has been written seconds before, on your live running instance available to your users, or in various locations in between, such as dedicated test areas. Using VMs and containers, as well as defining infrastructure as code, lets you create consistent environments. Choosing the right one is vital to building a successful, reproducible...