commit | a5894f3a5165496f43e59214a8040c2601619d40 | [log] [tgz] |
---|---|---|
author | Vinayak Suley <vsuley@chromium.org> | Thu Jun 01 11:36:31 2017 -0700 |
committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | Wed Jun 14 00:44:45 2017 +0000 |
tree | 8f5102312170e8594ac052e10df4af8eac5dc9cd | |
parent | ce7a63119627a1b2c95b797104ca563b2fd6fc42 [diff] |
Assigning video_MultiplePlayback to perbuild suite. The experimental suite has been retired. Moving this test to run in bvt-perbuild since we want it to run but not block the build. BUG=729098 TEST=None Change-Id: I98ac68708285493a48973ba2c86c8a03dbdd3f08 Reviewed-on: https://chromium-review.googlesource.com/521783 Commit-Ready: Vinayak Suley <vsuley@chromium.org> Tested-by: Vinayak Suley <vsuley@chromium.org> Reviewed-by: Rohit Makasana <rohitbm@chromium.org> (cherry picked from commit 34ae222c3d184602d4e4794a4e6a4bac91768a64) Reviewed-on: https://chromium-review.googlesource.com/531648 Reviewed-by: Vinayak Suley <vsuley@chromium.org> Commit-Queue: Vinayak Suley <vsuley@chromium.org> Trybot-Ready: Vinayak Suley <vsuley@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.