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

Logging in

Logging in is vital to many applications, so much so that many standard frameworks provide this functionality. Here, you should use white-box knowledge: how much does your application use a standard framework, and how much have you implemented for yourselves? If you rely entirely on a third-party framework, you can keep your testing brief and focus elsewhere because others have tested and used that code. Even then, you need to check that it has been used correctly, such as requiring a login for all restricted screens. If your application implements most or all logging-in functionality itself, you need a far more comprehensive test plan, as described here.

Logging in comprises two functions: authentication and authorization. Authenticating involves verifying the identity of a user and proving they are who they say they are. Authorization grants access to some parts of your application based on that identity. At a basic level, there may be administrator and user privileges...