Final Report

The Final Report template refers to the topics that a test manager should enter in a final report.

I. Test Management Summary

The Test Management Summary is a synopsis of the test manager’s final report. The summary should address five types of information:

a. The test project goals, which are referenced in the test plan, that have or have not been met.

b. The quality of the system under test as determined by risk-based testing.

c. Any discrepancies between the planned and actual test effort in terms of schedule and budget.

d. The critical benefits that were realized by the test effort.

e. A recommendation as to the transfer of the test object into the production environment.

II. Test Assignment

The Test Assignment section mirrors the information documented in the test plan. This information is related to the actual assignment in the Recommendations section of this report.

III. Information System Quality

The Information System Quality section summarizes the information system’s quality. This overview is the basis of the recommendation that’s documented in the Recommendation section.

a. Product Risks and System Requirements

The Product Risks and System Requirements section identifies the product risks and system requirements that the test effort did and did not address. The source of this information is the test-level specific progress or phase reports.

For each product risk that’s stated in the section, its status is documented. This entry is either “Correct” or an explanation as to the issue that precludes the “Correct” entry. Should an outstanding issue be the source of the lack of a “Correct” entry, the rationale is documented in the Overview of Issues section of the report. That section also addresses any product risks that were not tested because the risk materialized. For the latter status, the consequences must be stated.All product risks and requirements data should be reported in a table:

TABLE

b. Issues Overview

Provided in this section is a summary of the project’s outstanding issues, such as those related to risks as described in the Product Risks and System Requirements section. Also documented is progress on the outstanding issues. For instance, the test manager will state if the issue is transferred to a subsequent release of the product or if the issue will be addressed during the maintenance phase of the product’s life cycle.The manager should also make note of the future responsible party and whether an action item is outside the current project scope.This information should be documented in the report’s Recommendations section. As an alternative, the test manager may elect to summarize issues related to the individual test level.

c. Acceptance Criteria

The test strategy and the test plan contain information regarding acceptance criteria, in the latter of which is entry and exit criteria for individual test levels. This information should be stated in the Acceptance Criteria section of the Final Report. Also stated should be an indication as to whether the criteria were met or not. If the criteria were not met, the explanation should be provided as should the consequences of this event. When possible, a reference to the pertinent product risk should be made.

IV. Test Project Costs and Benefits

a. Time Expenditures

The test-level costs in terms of time and budget are reported in the test-level phase reports.Summarize and total this information at the project level in this section.

Alternatively, the variance between planned and actual time per test activity.This information can be gathered from the test control matrix or that determined using the Earned Value Method. This information is typically recorded using MS Project.


TABLE


b. Financial Costs

The Financial Costs section presents an overview of the budget and the actual costs. Reference documents for this section include existing budgets and a description of the planned activities.The budget will dictate the level of detail of the information that’s provided. Either the Earned Value Method of the Test Control Matrix methods data may be used as a source, as can the table created in part A. Included should be all costs. Such as travel expenses, tools, project audits and so on.

c. Test Benefits

In this area of the Test Summary Report, the benefits of the test project are stated. Issues are linked to product risks using test conditions. Also, comments regarding the impact on the software product should the faults in the product not have been identified and addressed are stated. Information such as the potential cost of the consequences of faults, in terms of time, money, reputation and customer goodwill is documented.

1. Test Project Deliverables

This section should begin with a summary of the test project’s deliverables. Next, an explanation of discrepancies between planned and actual deliverables is provided.

2. Test Automation Costs and Benefits

Sections IV A. and B. refer to test automation costs that should be compared to that of manual tests.Historical data provides information for actual costs of manual testing for similar test conditions for a certain number of repetitions.

V. Recommendations

The “Go-or-No-Go” decision to transfer the system to a production environment is documented in the Recommendations section. This decision is supported by comments of any discrepancies between the assigned test effort, which is described in the Test Assignment section, and that which occurred. The Information System Quality section is the basis of the decision to move the system to production or not, as well as the means my which outstanding issues and project risks should be addressed.