commit | 860ad5164a6e1e11f4ec99a1c05ae7e021384d00 | [log] [tgz] |
---|---|---|
author | Brian Norris <briannorris@chromium.org> | Fri Apr 13 16:02:35 2018 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Apr 17 15:53:11 2018 -0700 |
tree | 3c63bdf1ffd0fa7222da9a95a2143b5cc818af71 | |
parent | 711ede943a5939faa609cb621b6e5915ccdd568d [diff] |
network_WiFi_Perf: log VHT80 correctly in keyval results Wifi perf results generate keys by using the hostap config's printable_mode() method. This method didn't handle VHT80 correctly and instead interpreted it as 11A. Add special handling for VHT. I don't currently plumb the corresponding packet_capturer parameters, because (a) our current 'iw' doesn't have a clear way of configuring this (or at least, I was too lazy for this at the moment) and (b) we should probably plumb packet capture modes (i.e., 'iw dev XXX set freq ...') differently than "printable mode" anyway. Note that this means we probably aren't capturing network_WiFi_SimpleConnect.wifi_check5VHT80 correctly. Fortunately, that's the only other test that uses VHT rates, and it doesn't actually utilize those captures for anything. BUG=chromium:827829, chromium:774831 TEST=network_WiFi_Perf.vht80 (and others); check that the results/keyval file contains results like: ch044_modeVHT80_none_PSon_tcp_tx_throughput{perf}=191.98+-0.56 instead of: ch044_mode11A_none_PSon_tcp_tx_throughput{perf}=193.73+-5.60 Change-Id: I038eeeb1a54998324458ffe9609b6ea06d4766f2 Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1013261
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.