Description
The primary purpose of the Test Phase is to determine whether the automated system/application software or other IT solution developed or acquired and preliminarily tested during the Development Phase is ready for implementation. During the Test Phase, formally controlled and focused testing is performed to uncover errors and bugs in the IT solution that need to be resolved. There are a number of specific validation tests that are performed during the Test Phase (e.g., requirements validation, system integration, interface, regression, security, performance, stress, usability, and user acceptance). Additional tests may be conducted to validate documentation, training, contingency plans, disaster recovery, and installation depending upon the specific circumstances of the project. The Test Phase ends with a review to determine readiness to proceed to the Implementation Phase.

Responsibilities
Project Manager: The Project Manager is responsible and accountable for the successful execution of the Test Phase. The Project Manager is responsible for leading the Integrated Project Team that accomplishes the Test Phase activities and deliverables.

Test and Evaluation Team: The Test and Evaluation Team is responsible for Business Product testing and documentation of test results.

Users: Selected users may be required to participate in testing.

Critical Partners: The Critical Partners review test procedures and outcomes in their areas.

• Security: Check that the validation tests confirm the security of the Business Product. Penetration tests and vulnerability scans are executed, documented, and any failed components are reworked.

• Acquisition: Determine if changes are reviewed to determine if any contract modifications are necessary.

• Finance: Conclude that Changes are reviewed to determine the financial impact.

• Section 508: Verify that test plan results for Section 508 testing are satisfactory.

• CPIC: Determine if the Implementation Plan has a reasonable schedule.

• Performance: Determine if Measurement indicators support the performance measures agreed upon and validation tests confirm the performance measures. Ensure that system functionality is performing as stated and is able to achieve performance goals.

Activities
The following tasks are completed during the Test Phase:

• The Project Manager, in conjunction with the Business Owner and CIO, is responsible for establishing the test team and creating the Test Files/Data.

• The test and evaluation team is responsible for creating/loading the test database(s) and executing the system test(s). All results are documented in the Test Reports. Any failed components are migrated back to the Development Phase for rework, and the passed components migrated ahead for security testing.

• The test and evaluation team create or load the test database(s) and execute security (penetration) test(s). All tests are documented, similar to those above. Failed components are migrated back to the Development Phase for rework, and passed components will be migrated ahead for acceptance testing.

• The test and evaluation team create/load the test database(s) and execute the acceptance test(s). All tests are documented similar to those above. Failed components are migrated back to the Development Phase for rework, and passed components migrate ahead for implementation.

• During this phase, the documentation from all previous phases is finalized to align it with the delivered system. The Project Manager coordinates these update activities.

• Determine whether or not the tested product is ready for production.

During the Test Phase, the project team also develops the final version of the Implementation Plan that describes how the business product will be installed, deployed, and transitioned to the operational environment.

Exit Criteria
Objective: To determine if the test processes have been executed according to plan and whether the tests verify that the implementation of the Business Product will be successful.

Phase Specific Exit Criteria:

• Test plan ensures that test cases will be executed to make certain that requirements are met.

• Testing of the Business Product supports the decision to move to the Implementation Phase.

• Implementation Plan provides detailed information on the move of the Business Product into production.

Generic Exit Criteria:

• Variances from baselines have been identified and mitigated. [Cost and schedule variances and scope changes are identified, significant variances are explained, and Corrective Action Plans (CAPs) or rebaseline requests are in place as appropriate.]

• Investment baselines have been reviewed and revised as appropriate. [Should this investment continue as-is, be modified, or be terminated based on current knowledge?]

• The Project Management Plan and component plans have been reviewed and appropriately updated. [This includes Risk Management, Acquisition Strategy, Change Management, Configuration Management, Project Categorization, Requirements Management, Communication Plan, WBS/Schedule, IV&V Planning, Quality Assurance, Records Management, Staff Development Plan and Security Approach.]

Project Review
The Implementation Readiness Review (IRR) is conducted at the end of the Test Phase. The IRR is conducted to ensure that the IT solution or automated system/application that has been developed is ready for implementation activities, such that the required system hardware, networking and telecommunications equipment; COTS, GOTS, and/or custom-developed software; and database(s) can be installed and configured in the production environment(s).

Stage Gate Review
The Test Stage Gate Review evaluates whether the project should proceed to the Implementation Phase.