| commit | 833f6bb3a6da76fcddbd9b8dee970c63a2daa9d0 | [log] [tgz] |
|---|---|---|
| author | Alex Khouderchah <akhouderchah@chromium.org> | Thu Sep 13 10:36:20 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Mar 15 16:48:43 2019 -0700 |
| tree | bda2dae96ff8255b95925538178a9f0891cba72e | |
| parent | 6be187fe0b3537e0a1f96cf499b059a651694dee [diff] |
autotest: wifi: Update get_disconnect_reasons to match new shill logging
WifiClient.get_disconnect_reasons greps for certain strings within
/var/log/net.log. CL:1487574, however, modifies how shill logs certain
messages such that this functionality would no longer work (i.e. logs
may either say 'supplicant updated DisconnectReason to %d' or
'supplicant updated DisconnectReason from %d to %d', depending on
whether or not the disconnect reason was already set at that time).
For example, both of the following could be logged by shill:
* "supplicant updated DisconnectReason to 10"
* "supplicant updated DisconnectReason from 10 to 0"
But only the first one would be considered a disconnect by
get_disconnect_reasons prior to this change.
Note that this is not a long-term solution, which should involve a more
robust means of getting the disconnect reason from shill. This is only
here so that CL:1487574 will not break the existing get_disconnect_reasons
functionality.
CQ-DEPEND=CL:1487574
BUG=chromium:625387
TEST=Manual call to get_disconnect_reasons on machine with updated shill
as per CL:1487574.
Change-Id: Ic58eca4bbfdaf6135b01c45998408ef26928e54a
Reviewed-on: https://chromium-review.googlesource.com/1226151
Commit-Ready: Alex Khouderchah <akhouderchah@chromium.org>
Tested-by: Alex Khouderchah <akhouderchah@chromium.org>
Reviewed-by: Kirtika Ruchandani <kirtika@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.