| James Cook | 25e6a45 | 2017-06-27 14:01:15 -0700 | [diff] [blame] | 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 | AUTHOR = "Chrome OS Team" |
| 6 | NAME = "chrome-informational" |
| 7 | PURPOSE = "Informational tests of chrome" |
| 8 | |
| 9 | TIME = "SHORT" |
| 10 | TEST_CATEGORY = "General" |
| 11 | TEST_CLASS = "suite" |
| 12 | TEST_TYPE = "Server" |
| 13 | |
| 14 | DOC = """ |
| 15 | This suite contains informational tests that: |
| 16 | |
| 17 | * Test Chrome, not Chrome OS |
| 18 | * Require real hardware (for example, to test GPU process init |
| 19 | or display management) |
| 20 | * Should not block uprev of Chrome into Chrome OS |
| 21 | |
| 22 | Chrome tests that do not require real hardware should be |
| 23 | implemented in the Chrome repository as unit_tests or browser_tests. |
| 24 | |
| 25 | Tests in this suite are usually for experimental projects being |
| 26 | implemented behind a flag. Once the Chrome code stabilizes and |
| 27 | the flag is on-by-default the tests should be moved to bvt-cq |
| 28 | to block Chrome uprev if they fail. |
| 29 | |
| 30 | Tests in this suite must be SHORT and should not require any |
| 31 | special lab resources. |
| 32 | |
| 33 | @param build: The name of the image to test. |
| 34 | Ex: veyron_minnie-release/R60-9575.0.0 |
| 35 | @param board: The board to test on. Ex: veyron_minnie |
| 36 | @param pool: The pool of machines to utilize for scheduling. |
| 37 | """ |
| 38 | |
| 39 | import common |
| 40 | from autotest_lib.server.cros import provision |
| 41 | from autotest_lib.server.cros.dynamic_suite import dynamic_suite |
| 42 | |
| 43 | |
| 44 | args_dict['max_runtime_mins'] = 15 |
| 45 | args_dict['name'] = 'chrome-informational' |
| 46 | args_dict['job'] = job |
| 47 | args_dict['version_prefix'] = provision.CROS_VERSION_PREFIX |
| 48 | |
| 49 | dynamic_suite.reimage_and_run(**args_dict) |