Test Readiness Review (TRR)

Originally developed as a software CI review, this review is increasingly applied to both hardware and software items. A TRR determines the completeness of test procedures and their compliance with test plans and descriptions. [Systems Engineering Fundamentals (2001) – DAU]

The purpose of the Test Readiness Review is to provide management with the assurance that the software has undergone a thorough test process and is ready for turnover to the next test phase. The scope of the Test Readiness Review is to inspect the test products and test results from the completed test phase for completeness and accuracy, and to verify that the test cases, test scenarios, test scripts, environment, and test data have been prepared for the next test phase. [DAFS/DCII Standards and Guidelines]

The DoD Test and Evaluation Management Guide defines a TRR as follows.

The TRR is a multi-disciplined technical review designed to ensure that the subsystem or system under review is ready to proceed into formal test. The TRR assesses test objectives, test methods and procedures, scope of tests, and safety and confirms that required test resources have been properly identified and coordinated to support planned tests. The TRR verifies the traceability of planned tests to program requirements and user needs. It determines the completeness of test procedures and their compliance with test plans and descriptions. The TRR also assesses the system under review for development maturity, cost/ schedule effectiveness, and risk to determine readiness to proceed to formal testing.

The TRR as a tool can be used to support all tests in all phases of an acquisition program, including testing within a system-of-systems context. The PMs and the T&E WIPT should tailor any TRR to the specific acquisition phase, the specific planned tests, and the identified level of risk within the program. The scope of the review is directly related to the risk level associated with performing the planned tests and the importance of the test evaluation results to overall program success. The scope of a planned TRR should align with the requirements verification matrix in the programs SEP. Readiness to convene a TRR is predicated on the PMs and T&E WIPTs determination that preliminary, functional, and pre-qualification test evaluation results form a satisfactory basis for proceeding with a TRR and subsequent initiation of formal, system-level test. The TRR should answer the following questions:

• Why are we testing? What is the purpose of the planned test? Does the planned test verify a requirement that is directly traceable back to a system specification or other program requirement?
• What are we testing (subsystem, system, system of systems, other)? Is the configuration of the system under test sufficiently mature, defined, and representative to accomplish planned test objectives and/or support defined program objectives?
• Are we ready to begin testing? Have all planned preliminary, informal, functional, unit-level, subsystem, system, and qualification tests been conducted, and are the results satisfactory?
• What is the expected result and how can/do the test evaluation results affect the program?
• Is the planned test properly resourced (people, test article or articles, facilities, data systems, support equipment, logistics, etc.)?
• What are the risks associated with the tests and how are they being mitigated?
• What are the hazards and ESOH risks associated with the specific testing?
• Have the necessary Safety Releases from the PM been provided to developmental and operational testers prior to any test using personnel?
• What is the fall-back plan should a technical issue or potential showstopper arise during testing?