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


In this chapter, we’ve seen the importance of testing the maintainability of maintenance operations, system monitoring, and logging. None of these functions are customer-facing, but each has a massive impact on the engineering team working on the product and, through them, the improvements they can deliver to customers. How fast can your company fix bugs, recover from outages, and roll out changes?

Those things affect customers, and they need maintainable code. That doesn’t happen on its own; if you don’t check that the requirements for maintainability are written and implemented, it’s possible no one else will. This piece of testing is in your own best interest.

In the next chapter, we’ll consider destructive testing in which you deliberately degrade your system to see how it copes with internal issues. These are vital to recovering from errors but can be hard to plan for, making it a critical area to test.