| commit | 82c94ad3961a0a1f7d6453c979895cf905f76676 | [log] [tgz] |
|---|---|---|
| author | Ruben Rodriguez Buchillon <coconutruben@chromium.org> | Mon Sep 30 14:49:25 2019 -0700 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 06 05:25:22 2020 +0000 |
| tree | a2d7bb27995e39331ecb37f208e8c101542f3410 | |
| parent | f3f63b5971a4c0eb4e88c96d2e1d9cec71a0f3f7 [diff] |
servo: abstract dts mode logic
This change adds a few helpers to handle dts mode
- dts_mode_is_valid: whether dts mode can be supported.
- dts_mode_is_safe: whether controlling dts mode will remove the
main device's console access
- get_dts_mode: helper to get the dts mode
BUG=chromium:1009616
TEST=test_that --autotest_dir . $DIP firmware_Cr50CCDServoCap
/tmp/test_that_results_b2EdTg/results-1-firmware_Cr50CCDServoCap
[ PASSED ]
Note: all tests below are done by adding two logging statements into
initialize_dut() and subsequently asseting False to speed debug.
TEST=sudo servod -b atlas // v4 (type-c) + micro
test_that --autotest_dir . $AIP power_Monitoring -b atlas
12:03:08 INFO | autoserv| TYPE: servo_v4_with_servo_micro
12:03:08 INFO | autoserv| DTS MODE: True
TEST=sudo servod -b atlas // v4 (type-c) + ccd
test_that --autotest_dir . $AIP power_Monitoring -b atlas
12:05:20 INFO | autoserv| TYPE: servo_v4_with_ccd_cr50
12:05:20 INFO | autoserv| DTS MODE: True
TEST=sudo servod -b atlas // v4 (type-A) + micro
test_that --autotest_dir . $AIP power_Monitoring -b atlas
12:06:49 INFO | autoserv| TYPE: servo_v4_with_servo_micro
12:06:50 INFO | autoserv| DTS controls require a type-c servo v4.
12:06:50 INFO | autoserv| DTS MODE: False
TEST=sudo servod -b atlas // v2
test_that --autotest_dir . $AIP power_Monitoring -b atlas
12:08:19 INFO | autoserv| TYPE: servo_v2
12:08:19 INFO | autoserv| DTS MODE: False
Change-Id: I7f342691bf84896df5a779555bf33334ff1c17b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1835913
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.