1 page.title=Interpreting CTS results 2 @jd:body 3 4 <!-- 5 Copyright 2015 The Android Open Source Project 6 7 Licensed under the Apache License, Version 2.0 (the "License"); 8 you may not use this file except in compliance with the License. 9 You may obtain a copy of the License at 10 11 http://www.apache.org/licenses/LICENSE-2.0 12 13 Unless required by applicable law or agreed to in writing, software 14 distributed under the License is distributed on an "AS IS" BASIS, 15 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 16 See the License for the specific language governing permissions and 17 limitations under the License. 18 --> 19 20 <p>The CTS test results are placed in the file:</p> 21 <pre> 22 $CTS_ROOT/android-cts/repository/results/<start_time>.zip 23 </pre> 24 25 <p>If you have built the CTS yourself, <em>$CTS_ROOT</em> will resemble the 26 path <em>out/host/linux-x86/cts</em> but differ by platform. This reflects the 27 path where you have uncompressed the prebuilt official CTS <a 28 href="{@docRoot}compatibility/downloads.html">downloaded</a> from this site.</p> 29 30 <p>Inside the zip, the testResult.xml file contains the actual resultsopen 31 this file in any web browser (HTML5 compatible browser recommended) to view the 32 test results. It will resemble the following screenshots.</p> 33 34 <p class="note"><strong>Note:</strong> The results are provided to help you 35 ensure the software remains compatible throughout the development process and 36 act as a common format for communicating the compatibility status of your 37 device with other parties.</p> 38 39 <img src="images/cts-test-summary.png" alt="CTS test summary" id="figure1" /> 40 <p class="img-caption"> 41 <strong>Figure 1.</strong> CTS test summary 42 </p> 43 44 <p>If testResult.xml displays a blank page when using the Chrome browser, 45 <a href="https://www.chromium.org/developers/how-tos/run-chromium-with-flags">change 46 your browser configuration</a> to enable the 47 <em>--allow-file-access-from-files</em> command line flag.</p> 48 49 <p>The Device Information section provides details about the device, firmware 50 (make, model, firmware build, platform), and device hardware (screen 51 resolution, keypad, screen type). To access device information, click the link 52 above Test Summary.</p> 53 54 <p>The <em>Test Summary</em> section provides executed test plan details, like 55 the CTS plan name and execution start and end times. It also presents an 56 aggregate summary of the number of tests that passed, failed, timed out, or 57 could not be executed.</p> 58 <p>The next section also provides a summary of tests passed per package.</p> 59 60 <img src="images/cts-test-report.png" alt="CTS detailed test report" id="figure2" /> 61 <p class="img-caption"> 62 <strong>Figure 2.</strong> CTS test report 63 </p> 64 65 <p>This is followed by details of the the actual tests that were executed. The 66 report lists the test package, test suite, test case, and the executed tests. 67 It shows the result of the test executionpass, fail, timed out, or not 68 executed. In the event of a test failure details are provided to help diagnose 69 the cause.</p> 70 71 <p>Further, the stack trace of the failure is available in the XML file but is 72 not included in the report to ensure brevityviewing the XML file with a text 73 editor should provide details of the test failure (search for the 74 <em><Test></em> tag corresponding to the failed test and look within it 75 for the <em><StackTrace></em> tag).</p> 76
