1 <html devsite> 2 <head> 3 <title>Interpreting CTS results</title> 4 <meta name="project_path" value="/_project.yaml" /> 5 <meta name="book_path" value="/_book.yaml" /> 6 </head> 7 <body> 8 <!-- 9 Copyright 2017 The Android Open Source Project 10 11 Licensed under the Apache License, Version 2.0 (the "License"); 12 you may not use this file except in compliance with the License. 13 You may obtain a copy of the License at 14 15 http://www.apache.org/licenses/LICENSE-2.0 16 17 Unless required by applicable law or agreed to in writing, software 18 distributed under the License is distributed on an "AS IS" BASIS, 19 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 20 See the License for the specific language governing permissions and 21 limitations under the License. 22 --> 23 24 25 26 <p>The CTS test results are placed in the file:</p> 27 <pre class="devsite-click-to-copy"> 28 $CTS_ROOT/android-cts/repository/results/<start_time>.zip 29 </pre> 30 31 <p>If you have built the CTS yourself, <em>$CTS_ROOT</em> will resemble the 32 path <em>out/host/linux-x86/cts</em> but differ by platform. This reflects the 33 path where you have uncompressed the prebuilt official CTS <a 34 href="downloads.html">downloaded</a> from this site.</p> 35 36 <p>Inside the zip, the testResult.xml file contains the actual results. Open 37 this file in any web browser (HTML5 compatible browser recommended) to view the 38 test results.</p> 39 40 <p>If testResult.xml displays a blank page when using the Chrome browser, 41 <a href="https://www.chromium.org/developers/how-tos/run-chromium-with-flags">change 42 your browser configuration</a> to enable the 43 <em>--allow-file-access-from-files</em> command line flag.</p> 44 45 <h3 id="reading-the-test-results">Reading the test results</h3> 46 47 <p>The details of the test results depend on which version of CTS you are 48 using:</p> 49 50 <ul> 51 <li>CTS v1 for Android 6.0 and earlier</a> 52 <li>CTS v2 for Android 7.0 and later</a> 53 </ul> 54 55 <p class="note"><strong>Note:</strong> The results are provided to help you 56 ensure the software remains compatible throughout the development process and 57 act as a common format for communicating the compatibility status of your 58 device with other parties.</p> 59 60 <h4 id="device-information">Device Information</h4> 61 62 <p>In CTS v6.0 and earlier, select Device Information (link above Test Summary) to 63 view details about the device, firmware (make, model, firmware build, 64 platform), and device hardware (screen resolution, keypad, screen type). (CTS 65 v7.0 does not display device information.)</p> 66 67 <h4 id="test-summary">Test Summary</h4> 68 69 <p>The <em>Test Summary</em> section provides executed test plan details, like 70 the CTS plan name and execution start and end times. It also presents an 71 aggregate summary of the number of tests that passed, failed, timed out, or 72 could not be executed.</p> 73 74 <section class="expandable"> 75 <h4 class="showalways">Show CTS v1 sample test summary</h4> 76 <img src="/compatibility/cts/images/cts-test-summary.png" alt="CTS v1 test summary" id="figure1a" /> 77 <p class="img-caption"><strong>Figure 1a.</strong> CTS v1 sample test summary </p> 78 </section> 79 80 81 <section class="expandable"> 82 <h4 class="showalways">Show CTS v2 sample test summary</h4> 83 <img src="/compatibility/cts/images/cts-v2-test-summary.png" alt="CTS v2 test summary" id="figure1b" /> 84 <p class="img-caption"><strong>Figure 1b.</strong> CTS v2 sample test summary </p> 85 </section> 86 87 <p> </p> 88 89 90 <h4 id="test-report">Test Report</h4> 91 <p>The next section, the CTS test report, provides a summary of tests passed per package.</p> 92 93 <p>This is followed by details of the actual tests that were executed. The 94 report lists the test package, test suite, test case, and the executed tests. 95 It shows the result of the test executionpass, fail, timed out, or not 96 executed. In the event of a test failure details are provided to help diagnose 97 the cause.</p> 98 99 <p>Further, the stack trace of the failure is available in the XML file but is 100 not included in the report to ensure brevityviewing the XML file with a text 101 editor should provide details of the test failure (search for the 102 <em><Test></em> tag corresponding to the failed test and look within it 103 for the <em><StackTrace></em> tag).</p> 104 105 <section class="expandable"> 106 <h4 class="showalways">Show CTS v1 sample test report</h4> 107 <img src="/compatibility/cts/images/cts-test-report.png" alt="CTS v1 test report" id="figure2a" /> 108 <p class="img-caption"><strong>Figure 2a.</strong> CTS v1 sample test report</p> 109 </section> 110 111 <section class="expandable"> 112 <h4 class="showalways">Show CTS v2 sample test report</h4> 113 <img src="/compatibility/cts/images/cts-v2-test-report.png" alt="CTS v2 test report" id="figure2b" /> 114 <p class="img-caption"><strong>Figure 2b.</strong> CTS v2 sample test report</p> 115 </section> 116 117 <p> </p> 118 119 <h3 id="incomplete-test-modules">Reviewing test_result.xml for incomplete test modules</h3> 120 121 <p> 122 To determine the number of incomplete modules in a given test session, run 123 command 'list results'. The count of Modules Completed and Total Modules are 124 listed for each previous session. To determine which modules are complete vs. 125 incomplete, open the test_result.xml file and read the value of the "done" 126 attribute for each module in the result report. Modules with value done = 127 "false" have not run to completion. 128 </p> 129 130 </body> 131 </html> 132
