commit | fb39b5f12a9460202c22dfa8be901987eb7f840c | [log] [tgz] |
---|---|---|
author | Hsuan Ting Chen <roccochen@chromium.org> | Tue May 17 18:57:36 2022 +0800 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 26 14:03:22 2022 +0000 |
tree | 5d69b7bd36bb848e0e5bae8728635d5fb7c88901 | |
parent | 8c3b46e920f30ca742719df66eb45d8877d164c6 [diff] |
FAFT: MiniOS: Use normal mode in MiniOS related tests After CL:3558060, MiniOS is allowed under both normal and dev mode for images with debug features. Hence, there is no reason to force DUT in dev mode while running MiniOS related tests. Change the behavior from forcing dev mode to forcing normal mode for all the MiniOS related tests, this contains: - firmware_MiniosPriority.* - firmware_MiniosMenu.* - firmware_CorruptMinios.* - firmware_CorruptBothKernelAB Also change the names of related utilities. BUG=b:227382828, b:202217528 TEST=/usr/bin/test_that --fast --no-retry --iterations 1 --board=cherry $DUT_IP --autotest_dir ~/trunk/src/third_party/autotest/files/ firmware_MiniosPriority.minios_a firmware_MiniosPriority.minios_b firmware_CorruptMinios.minios_a firmware_CorruptMinios.minios_b firmware_MiniosMenu firmware_MiniosMenu.old firmware_CorruptBothKernelAB Cq-Depend: chromium:3564250 Change-Id: Id7583ceaa369dfeb51ef6b34ba8758137aaad6ad Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/3650304 Tested-by: Hsuan Ting Chen <roccochen@chromium.org> Commit-Queue: Hsuan Ting Chen <roccochen@chromium.org> Reviewed-by: Yu-Ping Wu <yupingso@chromium.org> Reviewed-by: Jae Hoon Kim <kimjae@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.