| commit | e6df2ce60f4c2a744cf88465388b9fa033d43bb7 | [log] [tgz] |
|---|---|---|
| author | Brian Norris <briannorris@chromium.org> | Thu Mar 01 13:34:49 2018 -0800 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Mar 02 19:52:00 2018 -0800 |
| tree | 923d6217c869b2887407fa383970ee7ff323d381 | |
| parent | 758d0695523cea67164fb00ca69f0a8f43dfc5e0 [diff] |
network_WlanDriver: add new .bvt version, with board exceptions
Some boards have Wifi which is unresolvably flaky, such that the driver
may just crash entirely and leave us with no Wifi device. We don't want
this flakiness to affect CQ results.
For now, we run this test only on bvt-perbuild (as we were doing
already), but we plan to move to bvt-cq soon.
The current exception list only contains nyan_kitty, because it's the
only lab device currently failing with unresolvable symptoms in the lab.
Occasionally, the device fails to load the mwifiex firmware correctly,
saying "FW failed to be active in time" after some long timeout. We've
debugged this issue before on some later platforms, but this requries
extensive vendor assistance, as the bug lies entirely within the
firmware.
I wouldn't be surprised if we had to add other Marvell-Wifi devices in
the future.
Also adjust the DOC wording to more accurately describe what it is
testing.
BUG=chromium:793526
TEST=`test_that ... network_WlanDriver.bvt` with $BOARD in and out of
exception list; with and without driver loaded; see WARN result for
forgiven failures, GOOD for success
Change-Id: I8107f0d3b9a9d520009407a60dbdb43cf869b0e1
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/944502
Reviewed-by: Harpreet Grewal <harpreet@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.