blob: c8468d1f46c316820b6ae12e70458792a2601230 [file] [log] [blame]
Clay Murphy468ba572015-04-13 18:25:11 -07001page.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/&lt;start_time>.zip
23</pre>
24
25<p>If you have built the CTS yourself, <em>$CTS_ROOT</em> will resemble the
26path <em>out/host/linux-x86/cts</em> but differ by platform. This reflects the
27path where you have uncompressed the prebuilt official CTS <a
Clay Murphy929f39c2015-05-04 17:08:07 -070028href="{@docRoot}compatibility/downloads.html">downloaded</a> from this site.</p>
Clay Murphy468ba572015-04-13 18:25:11 -070029
30<p>Inside the zip, the testResult.xml file contains the actual resultsopen
31this file in any web browser (HTML5 compatible browser recommended) to view the
32test results. It will resemble the following screenshots.</p>
33
34<img src="images/cts-test-summary.png" alt="CTS test summary" id="figure1" />
35<p class="img-caption">
36 <strong>Figure 1.</strong> CTS test summary
37</p>
38
39<p>The Device Information section provides details about the device, firmware
40(make, model, firmware build, platform), and device hardware (screen
41resolution, keypad, screen type). To access device information, click the link
42above Test Summary.</p>
43
44<p>The <em>Test Summary</em> section provides executed test plan details, like
45the CTS plan name and execution start and end times. It also presents an
46aggregate summary of the number of tests that passed, failed, timed out, or
47could not be executed.</p>
48<p>The next section also provides a summary of tests passed per package.</p>
49
50<img src="images/cts-test-report.png" alt="CTS detailed test report" id="figure2" />
51<p class="img-caption">
52 <strong>Figure 2.</strong> CTS test report
53</p>
54
55<p>This is followed by details of the the actual tests that were executed. The
56report lists the test package, test suite, test case, and the executed tests.
57It shows the result of the test executionpass, fail, timed out, or not
58executed. In the event of a test failure details are provided to help diagnose
59the cause.</p>
60
61<p>Further, the stack trace of the failure is available in the XML file but is
62not included in the report to ensure brevityviewing the XML file with a text
63editor should provide details of the test failure (search for the
64<em>&lt;Test&gt;</em> tag corresponding to the failed test and look within it
65for the <em>&lt;StackTrace&gt;</em> tag).</p>