Test Readiness Review (TRR)

A Test Readiness Review (TRR) is conducted to determine if the system under review
is ready to proceed into formal testing by deciding whether the test procedures are complete
and verify their compliance with test plans and descriptions. A TRR is normally conducted
before each major test configuration item including hardware and software and provides
management with the assurance that a system has undergone a thorough test process and is
ready for turnover to the next test phase. The Flight Readiness Review (FRR) is a subset test
of the TRR.

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. The TRR also assesses the system under review for development
maturity, cost/ schedule effectiveness, and risk to determine readiness to proceed to formal
testing. ()

Test Readiness Review checklist:

1. Whether all the tests are conducted according to the Test Plan or Cases?
2. Why are we testing?
3. What is the purpose of the planned test?
4. Does the planned test verify a requirement that is directly traceable back to a system
specification or other program requirement?
5. What are we testing (subsystem, system, system of systems, other)?
6. Is the configuration of the system under test sufficiently mature, defined, and
representative to accomplish planned test objectives and or support defined program
objectives?
7. Are we ready to begin testing?
8. Have all planned preliminary, informal, functional, unit level, subsystem, system, and
qualification tests been conducted, and are the results satisfactory?
9. What is the expected result and how can or do the test evaluation results affect the
program?
10. Is the planned test properly resourced (people, test article or articles, facilities, data
systems, support equipment, logistics, etc.)?
11. What are the risks associated with the tests and how are they being mitigated?
 12. What are the hazards and ESOH risks associated with the specific testing?
13. Have the necessary Safety Releases from the Program Manager (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?