commit | 05ae2a45397188dd7d7adbc49a61095ebf85e151 | [log] [tgz] |
---|---|---|
author | Kevin Cheng <kevcheng@chromium.org> | Mon Jun 06 10:12:48 2016 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Mon Jul 11 21:27:58 2016 -0700 |
tree | 2c404e897ad63415fb2c684f775927baffe77cb9 | |
parent | c5996fbae3c6c743b1c22000c210c509cadf653b [diff] |
[autotest] Store afe_host in and remove host attributes to/from machine dict. There are multiple times when the AFE is queried for random bits of info (host attibutes, labels, etc). To reduce the number of calls, store the AFE host object into the machine dict so we can store it into the host class. I chose the AbstractSSHHost class to grab it out of the arg dict since that is used both by CrosHost and ADBHost. Also removed host attributes as a class instance attribute since afe_host contains all that info already. Also use the os labels to do host class detection. BUG=chromium:546741 TEST=Tested a couple scenarios: - Manually on moblab to make sure cros/adb/testbed devices all pass dummy tests. - Trybot job on gnawty-paladin. - Moblab dummy suite run to ensure no breaking backward compatibility changes (moblab on R52 and testing with a tryjob gnawty build). - test_{that,droid}.py on a cros/adbhost device. Change-Id: I101c478c0f27f9fd444ccd4699a5c94e76d3b17e Reviewed-on: https://chromium-review.googlesource.com/349990 Commit-Ready: Kevin Cheng <kevcheng@chromium.org> Tested-by: Kevin Cheng <kevcheng@chromium.org> Reviewed-by: Kevin Cheng <kevcheng@chromium.org>
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.
See the guides to test_that
and test_droid
:
See the best practices guide, existing tests, and comments in the code.
git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
See the coding style guide for guidance on submitting patches.