Purpose

The acceptance test results outline which tests were run on a project and the outcomes of those tests. They are used to generate a history of the testing process, as well as the environment and the outcomes.

Application

The acceptance test results are used to determine whether or not the project deliverables are performing as originally anticipated. If they are, the test results are used as evidence that the customer should accept the project and sign off on any lingering contract documentation. The results also allow for the examination of any anomalies  that  may occur as implementation moves toward transition to customersupported operations. If the test results indicate the project is not performing as anticipated, the acceptance tests serve to identify which areas of project performance are not acceptable and what remediation may be required before the customer accepts the project deliverables.

Content

The acceptance test results will include information about the nature of the project, the tests, the environment, the outcomes, and any reference documentation needed to support the testing methodology. The results may include the information discussed in the following subsections.

This is simply an iteration of the scope statement or a description of the element undergoing testing.

This is a description of the breadth of the testing, and the nature of the testing (destructive/nondestructive) and the quantity or nature of the deliverables undergoing the tests.

3.0 Testing Approaches

This is a detailed description of the types of tests that have been conducted as elements of the acceptance tests and a detailed explanation of how the tests were actually conducted. Specific test cases are identified and the methodology is explained in detail. The test environment is also described here in detail.

For the tests identified in Section 3.0, the outcomes of each test are defined. For those that fail or only partially pass, details are provided on the nature of the remediation required or the rationale for the failure. This section may be broken out into general test outcomes and individual supporting component test outcomes.

Based on the tests and their results, further action may be required, or the customer may have agreed to some concessions on project performance or approach. Those modifications or additional actions are documented here.

6.0 Supporting Documentation

Because many tests, methodologies, and environments are unique, there may be a need for extensive reference documentation to describe the environment. It may be included either in whole or by reference in the acceptance test results.

Approaches

The level of detail in the acceptance test result documentation should be determined as the project contract documentation is being developed. The level of detail will largely determine the level of effort associated with the documentation. Also, because the outcomes from the acceptance test results often determine whether or not a project is  “accepted” and paid for, it is important to have a mutually understood protocol (between buyer and seller) for what will happen after the test results have been generated.

Considerations

Some customers may deem it essential that every element of a project’s test criteria pass before they will accept deliverables. Others will accept some marginal level of failure, as long as it does not exceed a given threshold. That’s why it is important to determine how perfect the test outcomes must be before the tests are conducted. It is also important to determine where specific attributes (yes/no, pass/fail) must be met and where other elements will be evaluated on a more variable or gradient scale. The more that can be done to establish expectations early in the project, the more likely the project acceptance test results will be viewed favorably when they are completed.