{"id":785,"date":"2023-01-12T19:09:34","date_gmt":"2023-01-12T19:09:34","guid":{"rendered":"https:\/\/webresources-uat.com\/nchrp1918\/?page_id=785"},"modified":"2023-01-12T19:09:34","modified_gmt":"2023-01-12T19:09:34","slug":"41-test-execution-and-analysis","status":"publish","type":"page","link":"https:\/\/crp.trb.org\/nchrpwebresource2\/setup\/41-test-execution-and-analysis\/","title":{"rendered":"(41) Test Execution and Analysis"},"content":{"rendered":"\n
\n
\n
\n
RESEARCH AND PLANNING<\/a>  |   SETUP<\/a><\/span>  |   ONGOING OPERATIONS<\/a>  | TRANSITIONING AND GROWING<\/a><\/div><\/div> \n
\n

Test Execution and Analysis (41)<\/h1>\n

Description:<\/strong><\/h3> \n

\n \n \n<\/p>

Test execution and analysis involves testing the actual RUC system by conducting the execution test scripts (see Test Plan and Scripts<\/a><\/i><\/b> building block), recording test results, correcting discovered issues, and retesting after issues are corrected.\n <\/p>\n

\n \n
\n

Details:<\/strong><\/h3>\n

The vendor executes unit tests, and the state validates the vendor\u2019s unit test results based on the test script and specification documents. When integration tests are needed, the developers of both systems participate, and the state validates the test results. The state designs and oversees system acceptance testing, or end-to-end testing, with support from the vendors. Small-scale operational trials can be carried out when system corrections based on end-to-end test results are complete.\n <\/p>\n <\/div>\n

\n
\n

Primary Use:<\/strong><\/h3>\n

Check system behavior and performance and correct issues discovered.\n <\/p>\n <\/div>\n \n

\n \n
\n

Best Practices\/Lessons Learned:<\/strong><\/h3>\n