| commit | 1e1bc01176164206941956a673a740343b8e7b89 | [log] [tgz] |
|---|---|---|
| author | Brian Norris <briannorris@chromium.org> | Mon Jul 30 13:30:31 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Aug 02 21:50:00 2018 -0700 |
| tree | 0bda0697c21b26f90e670ec6bf6158664f9d360d | |
| parent | c2aecb979e815583339494ec318c3c9817fbf13b [diff] |
[autotest] network_WiFi_MaskedBSSID: stop requiring MULTI_AP_SAME_BAND This test has some strange requirements: it wants to set up an illegal configuration, with 2 BSS's using the same BSSID, to imitate some broken routers in the field. The Linux mac80211 framework doesn't accept this, returning -ENOTUNIQ instead, so this doesn't work when you run both of these BSS's on the same radio. This all worked OK on APs that had more than 1 radio for each band (so you work around Linux's per-interface BSSID restriction), but it doesn't work on Gale, where we force the 2 BSS's onto the same radio. We can work around this by just switching this test to put the two incompatible BSS's on separate bands (2.4GHz / 5GHz), and then drop the CAPABILITY_MULTI_AP_SAME_BAND requirement. This should also fix some issues seen on some Whirlwind routers, where the 3rd radio (phy2) wasn't operating reliably. We may try to avoid using this radio entirely in the future, so this is a good start. BUG=chromium:774808, chromium:866181 TEST=network_WiFi_MaskedBSSID.wifi_masked_bssid on Gale Change-Id: Idab9c56f42ad426a0f6b323e49539699679cd2d4 Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1159461 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.