commit | 6d6c32ce5eecc1de980c43c65b4f6439a594fc0d | [log] [tgz] |
---|---|---|
author | Yicheng Li <yichengli@chromium.org> | Thu Jan 16 12:09:25 2020 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 31 19:47:58 2020 +0000 |
tree | affbd6f4b529ad5153af185344820b7e515372f6 | |
parent | c148618e07fe0d18f84bdf4200cdd7278d9cc731 [diff] |
cros/faft: Add statically built futility Some faft tests rely on futility to re-sign firmware images with dev keys. However, futility is not available in the base container used on lab servers. Add statically built futility so that these tests can run on lab servers. futility in this change was built in the following way: (In chroot) cd ~/trunk/src/platform/vboot_reference (Open Makefile) (Remove -Wimplicit-fallthrough from COMMON_FLAGS) (Remove the line "${FUZZ_TEST_BINS}: LDFLAGS += -fsanitize=fuzzer") rm -rf build && make STATIC=1 futil -j BUG=chromium:961293, chromium:1003023 TEST=test_that --board=nocturne <IP> suite:fingerprint TEST=(In chroot) cd ~/trunk/src/third_party/autotest tar -cvjSf autotest_server_package.tar.bz2 \ --exclude "files/ExternalSource" --exclude "files/site-packages" \ --exclude "files/client" files/ (Copy the resulting tarball to base container's /usr/local and extract there) (Copy nocturne_fp_v2.2.191-1d529566e.bin to container's /usr/local) (In base container) cd /usr/local/files/server/cros/faft ./gen_test_images.sh nocturne_fp \ /usr/local/nocturne_fp_v2.2.191-1d529566e.bin Change-Id: I75ab466b4f85c8bb96e698d1d48f6691ecd63735 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2006017 Reviewed-by: Wai-Hong Tam <waihong@google.com> Reviewed-by: Tom Hughes <tomhughes@chromium.org> Tested-by: Yicheng Li <yichengli@chromium.org> Tested-by: Tom Hughes <tomhughes@chromium.org> Commit-Queue: Tom Hughes <tomhughes@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.