Software Test Plan Results Documentation

Due: Friday, April 21st, 2006

Description

The Test Plan Results Documentation will be based upon your Test Plan, showing and discussing the results created by your system when executing the Test Plan. It will reflect whether your system has satisfied the validation and verification process specified in your Test Plan. It will show whether your system satifies your requirements and any requirements unsatisfied.

Recall the focus of test process, validation, and verification. Discussing the your results related to these topics will be the focus of your documentation. Validation involves assuring your client that the system meets their requirements and verification involves assuring yourself that the system conforms to its specification. It logically follows that there are two primary goals in the testing process:

  1. Demonstrate to yourself and your advisor that your system meets its requirements.
  2. Expose exceptional behavior in your system. This includes behavior that causes results to be faulty (for example, improper casting), the system to act undesirably (for example, unhandled or unexpected runtime exceptions), or non-conformity with specifications.

Previously, you provided a brief description of the test procedure including the necessary inputs and expected outputs, results, and side effects. This context should be maintained, either by including the test cases in this document or through a clearly reference navigation scheme, refering the reader back to the Test Plan as test case results and the system are analyzed.

A sample outline for the document would be:

Cover Page: Include the project title, your name, document title, and document date.

Table of Contents: Providing a table of contents will help readers navigate your document efficiently.

Solution Analysis: Analyze the results gained from the execution of your test plan. Refer to your Requirements Traceability of the Test Plan to assist in your discussion.

Test Results: Refer to the recording procedure specified in your Test Plan. This will show the results of all your tests.

Schedule: Provide the actual testing schedule implemented.

Appendices: Include any related information that does not fit into the sections above. Examples may include descriptions of systems that you used but did not develop, descriptions of hardware that will interface with your system, or any descriptive information that was simply too bulky to provide inline in the document.

Index: Common indices include an alphabetical listing of relevant terms, an index of tables, an index of figures, and an index of functions to assist the reader in finding information efficiently.