| commit | 3b393108879e2b353fbafdeb5e29b6d7ec548b72 | [log] [tgz] |
|---|---|---|
| author | Ilja H. Friedel <ihf@chromium.org> | Mon Jun 27 21:43:48 2016 -0700 |
| committer | Ilja H. Friedel <ihf@chromium.org> | Tue Jun 28 04:53:40 2016 +0000 |
| tree | 20bf4afbc33293d5e5648338d9b270c30cdc1573 | |
| parent | 79d2bdbbe7169fdd66784004745f25736415d3aa [diff] |
hardware_StorageWearoutDetect: move to bvt-perbuild. This is a good test. The problem is it detects hardware health of an individual DUT. By the time the DUT is replaced random machine allocation causes flakes. For this reason it can't be in bvt-cq. BUG=chromium:589344 TEST=https://wmatrix.googleplex.com/bvt-cq hardware_StorageWearoutDetect View test details and logs for hardware_StorageWearoutDetect. R53-8458.0.0 R53-8460.0.0 R53-8462.0.0 R53-8462.0.0-rc2 R53-8463.0.0-rc2 R53-8479.0.0 R53-8484.0.0 R53-8485.0.0 R53-8486.0.0 R53-8491.0.0 R53-8500.0.0 R53-8502.0.0 R53-8504.0.0 R53-8506.0.0 R53-8510.0.0 celes edgar expresso peach_pit veyron_jaq veyron_mighty winky Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_A Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_B Detected wearout parameter:MMC failure DEVICE_LIFE_TIME_EST_TYP_BMMC failure DEVICE_LIFE_TIME_EST_TYP_A FAIL bvt-cq Mon Jun 27, 22:52 ... Change-Id: I57ac64f6ead54541e3948f3b88604e2494ba54d3 Reviewed-on: https://chromium-review.googlesource.com/356581 Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Tested-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.