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

Using logging

Logging is the most useful form of output from your system for diagnosing issues and understanding the details of its behavior. This section considers how logs should be written so that you can use them to the best effect.

Finding “the” log

It’s vital that you get the correct information to the developer to help diagnose an issue in their code. While I always try to include the relevant information, I’ve lost count of the number of times a developer has asked me for the log. It’s a simple enough request; the only problem is the word the. Which log do they need for any given issue? Within that log, which line is the clue? Other sections of this chapter will recommend approaches to finding problems within logs; here, we consider finding the correct log in the first place.

Real-world example – Logging on dual redundant hardware

In two of my jobs, I’ve improved the presentation of logs, and in both cases, I’...