commit | f143424edb423ecfe5db524c5bf70da0ffe90ed0 | [log] [tgz] |
---|---|---|
author | Shelley Chen <shchen@chromium.org> | Thu Feb 22 23:48:50 2018 -0800 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri Feb 23 23:13:04 2018 -0800 |
tree | 8b6de2b28d497148c250272b4bafbdb3396f6949 | |
parent | 175bce0f4cd2b328baf17163d25329e6f269575f [diff] |
firmware_CorruptRecoveryCache: Ensure init/restore DUT state This test needs memory training to be done before the start of the test, but never makes sure that this is the case. So, it's possible if the DUT was flashed right before running this test that we fail the 3-key recovery test because we are doing memory training. Added an extra recovery boot at the beginning of the test to make sure memory training is done. Also, the test never cleans up after it runs and exits with the DUT in recovery mode because of the 4-key recovery test. Added an extra reboot to ensure that DUT is not in recovery mode. Additionally, this test was saving and restoring the firmware, but the test itself never corrupts the firmware. So, there's no reason for this to be done. BUG=b:73293232 BRANCH=None TEST=run firmware_CorruptRecoveryCache Change-Id: I5ea34e695f5ab1bb2f2f513da5af851dc701fa46 Signed-off-by: Shelley Chen <shchen@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/934146 Reviewed-by: Furquan Shaikh <furquan@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.