| commit | 396d281cd74a26be69ba2d498dab9a679ea812c2 | [log] [tgz] |
|---|---|---|
| author | Amin Hassani <ahassani@chromium.org> | Tue Jun 23 11:20:45 2020 -0700 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Jul 06 16:45:05 2020 +0000 |
| tree | 7ad7755de7e39538b0c39ebe88d8c163158fd24c | |
| parent | 732412fcf3840f55f4e863b20aa9fe1b6c251fb9 [diff] |
autoupdate_EndToEndTest: Use quick-provision for installing the source image Currently, autoupdate_EndToEndTests use AU to install very old images in order to test AU success on old images. This means that newer update_engines should be able to apply a very old update payload. This has caused us issues in many places as it has hindered us to deprecated old features and improve update_engine to a more efficient manner. Now that we have quick provision payloads in release buckets, we can use them to install the source image of end to end test. This CL does that. However, the only caveat here is that the fallback code to provision with AU when the QP fails does not work because the release buckets do not have the test AU payloads in them. So we added a flag (au_fallback) and disabled that fallback. And we added a temporary fallback to the original provision mechanism using the AU payloads. We need to remove this once the EndToEnd tests are stable and showing no sign of failures in quick-provision. BUG=chromium:991421 TEST=test_that --autotest_dir ~/trunk/src/third_party/autotest/files/ --args="target_release=13280.0.0 target_payload_uri='gs://chromeos-releases/dev-channel/reef/13290.0.0/payloads/chromeos_13290.0.0_reef_dev-channel_full_test.bin-gvswkobwg43gf4byzyw75rj4io3sl5y5' source_release=13280.0.0 source_payload_uri='gs://chromeos-releases/dev-channel/reef/13290.0.0/payloads/chromeos_13290.0.0_reef_dev-channel_full_test.bin-gvswkobwg43gf4byzyw75rj4io3sl5y5' update_type=full" chromeos6-row4-rack10-host12.cros.corp.google.com autoupdate_EndToEndTest TEST=above test after raising an exception in _quick_provision_with_gs_cache() to make sure _quick_provision_with_devserver() works too. Change-Id: I1ac1828f58c9a63f4a7d8888e651248033d567ef Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2261239 Tested-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Kyle Shimabukuro <kyleshima@chromium.org> Reviewed-by: David Haddock <dhaddock@chromium.org> Commit-Queue: Amin Hassani <ahassani@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.