commit | 6f36a9677123ca15de4fcc144d0be2da449364ad | [log] [tgz] |
---|---|---|
author | Ruben Rodriguez Buchillon <coconutruben@chromium.org> | Wed Oct 02 14:55:59 2019 -0700 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 07 15:26:45 2020 +0000 |
tree | 3c8d19b4ca0811f527becc12c4dd00a69e0cc120 | |
parent | e5fe672aa690496247377ec3e8301fb882ca3a3e [diff] |
servo: add get_servo_fw_versions This change is intended to provide a more portable way for tests that want to record the various servo firmware version on the system to retrieve that information. Now, calling get_servo_fw_versions give a dictionary of servo_type_version.prefix: fw_version This is aimed at the new servod, and this change retrofits the existing servod to that logic. Essentially, the prefix can be thought of as a role as well. For example 'main' is always the device that requires no prefix. There is one special 'prefix' that we manufactur that is 'ccd_flex_secondary' - this means that the device is actually connected to the same DUT as the main device, and providing a flex and ccd dual connection. BUG=chromium:1009616 TEST=test_that --autotest_dir . $DIP firmware_Cr50ConsoleCommands --args "servo_host=$LIP" /tmp/test_that_results_9yxVIF/results-1-firmware_Cr50ConsoleCommands [ PASSED ] cat /tmp/test_that_latest/*/*/results/keyval | grep version ccd_cr50_version.ccd_flex_secondary{attr}=0.3.24/cr50_v1.9308_87_mp.378-4b50ca0 cr50_version{attr}=0.3.24/cr50_v1.9308_87_mp.378-4b50ca0 servo_micro_version.main{attr}=servo_micro_v2.3.7-096c7ee84 servo_v4_version.support{attr}=servo_v4_v2.3.22-ecb74cc56 servod_version{attr}=servod 1.0.0+758c96d // edited to remove all versions other than the servo devices and servod Change-Id: I21b0b70ef8b4a9ba4664ddd84aa3803288cce241 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1835914 Tested-by: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Commit-Queue: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Reviewed-by: Mary Ruthven <mruthven@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.