commit | b4f86fb6aa3cc57c73c6b636fb1645945092b618 | [log] [tgz] |
---|---|---|
author | Mary Ruthven <mruthven@chromium.org> | Mon Aug 07 11:32:49 2023 -0700 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 08 00:35:07 2023 +0000 |
tree | dafcdf88a5347b6528b421413874dabef10beb3a | |
parent | bafd3057533630e67be471bb2edbaad9a43f7ad0 [diff] |
faft-gsc: use gsc_ecrst_pulse to reset the EC Use `ecrst pulse` to reset the EC and enter dev mode. Update faft-gsc tests to use gsc_ecrst_pulse for cold reset. `ecrst pulse` can reset the EC and keep the EC-EFS2 boot mode in sync with the system state when ccd is locked. This changes try to use the ecrst pulse control if it's available. If it isn't, it falls back to uring the old controls. A follow up CL will remove the backup methods after the labstation image has ecrst pulse support in hdctools. BUG=b:294426380 TEST=run firmware_Cr50DevMode and firmware_Cr50Testlab on hatch Change-Id: I97d2affe6cd2e39c6fa7bc80683031e12e936b62 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/4755823 Commit-Queue: Mary Ruthven <mruthven@chromium.org> Reviewed-by: Edward Hill <ecgh@chromium.org> Tested-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 ChromeOS team to validate complete system images of ChromeOS 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 ChromeOS 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 ChromeOS.
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.