commit | 825cf8646074cd91c7f5a9e86ba4d16fdcdbab5f | [log] [tgz] |
---|---|---|
author | Keith Haddow <haddowk@chromium.org> | Wed May 31 22:35:23 2017 -0700 |
committer | Ilja H. Friedel <ihf@chromium.org> | Sat Jun 03 01:13:27 2017 +0000 |
tree | 124ff4413010ce075b7217e7a2a40c93350e370d | |
parent | 7fffc705bfc249b3fc386ae64c391a5bfea516b9 [diff] |
[autotest] Add CTS test to collect the cannonical test list. CTS dashboard now shows expected tests for each device and CTS version we need partner to supply this information since some devices will not be in our lab, add a new test to each ABI of CTS to collect all the expected tests. test_that 100.107.3.139 cheets_CTS_N.x86.tradefed-run-collect-tests-only test_that 100.107.3.139 cheets_CTS_N.arm.tradefed-run-collect-tests-only test_that 100.107.3.139 cheets_CTS_N.x86.CtsWebkitTestCases BUG=b:62101940 TEST=test that commands Change-Id: I69070e99790333e3f1d9495e0308eb929dcb93de Reviewed-on: https://chromium-review.googlesource.com/520574 Commit-Ready: Keith Haddow <haddowk@chromium.org> Tested-by: Keith Haddow <haddowk@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Reviewed-by: Keith Haddow <haddowk@chromium.org> Reviewed-by: Rohit Makasana <rohitbm@chromium.org> (cherry picked from commit 094111b2ea208ca0e76d11332aaea69128a2f816) Reviewed-on: https://chromium-review.googlesource.com/522352 Tested-by: Ilja H. Friedel <ihf@chromium.org> (cherry picked from commit 9be2c1c03523a14ed8d50aa80ee69c163def8380) Reviewed-on: https://chromium-review.googlesource.com/522936
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.