commit | 6037726d3fb0bcae2c57071339d6e27f7965f4f9 | [log] [tgz] |
---|---|---|
author | Wai-Hong Tam <waihong@google.com> | Thu Mar 01 10:55:39 2018 -0800 |
committer | chrome-bot <chrome-bot@chromium.org> | Wed Feb 06 08:31:58 2019 -0800 |
tree | 8ab96b9a8db50080baff5cc1d840bc4aab4b9af7 | |
parent | c7bd43e2a9837b2dd0a7b36007f7815060cb921d [diff] |
faft: Swap servo v4 role to SNK for recovery USB boot In recovery boot, the locked EC RO doesn't support PD for most of the CrOS devices. The default servo v4 power role is a SRC. The DUT becomes a SNK. Lack of PD makes CrOS unable to do the data role swap from UFP to DFP; as a result, DUT can't see the USB disk and the Ethernet dongle on servo v4. This is a workaround to set servo v4 as a SNK, for every FAFT test which boots into the USB disk in the recovery mode. A test should define the argument used_for_recovery=True in the setup_usbkey(). BUG=b:123719781 TEST=Only use a single-USB-port on a locked Snappy device, which connects to servo v4 with servo micro, and servo v4 connects to Ethernet, USB disk, and power supply. * Run the FAFT test firmware_RecoveryButton.ec_wp which locks EC through WP and boots into the servo v4 USB disk. * Run the firmware_PDProtocol not broken. Change-Id: Id92f6fa8a87405880c17f2853b40dfb2568fce63 Reviewed-on: https://chromium-review.googlesource.com/943832 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Wai-Hong Tam <waihong@google.com> Reviewed-by: Wai-Hong Tam <waihong@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.