commit | 73c381f2820cb338a609382ac310b585e404c68f | [log] [tgz] |
---|---|---|
author | Vadim Bendebury <vbendeb@chromium.org> | Wed Jun 13 19:11:58 2018 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri Jun 15 15:26:26 2018 -0700 |
tree | b58554c2a11012a75f544f6eef17fc86a9f8de1f | |
parent | 13332ae8c1e50483c7940e2f7db3d0f19f06fa17 [diff] |
platform_Flashrom: account for unibuild firmware tarballs The platform_Flashrom test at one point tries to reprogram the DUT flash device with the BIOS image from chromeos-firmwareupdate self extracting archive. The test expects to see the bios.bin file in the top level directory created when the tarball is unpacked. With recent introduction of the unibuild there could be multiple bios images in the same tarball, located in the models subdirectory. This patch modifies the test to use the FirmwareUpdater() class to properly locate the bios image matching the model the test is running on. Also removed the unused re import, as suggested by the linter. BRANCH=none BUG=b:79492818 TEST=verified that platform_Flashrom test passes on Fizz(unibuild) and Pyro(single bios.bin). Change-Id: I1787c8c14c69f8da4860224b93d62b52ed6e4f7d Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1100492 Reviewed-by: Wai-Hong Tam <waihong@google.com>
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.