| commit | 2337061e7383480c84c4b864044d7f68373cf44a | [log] [tgz] |
|---|---|---|
| author | harpreet <harpreet@google.com> | Fri Nov 16 17:22:19 2018 -0800 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Nov 29 16:09:02 2018 -0800 |
| tree | 13b77430b9535f9762fec52d56f5a473f8e94298 | |
| parent | 4c99e31da15a2742abf14cb21ce1c0cbcbd6e3e2 [diff] |
[wifi interop lab] Get interop lab up and going Wifi interop lab will allow for testing ChromeOS DUTs against 50+ commercially sold APs across different channels/frequencies. All the APs are statically configured and this configuration is reflected in chaos_ap_list.conf. Due to the time it takes to test a given DUT against all APs (~3hrs) and the fact that we can only run the test on 1 DUT at a time (due to current design limitations), the plan is to split the test runs across different days such that the test(s) will be run on each DUT once per week. Old design docs: https://docs.google.com/document/d/1tnp0JbL6Z9kxNsrBKeh2ZoTFxiH2WzFK49LsGZRGLd0/edit# https://docs.google.com/document/d/1BxwqwTZ7c84nXyiJPpyzSX1hDvZTch4kWtPpIBluNa4/edit AP configurations: https://go/chaos-ap-configs DUT setups: http://go/wifi-device-life-cycle-chaos Test run flow chart: https://go/chaos-test-run-flow-chart We also plan to continue adding newer APs to the interop lab as needed. BUG=chromium:906277 TEST=Tested using kevin against all APs in chaos lab; unit tests (e.g., `utils/unittest_suite.py -r server/cros/ap_configurators/`) Change-Id: Ief141529fc0df264dac804e771aaba82fbcb5d65 Reviewed-on: https://chromium-review.googlesource.com/1341180 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Dinesh Kumar Sunkara <dsunkara@google.com> 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.