[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-05-08。"],[],[],null,["# Interpret CTS results\n\nThe CTS test results are placed in the file: \n\n```\nCTS_ROOT/android-cts/results/start_time.zip\n```\n\nIf you have built the CTS yourself, \u003cvar translate=\"no\"\u003eCTS_ROOT\u003c/var\u003e resembles\n`out/host/linux-x86/cts` but differs by platform. This reflects the path where\nyou have uncompressed the prebuilt official CTS\n[downloaded](/docs/compatibility/cts/downloads) from this site.\n\nInside the zip, the test_result.xml file contains the actual results.\n\nDisplay Android 10 and later results\n------------------------------------\n\nA test_result.html file exists within the zip archive, you can directly open it\nin any HTML5-compatible web browser\n\nDisplay Pre-Android 10 results\n------------------------------\n\nOpen test_result.xml file in any HTML5-compatible web browser to view the test\nresults\n\nIf this file displays a blank page when using the Chrome browser,\n[change your browser configuration](https://www.chromium.org/developers/how-tos/run-chromium-with-flags)\nto enable the `--allow-file-access-from-files` command line flag.\n\nRead the test results\n---------------------\n\nThe details of the test results depend on which version of CTS you are using:\n\n- CTS v1 for Android 6.0 and earlier\n- CTS v2 for Android 7.0 and later\n\n| **Note:** The results are provided to help you ensure the software remains compatible throughout the development process and act as a common format for communicating the compatibility status of your device with other parties.\n\n### Device information\n\nIn CTS v1 and earlier, select Device Information (link above Test Summary) to\nview details about the device, firmware (make, model, firmware build, platform),\nand device hardware (screen resolution, keypad, screen type). CTS v2 does not\ndisplay device information.\n\n### Test summary\n\nThe *Test Summary* section provides executed test plan details, such as the CTS\nplan name and execution start and end times. It also presents an aggregate\nsummary of the number of tests that passed, failed, timed out, or could not be\nexecuted.\n| **Note:** **Ignored** means that the test did not run at all and was completely skipped. **Assumption Failure** means that some precondition of the test isn't met and the test was aborted. Both Ignored and Assumption Failure are treated as Pass.\n\n### Android 10 CTS sample test summary\n\n**Figure 1:** Android 10 CTS sample test summary\n\n### CTS v2 sample test summary\n\n**Figure 2:** CTS v2 sample test summary\n\n### CTS v1 sample test summary\n\n**Figure 3:** CTS v1 sample test summary\n\n### Test report\n\nThe next section, the CTS test report, provides a summary of tests passed per\npackage.\n\nThis is followed by details of the actual tests that were executed. The report\nlists the test package, test suite, test case, and the executed tests. It shows\nthe result of the test execution---pass, fail, timed out, or not executed. In the\nevent of a test failure details are provided to help diagnose the cause.\n\nFurther, the stack trace of the failure is available in the XML file but is not\nincluded in the report to ensure brevity---viewing the XML file with a text editor\nshould provide details of the test failure (search for the *\\[Test\\]* tag\ncorresponding to the failed test and look within it for the *\\[StackTrace\\]* tag).\n\n### Show CTS v2 sample test report\n\n**Figure 4:** CTS v2 sample test report\n\n### Show CTS v1 sample test report\n\n**Figure 5:** CTS v1 sample test report\n\nReview test_result.xml for incomplete test modules\n--------------------------------------------------\n\nTo determine the number of incomplete modules in a given test session, run\ncommand 'list results'. The count of Modules Completed and Total Modules are\nlisted for each previous session. To determine which modules are complete vs.\nincomplete, open the test_result.xml file and read the value of the \"done\"\nattribute for each module in the result report. Modules with value done =\n\"false\" have not run to completion.\n\nTriage test failures\n--------------------\n\nUse the following suggestions to triage test failures.\n\n- Verify your [CTS environment](/docs/compatibility/cts/setup) is set up correctly, if a test is failing due to incorrect preconditions. This includes the physical environment, desktop machine setup, and Android device setup.\n- Verify device stability, test setup, or environment problems, if a test is appearing excessively flaky.\n- Retry the test in isolation if still failing.\n- Check for external factors causing test failures, such as:\n - Environmental setup. For example, a misconfigured desktop machine setup may be the cause of test failures occurring on all Device-Under- Test (DUTs) (including reference devices).\n - External dependencies. For example, if a test fails on all devices in multiple sites starting at a specific point in time, a bad URL might be at fault.\n - If DUT does not include the security patch, its security test failure is expected.\n- Validate and analyze the differences between passing and failing devices.\n- Analyze the assertion, log, bugreport, and the [CTS source](https://android.googlesource.com/platform/cts/). For a HostTest, assertion and log can be very generic so it is helpful to also check and attach device logcat.\n- Submit a test improvement patch to help reducing test failures.\n\nSave partial results\n--------------------\n\nTradefed doesn't save partial test results when the test invocation fails.\n\nWhen Tradefed is not generating any test results, it's implied that a serious issue has\noccurred during the test run, thus making the test result untrustworthy.\nThe partial result is deemed unhelpful as it doesn't provide value when\ninvestigating device issue."]]
