|
Test Plan Document Contents
I. Title Page
II. Include a brief Summary of your System - 1/2 to 1 page.
III. Briefly describe the organization of your system. Include diagrams or tables from the design document which will help the reader understand the organization of your program. For example, you could include the structure chart or class table. If these diagrams are long or complicated then just reference the pages in the design document where these diagrams or tables can be found.
IV. Describe the integration technique your team plans to use.
V. Include Unit Test Plans for your system units. Each unit test plan should contain:
A. Identification of the unit, programmer, version number, and indication of where this unit fits into the program. (You could reference the structure chart)B. Unit purpose and function.C. Brief description of how the unit works.D. Prerequisites for testing; database, hardware, etc.E. Total number of unit tests to be run with space to later insert percentage passed and list of bugs found.F. For each test you need1. test number2. purpose for test3. date test was performed4. any database prerequisite that is special for this test5. initial conditions6. inputs7. expected outcomes8. actual outcomes and method of verifying outcomeDo the results indicate that rework is required for this unit?Show at least 4 tests that are representative of the different types of tests you will be performing on this unit. If a test has not been run then you can leave the answers to 3, 8 and 9 blank. Note, this is not all the tests that you should run for the unit.
VI. Summarize the results of the structured walkthrough of one of your systems modules. Indicate which module was examined, who participated and in what roles, and indicate what errors were found
VII. Acknowledgments
The Test Plan Document is Due on April xx, 2000.
|