| commit | f0bce71897e860dd33f5e7b607a20cd2f04c2eb6 | [log] [tgz] |
|---|---|---|
| author | Amin Hassani <ahassani@chromium.org> | Mon Feb 10 16:14:35 2020 -0800 |
| committer | Commit Bot <commit-bot@chromium.org> | Sat Feb 15 02:59:57 2020 +0000 |
| tree | b40e428badc22c81ec7f7181ffda9db66001c0d9 | |
| parent | 8e84a3b1001c5c21cbd4f89663b4c849a24334be [diff] |
Move enterpise AU tests to Nebraska nano_omaha_devserver.py is being deprecated (as mattar of fact in this very CL). So we need to move all the AU enterprise codes to nebraska.py (through nebraska_wrapper.py). In this process we deprecated enterprise_au_context.py which was doing weird stuff and pushed some stuff it does to update_engine_util.UpdateEngineUtil. Then the tests that used the enterpise_au_context.py can inherit from UpdateEngineUtil instead and use nebraska_wrapper to do the same things much easier. BUG=chromium:999047 TEST=test_that 100.90.30.183 policy_AUServer.TargetVersion.full_prefix --args="running_at_desk=True job_repo_url=http://100.115.245.200:8082/static/reef-release/R81-12860.0.0/autotest/packages" --no-retry TEST=test_that 100.90.30.183 policy_AUServer.AUDisabled.true --args="running_at_desk=True job_repo_url=http://100.115.245.200:8082/static/reef-release/R81-12860.0.0/autotest/packages" --no-retry The 'AUDisabled.true' test fails with some problem with dm_server which could be caused by my setup. But it passes the update part which is what we're changing here. Change-Id: I415022f7c681178b42f8887db970df63aa38f3c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2048896 Tested-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Derek Beckett <dbeckett@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.