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

Running code analysis

Part of your security approach should be source code analysis, which can identify security issues before the application is even run. This is a form of static testing, as described in Chapter 6, White-Box Functional Testing. Like linting, this automatic check can detect potential security issues such as being vulnerable to SQL injection attacks or buffer overflows.

Many tools are available for such analysis, and the development team should ensure they run one before the code reaches the test team.

Such tools are easy to run and can be built into deployment pipelines to check each code change. However, they can flag false positive results, and it can be challenging to uncover some classes of vulnerability, such as authentication or access control. They also can’t find configuration issues, as they only examine the code rather than how it is deployed.

Despite its weaknesses, code analysis can quickly find important classes of bugs and is a necessary...