commit | b61ec9ef15744696e028d74b0c93b94842726077 | [log] [tgz] |
---|---|---|
author | Otabek Kasimov <otabek@google.com> | Fri Dec 18 02:32:42 2020 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Dec 31 00:52:09 2020 +0000 |
tree | 4db8540b7f68b0a5accc450df429cbf6b7bb4fd0 | |
parent | 1ed19b19b75f839ddcc69fe9d7ac29908a188be1 [diff] |
Revert "deploy: Reboot DUT by cold-reset from servo side" This reverts commit 58d76767c5b34c9adbf23721e50f16b4869eb262. Reason for revert: Possible wrong idea, rollback for re-testing Original change's description: > deploy: Reboot DUT by cold-reset from servo side > > When we do update FW for RO+RW in mostly cases we need reboot the DUT > by cold-reset. > The warm-reset(reboot) is not recommended as reboot after flashing new FW. > > BUG=chromium:1157932, chromium:1105952 > TEST=re-run install-firmware step on not finished deployment step > > ./site_utils/deployment/prepare/main.py --results-dir /tr --hostname chromeos6-row14-rack24-host7 --host-info-file /tr/host_info_store/chromeos6-row14-rack24-host7.store install-firmware > > Change-Id: I99bd4279badc83e9899d54e57e1e61ca5baf5f90 > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2590711 > Tested-by: Otabek Kasimov <otabek@google.com> > Reviewed-by: Garry Wang <xianuowang@chromium.org> > Reviewed-by: Gregory Nisbet <gregorynisbet@google.com> > Commit-Queue: Otabek Kasimov <otabek@google.com> Bug: chromium:1157932 Bug: chromium:1105952 Change-Id: Ie14c8dd133f4c189a22770f1af35945b32e6b368 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2598178 Reviewed-by: Evan Green <evgreen@chromium.org> Reviewed-by: Gregory Nisbet <gregorynisbet@google.com> Reviewed-by: Gregory Nisbet <gregorynisbet@chromium.org> Tested-by: Otabek Kasimov <otabek@google.com> Commit-Queue: Otabek Kasimov <otabek@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.
You need to run utils/build_externals.py
to set up the dependencies for pre-upload hook tests.