commit | 50dbfee6b8a2fa03269c4c1339e4d970cd127d5f | [log] [tgz] |
---|---|---|
author | David Haddock <dhaddock@chromium.org> | Fri Jan 12 12:43:12 2018 -0800 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Jan 18 17:40:26 2018 -0800 |
tree | ed0ed15dec774f6649b66354f5c1fa7345f663eb | |
parent | 634c6c8eb63068d85a5b79a34c807ded52c77287 [diff] |
Create a function that all AU tests can call to get an update url. Each AU test needs a slightly different setup but ultimately they just want an update url to call and don't care about where that url comes from or where the payloads are staged. This functionality has lived in each test but I think it is cleaner to have one function in the base test class that figures it out and just returns the test the update url to use. BUG=chromium:799713 TEST=autoupdate_P2P, autoupdate_ForcedOOBEUpdate, autoupdate_EndToEndTest still pass Change-Id: I56c6b00f0fbc8f9a3b7b988c9f3f252960364d9b Reviewed-on: https://chromium-review.googlesource.com/865287 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: David Haddock <dhaddock@chromium.org> Reviewed-by: danny chan <dchan@chromium.org> Reviewed-by: 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.