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

Running UX reviews

The user interface presents so many possibilities, is so essential, and can generate so much discussion that it deserves its own review meeting. These follow the same guidelines as the main feature specification review, as specified in Chapter 3, How to Run Successful Feature Specification Reviews, although there are differences.

The guest list for the UX review should include the UX team, the developers, the project manager, and the testers working on the feature. The project manager and senior developers are still optional. This area benefits from multiple points of view, so make sure everyone can attend and is prepared to present their ideas. Having said that, from experience, it’s good to keep the guest list as short as possible; otherwise, having too many opinions can make these meetings take too long.

The timing for the UX review is also tricky. The developers should expect this meeting, or they may consider the interface finished when, in fact...