How to Build a Test Plan
After months of analysis, design and development, the product is finally complete. All the requirements have been met, change requests were included, and now it is time to begin testing. No matter the approach or methodology, the test process should follow a script or test plan. This plan lists the items to be tested, the people performing the tests, a timeline and criteria that defines success or failure. The plan does not have to be hundreds of pages long -- just enough to define the tasks. Follow these steps to create an effective test plan.
Other People Are Reading
Instructions
-
-
1
Create an outline. Check the reference links below for a few examples. The size and scope of the project should dictate the breadth of the test plan.
-
2
Identify the testing team. Assess their skill levels, check their availability (other projects, vacations or holidays), then begin to build a rough timeline.
-
-
3
List all requirements, features, change requests and other items. Group them together logically, by functions, modules or other ways so related items can be tested together.
-
4
Define test scenarios for each group of features. Make sure to test exceptions and boundary conditions. For example, if tax rates are 15 percent for those earning up to $10,000 and 20 percent for those earning more than $10,000, test tax rate calculations at $9,999.99, $10,000 and $10,000.01. Also test negative and excessively large numbers to make sure they are rejected.
-
5
Create additional scenarios to minimize liability and risk. Test consumer products to find inappropriate uses. Test web software for hacking and security intrusions. Medical devices should be tested to ensure safe operation, even when not used correctly.
-
6
Describe success and failure criteria for each test, as well as procedures for reporting problems. When a test fails, how is it reported? Who does the report go to? How and when are changes released and what tests are repeated?
-
7
Complete the schedule. Create a timeline for the test process -- listing who performs what tests and when they are performed. Are there dependencies to consider? Certain tests only may be possible after other tests have passed successfully. If necessary, create the budget that accompanies the schedule.
-
8
Determine the end point. At what point will the product be released? Depending on the type of product, a 100 percent success rate may not be necessary. Determine this benchmark before testing begins and make sure the test team and stakeholders agree to these conditions.
-
1
Tips & Warnings
Identify risks. Determine which features have the highest priority or could cause the greatest problems, then test these features early on in the process.
