| commit | ac21089415e799768a73a8d31186b6aeb58c8158 | [log] [tgz] |
|---|---|---|
| author | David Haddock <dhaddock@chromium.org> | Mon Feb 05 20:36:27 2018 -0800 |
| committer | chrome-bot <chrome-bot@chromium.org> | Wed Feb 14 04:07:14 2018 -0800 |
| tree | 4393cca973a80da36a35ecd1f3e25ff96f1c131f | |
| parent | 84d15655c6120786a1f16e8376c1fe768181ca17 [diff] |
Forced OOBE Update over cellular.
We already have a forced OOBE update test but we want to have a test for
cellular as a few devices will be shipping with LTE.
Working with cellular means the test can no longer use a devserver in the lab.
It cannot verify the update worked successfully by checking the hostlog.
To make this work it requires enabling updates over cellular in the
server test. Then making the payload public so it can be reached over
cellular. Then checking the update engine log for cellular entries and update
successful entries.
The client test will need to switch to cellular, start an omaha instance
and watch the update until just before reboot.
BUG=chromium:809719
BUG=chromium:809681
TEST=autoupdate_ForcedOOBEUpdate.cellular.{full|delta} passes
TEST=autoupdate_Cellular still passes
TEST=autoupdate_ForcedOOBEUpdate still passes
Change-Id: Iad1b1aadd6f437aebc8026bb3ce612466fa78fb4
Reviewed-on: https://chromium-review.googlesource.com/911605
Commit-Ready: David Haddock <dhaddock@chromium.org>
Tested-by: David Haddock <dhaddock@chromium.org>
Reviewed-by: Amin Hassani <ahassani@chromium.org>
Reviewed-by: Harpreet Grewal <harpreet@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.