commit | e4139c8388715fe49c8f65b90dfab9208a431905 | [log] [tgz] |
---|---|---|
author | Mary Ruthven <mruthven@google.com> | Mon Nov 12 18:07:58 2018 -0800 |
committer | chrome-bot <chrome-bot@chromium.org> | Mon Nov 19 19:14:00 2018 -0800 |
tree | 9f446c5a2d681901a68bae6ca0583901b7371bb1 | |
parent | 2637cd45e8c6d2b49de44585813c80becb661997 [diff] |
autotest: add test to stress servo consoles We have had a lot of servo issues that can be reproduced by running console commands or servo controls a bunch. This adds a test to run the same control or console command many times to catch errors. It adds control files to stress the main controls/consoles used by autotest. The cr50 and ec controls send commands that produce a lot of output, so issues can be caught more quickly. servo micro and servo v4 don't have the necessary controls to create autotest console objects, so the test just uses the servo_micro_version and servo_v4_version controls for testing. BUG=none BRANCH=none TEST=run these tests on servo micro with servo v4. The cr50 console test shows that the console drops characters. servo_micro console gets wedged after a while. Change-Id: Iddd89db739a0a8e9c6e8794a4a704299dd94522a Signed-off-by: Mary Ruthven <mruthven@google.com> Reviewed-on: https://chromium-review.googlesource.com/1332672 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Mary Ruthven <mruthven@chromium.org> Reviewed-by: Nick Sanders <nsanders@google.com>
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.