| commit | 1a7644e393fbb03980c495524b0aaee9afdb1d6d | [log] [tgz] |
|---|---|---|
| author | Brian Norris <briannorris@chromium.org> | Tue Jul 31 11:55:34 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Aug 02 21:50:01 2018 -0700 |
| tree | 420d86f9e0322a9aa9a5bb762f5fb487981452d9 | |
| parent | 1e1bc01176164206941956a673a740343b8e7b89 [diff] |
[autotest] network_WiFi_BgscanBackoff: straighten out router requirements
As written today, this test requires CAPABILITY_MULTI_AP_SAME_BAND but
doesn't declare it. The test starts up multiple BSS's at distinct
frequencies, which can't be served by a single radio.
For the 'wifi_bgscan_backoff' test, this isn't really required; the test
can just as well be run on separate 2G vs. 5G bands.
For the '5760noise_check' variant, we explicitly wanted to test two
5GHz channels. This isn't possible on Gale, so let's add a capability
check so this test gets a TEST_NA result.
As a related effect, this also should move the .wifi_bgscan_backoff
variant to avoid running on phy2 on Whirlwind, which can help avoid some
flakiness. Whirlwind's phy2 is not known to be a reliable transmitter,
and we may stop using it entirely soon.
BUG=chromium:774808, chromium:866181
TEST=network_WiFi_BgscanBackoff.wifi_bgscan_backoff
and network_WiFi_BgscanBackoff.5760_noise_check with gale;
the former now passes, and the latter gets TEST_NA
Change-Id: I9f6d7ea0dba86d84aaa8cbc8ca236baf8fbdf92b
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1159462
Reviewed-by: Grant Grundler <grundler@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.