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 information display

Keep the screens that display information as simple as possible. To return to the theme of this chapter, less is more. This is easy to say, and the more egregious violations of this principle are easy to spot. The trick is seeing them early enough and finding even the mildest of examples. This is a large subject and deserves a dedicated team to focus on it. Here, I will only cover some simple examples to look out for while testing, but I thoroughly recommend reading further on this fascinating subject. Within the Packt library there is Practical UX Design by Scott Farnanella or Hands-On UX Design for Developers by Elvis Canziba.

Real-world example – Too many axes

One company I worked for produced an internal tool in which graphs of network activity had eight different axes, all plotted on the same chart. Sending bandwidth, receiving bandwidth, packet loss, jitter, and latency all had lines that were superimposed over each other by default. If...