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


Successfully performing load testing has several prerequisites beyond that of other forms of testing:

  • A dedicated test environment: Taking the system to its limits may cause other tests to fail, so they should be run elsewhere.
  • A complete test environment: To see realistic loading issues, you will need a complete, realistic system with the correct subsystems and resources in place.
  • A reliable test environment: You need networks without packet loss and systems without other recurring issues before you can reliably find loading issues.
  • A loaded test environment: Add at least as many entities as are present on your live system.
  • Load generation tools: To rapidly create entities and perform actions on your system:
    • This includes generating web requests or a database load, simulating client connections, or data processing tasks. For more details, see the Load test design section.

All these need to be in place to carry out the tests in this section...