 Welcome to the CTS Learning Series, Chapter 6, Testing an OSS UOC Example. Video 5, Review of Testing Result. In this video, we will explore where an OSS Conformance Testing Report is generated, analyze the contents of the report, and explain the conformance tests that resulted in failure. The Conformance Test Report is generated in the same directory the Project Configuration file is located. For our case, the Project Configuration files were located in the CTS Learning Series directory. OSS Conformance Test Reports look very similar to Non-OSS Test Reports, but the tests are executed differently than Non-OSS tests, as explained in Chapter 6, Video 2. In our case, since we only selected the C++ runtime based on the general profile, the CTS has called each of the required functions that should be supplied by the C++ runtime. If the test failed, the C++ function does not exist in the C++ standard libraries. Take the tests executed for C time. If we expand C time in the Navigation pane, we can see some tests passed and some tests failed. Local time underscore R has failed, for example. In searching through the C++ standard libraries, we can see that GNU does supply local time R, but not in the standard library, which is a requirement of the FaceTesticle standard, thus resulting in failure. The other failing results contained in the test report are also because GNU does not supply the required function in their C++ standard library. Thank you for watching. This concludes Chapter 6, Testing in OSS-UOC, Video 5, Review of Testing Result. This also concludes Chapter 6.