How to Design a Test Plan
To design an effective test plan, first assemble the right test team. This team then performs a risk assessment to establish testing objectives, which are the foundation for the actual test plans. The team must then design and construct a test case around these objectives. Integration tests conclude the process as technicians prepare to execute the system.
Other People Are Reading
Instructions
-
-
1
The purpose of the system test is to ensure that the customer's documented requirements are met in preparation for user-acceptance testing. Test cases and scenarios are designed to accomplish this purpose.
-
2
Create business scenarios. These are real-life events that might occur on any given day. They can vary in size and impact from simple to complex. Marriage is a common event in personal banking, and mergers are a common event in corporate banking. These are both examples of simple events. Presidential elections and rising interest rates, however, may affect the firm in many ways. Therefore the process response is complex.
-
-
3
Define the test case. A test case evaluates the expected results for an application or event. It can be defined for data entry, a calculation or any desired output. Each test case should consist of an introduction (name, ID), activity (conditions, environment) and results (actual versus expected, pass/fail).
-
4
Create as many test cases as possible. Use your requirements as a checklist. Provide a space for documentation of the actual result next to each test case condition. You may need to create more business scenarios to accommodate all test cases.
-
5
Create an identifier for each test case. Numbers should follow the order of the tests.
-
6
Include test script. Provide the technician with a narrative or documentation to support the process. Be sure to include guidance on timing.
-
1
Tips & Warnings
Choose dates far in the future for test scenarios to avoid confusion.
References
- Photo Credit freedigitalphotos.net
