History

liiir1985 ad350b4d66 补上遗漏的文件		2024-07-01 23:19:47 +08:00
..
bin	initial	2024-06-22 20:45:49 +08:00
cli	initial	2024-06-22 20:45:49 +08:00
client	initial	2024-06-22 20:45:49 +08:00
contrib	initial	2024-06-22 20:45:49 +08:00
database	initial	2024-06-22 20:45:49 +08:00
docs	initial	2024-06-22 20:45:49 +08:00
frontend	initial	2024-06-22 20:45:49 +08:00
logs	initial	2024-06-22 20:45:49 +08:00
metadata	补上遗漏的文件	2024-07-01 23:19:47 +08:00
results	initial	2024-06-22 20:45:49 +08:00
server	initial	2024-06-22 20:45:49 +08:00
site_utils	initial	2024-06-22 20:45:49 +08:00
test_suites	initial	2024-06-22 20:45:49 +08:00
tko	initial	2024-06-22 20:45:49 +08:00
utils	initial	2024-06-22 20:45:49 +08:00
venv	initial	2024-06-22 20:45:49 +08:00
.style.yapf	initial	2024-06-22 20:45:49 +08:00
CTS_OWNERS	initial	2024-06-22 20:45:49 +08:00
ENGPROD_OWNERS	initial	2024-06-22 20:45:49 +08:00
FINGERPRINT_OWNERS	initial	2024-06-22 20:45:49 +08:00
FIRMWARE_OWNERS	initial	2024-06-22 20:45:49 +08:00
INFRA_OWNERS	initial	2024-06-22 20:45:49 +08:00
LGPL_LICENSE	initial	2024-06-22 20:45:49 +08:00
LICENSE	initial	2024-06-22 20:45:49 +08:00
METADATA	initial	2024-06-22 20:45:49 +08:00
MODULE_LICENSE_LGPL	initial	2024-06-22 20:45:49 +08:00
OWNERS.android	initial	2024-06-22 20:45:49 +08:00
PRESUBMIT.cfg	initial	2024-06-22 20:45:49 +08:00
PRESUBMIT.py	initial	2024-06-22 20:45:49 +08:00
README.md	initial	2024-06-22 20:45:49 +08:00
__init__.py	initial	2024-06-22 20:45:49 +08:00
common.py	initial	2024-06-22 20:45:49 +08:00
global_config.ini	initial	2024-06-22 20:45:49 +08:00
main.star	initial	2024-06-22 20:45:49 +08:00
moblab_config.ini	initial	2024-06-22 20:45:49 +08:00
ssp_deploy_config.json	initial	2024-06-22 20:45:49 +08:00

README.md

Autotest: Automated integration testing for Android and Chrome OS Devices

Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.

Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:

A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.
A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.
Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.
Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.
Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.