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

Testing user interaction

As with displaying information, there is vast and growing literature on user interactions; I will only list a few particular examples here. As ever, trust yourself – if something annoys you, if you make mistakes, or if you have to carefully think through steps when using your product, then others will struggle even more. The fault is not necessarily yours, so first, check whether your application could be easier for users to use.

A good interface will guide users from the general to the specific: I want to change how I’m viewing this page (so I select View), I want to zoom in (so I select Zoom), I want to zoom to 200% (so select 200%). Are there clear routes through your application like that for all your user stories?

The other extreme is the Linux command prompt. While massively powerful and configurable, it provides almost no guidance. It’s simply a prompt; all the knowledge about how to use it comes from the user. In a way, it...