commit | 1e8571e216ed3f8fb7154109bb29e85adbafa48b | [log] [tgz] |
---|---|---|
author | Brian Norris <briannorris@chromium.org> | Thu Mar 28 11:21:19 2019 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Mon Jul 15 18:22:23 2019 -0700 |
tree | 188e327ff48223bdb214483e7e71988952c91e57 | |
parent | 8466f00364d278ed087e61cd875138a447214f20 [diff] |
network_WlanRegulatory: refresh for the modern world This test has a few problems: (1) CRDA is going away someday, to be replaced by /lib/firmware/regulatory.db. This isn't immediately a problem, since we can install both databases, even as we transition to the latter, and we're only really looking at it directly to enumerate the available domains. But we should note that deficiency, and adapt the descriptions of this test so it's not as misleading. (2) Some drivers are "self-managing" their domain detection, which often means they won't respect a setting from user space. We should avoid requiring this test on such systems. (3) This test appears to promise more than it really can do. For one, it does not verify that the applied rules actually do anything. Document that a little better. (4) It's not part of any suite, so no one ever runs it. Add it to wifi_matfunc. (5) It doesn't re-set the domain in the event of a failure. Move that step to a cleanup function, so it runs even if we hit a failure. BUG=chromium:707306 TEST=run it on a variety of devices (Intel, QCA, Marvell) and kernels Change-Id: Ife6235549b3dcde9e468c8ef93d643b5df48a4c4 Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1544901 Legacy-Commit-Queue: Commit Bot <commit-bot@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.