xref: /aosp_15_r20/external/autotest/client/site_tests/desktopui_ChromeCheck/control (revision 9c5db1993ded3edbeafc8092d69fe5de2ee02df7)
1# Copyright 2017 The Chromium OS Authors. All rights reserved.
2# Use of this source code is governed by a BSD-style license that can be
3# found in the LICENSE file.
4
5# TEST SOON TO BE DISABLED UNTIL MIGRATED TO PYTHON 3.
6# For instructions on how to: go/tauto-py3-migration
7# To re-enable migrate to Python 3.
8# If the test is not migrated by 1/14/22 it will be deleted.
9
10AUTHOR = "derat, chromeos-ui"
11NAME = "desktopui_ChromeCheck"
12ATTRIBUTES = "suite:bvt-perbuild"
13TIME = "SHORT"
14TEST_CATEGORY = "General"
15TEST_CLASS = "desktopui"
16TEST_TYPE = "client"
17JOB_RETRIES = 0
18
19DOC = """
20Test that Chrome is at least marginally usable.
21
22Uses Telemetry to log in, load a simple HTML page, and log out. Along the way,
23tests that session_manager emits the expected SessionStateChanged D-Bus signal
24about the session starting and that the user's encrypted home directory is
25mounted.
26
27A failure can indicate several things:
28
29- Telemetry-to-Chrome communication isn't working (is Chrome crashing?).
30- Chrome and session_manager aren't coordinating login properly.
31- Chrome is internally broken and can't load web pages.
32- Chrome and cryptohome aren't coordinating user home dir mounting properly.
33
34That's a fairly broad range of causes. They're all covered here with the intent
35of providing a single fast-running, minimally-flaky test that can be used to
36validate new versions of Chrome before integrating them into ChromeOS.
37
38The info log provides high-level information about what the test is doing and
39can hopefully be used to narrow down the location of failure.
40"""
41
42job.run_test('desktopui_ChromeCheck')
43