commit | a082bb553c6603571a894bd9b1f92ddfae3aa1d3 | [log] [tgz] |
---|---|---|
author | Brian Norris <briannorris@chromium.org> | Fri Dec 13 14:39:49 2019 -0800 |
committer | Brian Norris <briannorris@chromium.org> | Mon Dec 16 22:43:30 2019 +0000 |
tree | ac9505f35dd8323978144191ed522d6f16c175ca | |
parent | fcc8aadd8c3d2f5ba30a1a08bc77737612173056 [diff] |
packet_capturer: avoid new (iw >= v4.14) 'set freq' syntax This CL started using the new '80MHz' option to 'iw ... set freq': https://crrev.com/c/1877829 But that's only present on new iw, since v4.14: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/commit/?id=159d5e4263403e2e10716168f672d2cd606bcfa2 We haven't upgraded our Whirlwind APs in a little while, so they don't have this yet. Use this as a stopgap measure. This procedure is somewhat ripped off what 'iw' does to compute cf1 for us. BUG=chromium:1017533, chromium:1005443 TEST=`network_WiFi_SimpleConnect.wifi_check5VHT80_mixed` (which uses 80MHz capture) on various APs (note: use a separate router+pcap, or else you won't actually hit this code path) Change-Id: I05792c3a1c5804254eeeefdd94f7b2e4727d3f79 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1967946 Tested-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Jared Pauletti <pauletti@google.com> Reviewed-by: Kirtika Ruchandani <kirtika@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.