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

Making the Most of Exploratory Testing

“Begin at the beginning,” the King said, very gravely, “and go on till you come to the end: then stop.”

- Lewis Carroll, Alice in Wonderland

This chapter introduces exploratory testing: manually trying out a new feature to get rapid feedback on its behavior. We’ll describe exploratory testing in detail, consider its strengths and weaknesses, and when you should perform it in a project.

We’ll look at the prerequisites you need to begin exploratory testing and the approaches you should take. This testing can be a miniature version of the complete test plan, taking a customer’s point of view, and using your naivety about how the feature works to identify confusing areas.

Exploratory testing should be used as part of a larger test strategy but can be run in isolation when time is short. We’ll finish by looking at what you should check when performing this testing, and the importance of curiosity, both here and throughout the testing process.

In this chapter, we will cover the following topics:

  • What is exploratory testing?
  • Advantages, disadvantages, and alternatives
  • Understanding when testing should begin
  • Understanding the test activities
  • The spiral model of test improvement
  • Performing the first test
  • Mapping out new features
  • Using your naivety while testing
  • Running complete exploratory testing
  • Using exploratory testing by necessity
  • Checking exploratory test results
  • Using curiosity in testing