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


In this chapter, you have seen many examples of security processes and tests you should run on your application. The first step in security testing is identifying the attack area – what different kinds of servers do you have, which are public and private, what ports do they have open, and what protocols do they support? Armed with that information, you can perform security scans and design test plans on the relevant machines.

We described running security scans and code analyses as the first steps for testing security, and considered the main areas of security vulnerability, including logging in, privilege levels, and user and file inputs. We looked at web server misconfigurations that can lead to security problems and considered PII, which is particularly sensitive and needs to be identified throughout your system, along with a process to ensure its deletion.

Finally, we looked at systems around security testing of the application, including running a bug bounty...