|author||Ruben Rodriguez Buchillon <firstname.lastname@example.org>||Tue Mar 09 17:21:25 2021 -0800|
|committer||Commit Bot <email@example.com>||Fri May 14 19:39:31 2021 +0000|
RELAND: servo: build v4p1 layers into autotest This cl was generated running this command: sed -i "s/'$old'/'$new'/g" $(grep -lr "'$old'") The command was run with the following old/new pairs: old: servo_v4_type - new: root.dut_connection_type old: servo_v4_sbu - new: servo_dut_sbu old: servo_v4_role - new: servo_pd_role old: servo_v4_dts_mode - new: servo_dts_mode old: active_v4_device - new: active_dut_controller The list for those is from crrev.com/c/2407392 and crrev.com/c/2693385 Additionally, the firmware retrieval for servo types is adjusted so that v4 and v4p1 are both retrieved with their new shorthand: root.servo_fw_version Note that ultimately, all servo firmwares will be retrieved that way i.e. with a target (e.g. root, main, etc) rather than the type. The type is always baked into the firmware name anyways. BUG=b:180152565 //tests with atlas with v4p1, micro, and ccd TEST=test_that $atlas_ip servo_Verification --args="servo_host=$lip" // all passed //tests with dru with v4, ccd TEST=test_that $atlas_ip servo_Verification --args="servo_host=$lip" // all passed Change-Id: I2b1570fba766d3bc0d246821e6522d745a4e392b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2864008 Tested-by: Ruben Rodriguez Buchillon <firstname.lastname@example.org> Tested-by: Garry Wang <email@example.com> Reviewed-by: Otabek Kasimov <firstname.lastname@example.org> Reviewed-by: Garry Wang <email@example.com> Reviewed-by: Namyoon Woo <firstname.lastname@example.org> Commit-Queue: Ruben Rodriguez Buchillon <email@example.com> (cherry picked from commit 030ff1682045483ae51a7b8a3e526ffde473a1de) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2898002 Reviewed-by: Ruben Rodriguez Buchillon <firstname.lastname@example.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
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.