commit | 08e868dbd2125d6d83ca2e65754a873bd43a41a3 | [log] [tgz] |
---|---|---|
author | Matthew Wang <matthewmwang@chromium.org> | Thu Apr 19 12:04:54 2018 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Wed Apr 25 23:00:11 2018 -0700 |
tree | 2539a466de95579969f4bec5ec0b39cd8ea1b634 | |
parent | 6f1d4786165096ee3a23f551cb49497479e22267 [diff] |
Change autotest bridge interface setup and teardown Configure hostap to always bring up bridge interfaces with prefix 'hostapbr', followed by index of bridge interface (instead of a customizable name). This allows us to clean up the bridge interfaces during autotest setup and teardown. Also modify network_WiFi_RoamFT to do extra cleanup. BUG=chromium:832402 TEST=1) Ran network_WiFi_RoamFT autotests on local DUT and on one of the machines affected by crbug/832402, and ran network_WiFi_SimpleConnect.wifi_5HT20 afterward. 2) Ran network_WiFi_RoamFT autotests and hit CTRL-C after both APs were configured but before tests ran to completion, and verified that bridge interfaces hostapbr0 and hostapbr1 were still up. Ran network_WiFi_SimpleConnect tests afterward to make sure cleanup was done correctly and that tests passed. Change-Id: Ie17b7484a28a94bee5fdf8116fc25d98124cd2ae Reviewed-on: https://chromium-review.googlesource.com/1020144 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Matthew Wang <matthewmwang@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.