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)
1
Part 1 – Preparing to Test
6
Part 2 – Functional Testing
13
Part 3 – Non-Functional Testing
17
Conclusion
Appendix – Example Feature Specification

Attack types

The security threats to your application fall into two classes – acquiring access to restricted information and gaining control of private systems. The first class is easier and more common. Data leaks involve anything from accidentally allowing public access to data stores to using outdated cryptographic hashes, giving sufficiently resourced attackers the chance to break their encoding. It’s harder to control remote systems, but anywhere there is an input there is a chance to enter invalid data that will trick your application into obeying an attacker.

As a simple example, a 404 content injection attack involves creating a link that makes a trusted third party display a message of your choice. For example, you can enter www.example.com/visit_my_company in your browser. If example.com is vulnerable to this attack (which it isn’t, in reality), it would display an error such as The URL /visit_my_company was not found on this server.

You have now...