| commit | 37baf743f3a0efb404e04fd86b96125aba2c4112 | [log] [tgz] |
|---|---|---|
| author | Kirtika Ruchandani <kirtika@google.com> | Wed Apr 10 14:03:26 2019 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Apr 12 05:53:48 2019 -0700 |
| tree | 0f165c1f788016ddfd1ea9c43d5e0ebd9e1bb3d3 | |
| parent | 06475c585fdf5dd0884dfa3df293027bc235e262 [diff] |
network_WiFi_BT_AntennaCoex: Use ch11, not ch13 2472 MHz aka channel 13 is forbidden in the US. This test tries to connect there in the very last sub-test. That will fail because we never even scan on that channel. Change it to channel 11. Note that the failure only happens on DUTs which have a US regdom, as the world regdom (country code:00) will allow scanning on ch13. You can notice this as the test failure is: Expected connection to BT_AntennaCoex_d_gw1o2_ch13 to succeed, but it failed with reason: FAIL(Discovery timed out). And the wpa_debug shows the scan list never included 2472: 2019-04-05T09:38:53.707821+00:00 DEBUG wpa_supplicant[733]: nl80211: Scan \ included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 \ 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600\ 5620 5640 5660 5680 5700 5720 5745 5765 5785 5805 5825 BUG=chromium:876920 TEST=Lock chromeos15-row2-rack2-host1 that was failing this test in the lab, run test with this change and watch it pass. Change-Id: I1966d25146952f7278a81d79fd9c6db28cd8bf0a Signed-off-by: Kirtika Ruchandani <kirtika@google.com> Reviewed-on: https://chromium-review.googlesource.com/1562531 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Kirtika Ruchandani <kirtika@chromium.org> Reviewed-by: Kirtika Ruchandani <kirtika@chromium.org> Reviewed-by: Brian Norris <briannorris@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.