commit | c527bcc4ce659e27c76d427a6f7844c4e5617bc8 | [log] [tgz] |
---|---|---|
author | Daniel Erat <derat@chromium.org> | Sun Jun 17 07:02:01 2018 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Jun 21 08:14:22 2018 -0700 |
tree | c9a3879fac29d13d074ff312addaccd924486a0a | |
parent | 44aca32e77f0931458d26cb949207a4239f5a6dc [diff] |
autotest: Add tast.informational and tast.must_pass. Add control files for new tast.informational and tast.must_pass server tests and remove the existing tast.bvt test. Both of the new tests run in bvt-perbuild initially. BUG=chromium:853545 TEST=none CQ-DEPEND=Ice0d28ad5c27ca019667f5f2baba43c986ec57d9 Change-Id: I3abb61d2999c22ed110d9e6ec1d405333d2051ea Reviewed-on: https://chromium-review.googlesource.com/1105132 Commit-Ready: Dan Erat <derat@chromium.org> Tested-by: Dan Erat <derat@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@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.
You need to run utils/build_externals.py
to set up the dependencies for pre-upload hook tests.