香港理工大学-软件测试计划.docVIP

This is a sample of an outline for a test plan. It has been designed for medium to small test projects, and thus is fairly lightweight. It is by necessity general, because each enterprise, each development group, each testing group, and each development project is different. This outline should be used as a set of guidelines for creating your own standard template; add to it or subtract from it as you find appropriate. Bear in mind that it is generally better to have an excess of detail in the template—detail which can be removed when creating a specific test plan—than to have to remember to add something that is not in the template. (Looking for a heavy-duty test plan? The government and the military are good sources. Try the one on the IRS Web site: /bus_info/tax_pro/irm-part/part02/28781a.html) Make sure to fill in the running headers and footers with the product name, draft numbers, revision dates, and page numbers; this is important in places with lots of test projects on the go. Make sure to include the author’s name, too, so that errors or questions can be addressed to the right person. OVERVIEW PRODUCT NAME PRODUCT REVISION PROJECT LEADS Marketing Lead (or other customer representative) Program Manager Development Lead Test Lead Build and Release Control Engineer Legal representative Include names, phone numbers, and email addresses for each. Note that this table will differ for a particular company or group. The goal is to ensure that anyone walking into the company or into the test role can easily identify and contact the people he/she needs to reach. TEST PROJECT STAFF Test requirements designers Test case designers Test personnel For manual (i.e. non-automated) tests For automated tests Test automation programmers Documentation reviewers Legal reviewer Include names, phone numbers, and email addresses for each. Note that there may be several people in each role, that one person may be obliged to fill multiple roles, and that some roles (e.g.