| commit | c0ce5456d710eb5f9410e183fe768c216509e4b1 | [log] [tgz] |
|---|---|---|
| author | Ben Kwa <kenobi@google.com> | Wed Jul 12 12:12:46 2017 +0800 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Jul 13 11:44:40 2017 -0700 |
| tree | e008063c986328d2c2ac7bc4587a4da7fe2c8f6e | |
| parent | 7b8e9b580b9883fc60bee7d26973c6d8d14cb5c8 [diff] |
autotest: reland recent lxc changes This reverts commit 1b617599f43e88a40eabbd2570e90649c0ede990, which effectively relands the following commits: d8542a8d5 Address container differences on moblab vs shard. d3498cc07 Create Zygote, a configurable container. 966db080d Create a new module for lxc code. i.e. https://chromium-review.googlesource.com/c/558015/ https://chromium-review.googlesource.com/c/557061/ https://chromium-review.googlesource.com/c/538127/ It also fixes the problem introduced by those CLs, and adds new unittests (see new container_unittest.py) for those conditions. BUG=chromium:741139, chromium:738598, chromium:720219 TEST=sudo python site_utils/lxc/container_unittest.py -v TEST=sudo python site_utils/lxc/lxc_functional_test.py -v TEST=sudo python site_utils/lxc/zygote_unittest.py -v TEST=sudo python site_utils/lxc/container_bucket_unittest.py -v Change-Id: I6c1c23426a4baf4e12135c4ef8b25fdefabbf46b Reviewed-on: https://chromium-review.googlesource.com/566741 Commit-Ready: Ben Kwa <kenobi@chromium.org> Tested-by: Ben Kwa <kenobi@chromium.org> Reviewed-by: Dan Shi <dshi@google.com>
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.