commit	4cdeb423a789e291197141520ccf7207f1135520	[log] [tgz]
author	Matt Mallett <mattmallett@chromium.org>	Thu May 10 14:21:41 2018 -0700
committer	chrome-bot <chrome-bot@chromium.org>	Mon Jun 04 17:23:29 2018 -0700
tree	ed5b5f08587399fe4fe773dabaefe47e9dd2271d
parent	ddc277e99c89057b7686a24dbe2956b40c4b19b2 [diff]

[moblab] update storage_qual suite to use dynamic_suite

Replace sequence running of storage_qual, storage_qual_quick
with dynamic suite approach. This requires all the control
files to be present in source control. Created a script
that generates all the required control files.

Created hardware_StorageQualSetup that verifies moblab has the correct setup
of DUTs and labels. This runs as a part of storage_qual, storage_qual_quick,
and can be run from moblab_setup suite.

Note that this CL is huge, but the majority of files are auto-generated.
The important files to review are
 server/site_tests/hardware_StorageQual/generate_storage_qual_control_files.py
 server/site_tests/hardware_StorageQualSetup/control.moblab_setup
 server/site_tests/hardware_StorageQualSetup/control.storage_qual
 server/site_tests/hardware_StorageQualSetup/hardware_StorageQualSetup.py
 frontend/client/src/autotest/moblab/SuiteRunnerView.java

BUG=chromium:842229
TEST=ran moblab_setup with multiple configurations to verify
hardware_StorageQualSetup, ran the full hardware_storagequal_fast

Change-Id: Ib81c55e902f0db221fe631a0f1491d8a608f7952
Reviewed-on: https://chromium-review.googlesource.com/1060242
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Matt Mallett <mattmallett@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>

246 files changed

tree: ed5b5f08587399fe4fe773dabaefe47e9dd2271d

README.md

Autotest: Automated integration testing for Android and Chrome OS Devices

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.