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


Picture this scene: you’ve designed a beautiful website or app that is clean and straightforward to use with a clear flow between tasks and provides all the complex functionality of your application at your users’ fingertips. This would be excellent, except it doesn’t load on their device.

There will always be a wide variety of operating systems and web browsers being used and supported at any time, with a spread of percentages from new to old and between competitors. Which platforms and versions does your application support? That’s the first interoperability question and will depend on the variety of versions your users are using. The product owner needs to trade off the technical effort of supporting those versions against the importance of those customers. You might include a version because many customers use it or because there’s a smaller number of highly important clients. Whatever the reason for their inclusion, as a tester...