| commit | 8ad6c625877be2276428da8cee01cf55784a51d4 | [log] [tgz] |
|---|---|---|
| author | Mary Ruthven <mruthven@chromium.org> | Tue Oct 08 17:57:08 2024 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 04 01:05:51 2024 |
| tree | 859c67d9fa170d7fea8526939f76d08cab666338 | |
| parent | 594a82577b4b455945cc232e29b63efbd598e944 [diff] |
Reland "chrome_ti50: fail test if "externally driven!" message shows up" This is a reland of commit 024ceca55992a58a1469f5a5e0c167aecf3fe2cf Original change's description: > chrome_ti50: fail test if "externally driven!" message shows up > > "externally driven!" means that the external WP signal doesn't match the > WP state ti50 is trying to set. It shouldn't happen. Servod sets the > ti50 WP state before driving the signal. > > Fail the test if "externally driven!" shows up in the logs, so we can > see what tests trigger the issue. > > This CL may need to be reverted if it causes a lot of tests to fail. > > BUG=none > TEST=none > > Change-Id: Id5c971ab998f423628d879e0bbe69139446ba5e5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/5916831 > Tested-by: Mary Ruthven <mruthven@chromium.org> > Reviewed-by: Jett Rink <jettrink@google.com> > Commit-Queue: Mary Ruthven <mruthven@chromium.org> Bug: none Change-Id: I311d50d4d69c9711da59cc0ef8807cd540db829d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/6067031 Commit-Queue: Jett Rink <jettrink@google.com> Reviewed-by: Jett Rink <jettrink@google.com> Auto-Submit: Mary Ruthven <mruthven@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.