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

Designing monitoring

Monitoring involves checking system performance metrics and regularly running simple automated checks. These overlap with tests you should have run before release, but they fulfill a different function since they find test escapes and operational issues affecting your live environment. Since monitoring checks are run after a system’s release, they are not tests as such but have so much overlap with your test plan that they’re worth considering here.

Being a tester, you’ll interact with the monitoring in two ways:

  • Firstly, you’re a user, using monitoring to check for errors on your test system. New code must complete its test run without causing errors in the monitoring system.
  • Secondly, you need to ensure that every new feature has relevant monitoring. If your system can now fail in a new way that you’re blind to, that’s a bug that needs fixing.

Monitoring requires a dedicated system that gathers all...