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 the user interface’s look and feel

The watchword for the look and feel of any interface is consistency – a small set of colors, fonts, and styles should be used throughout. Or, to return to the theme of this chapter: less is more. Fewer designs and colors provide a better experience for users.

As a tester, you can check that consistency. Do new pages use the correct company colors? Does the text use a consistent font that’s a uniform size? Are the buttons and links the same size and design as others? If there is a genuinely new element, does it use the same style as others in a new way?

Typically, adding new features simply involves extending the styles already in use, but every so often, there is a project to rebrand a product. Due to the amount of work and the marginal gain this involves, I’ve only seen it done when absolutely necessary.

Real-world example – The corporate takeover

One successful company where I worked was bought...