How to Write a Software Test Plan

Creating a software test plan begins before the software is created.

Writing a software test plan involves deciding what things to test of the new software, on what hardware and in what stages. Some say creating the software test plan is the same as any full-scale project management project. Being in charge of writing the software test plan, you'll conduct meetings and interviews with networking teams, current programming teams, upper management and end users. You'll create the software test plan when the software is in its planning phases. A word-processing program can make writing the software test plan easier.

Things You'll Need

• Word processing software
• Internet access (optional)

Instructions

1. Decide what types of testing will take place and when. Code module tests parts of the code for functionality as each is created. System testing checks the overall software application, and load tests determine how the software holds up under extreme traffic and usage conditions.

2. Insert the approximate times or in what phases the testing will take place. Breaks or benchmarks in the coding processes generally indicate appropriate testing times.

3. List those who are responsible for reporting information, as well as the heads of each department involved in the creation and testing of the software. Include relevant contact information.

4. Identify and include any specialized hardware the software will be tested on. For example, note whether the testing is to take place on one laptop, one personal computer and one Apple computer all at the same or individually, or whether the software will be tested on prototype hardware when applicable.

5. Make a list of business expectations the software is expected to perform successfully. Categorize expectations for each major function of the software, so the testing can be performed separately. For example, separating testing requirements for calculation functions and those expected for sorting, deleting or updating functions will allow you to isolate the functions for finding the most bugs at once.

6. Submit the software test plan for approval to necessary department heads.

Tips & Warnings

• Creating the software test plan document in sections will make it easier to read. Filling in each section as you obtain the necessary information will keep you from doubling back to get the same information from the different teams later.

• Clarify anything you do not understand when working with end users and various teams so you can define with simple and very clear terminology exactly how the software is to perform in order to be considered successful. Keep accurate records while working on the software test plan so you can provide information quickly to those who need it during the coding stages.

References

• "Information Technology Project Management"; Kathy Scwalbe, Ph.D.; 2007
• Micro Tools, Inc: How to Write a Great Software Test Plan