| commit | bfe724449bd2bb0e76b8667bd1c2f121b6af1c5f | [log] [tgz] |
|---|---|---|
| author | Mengqi Guo <mqg@chromium.org> | Thu Oct 12 16:37:54 2017 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Oct 30 23:21:31 2017 -0700 |
| tree | 8dada304a0989004e0ba55f847d960e60c87799c | |
| parent | 9b8e7ad6f8f112562eb97e1188df5b58c46f28a4 [diff] |
power_UiResume: Measure ARC suspend to resume time
Our goal is to better simulate user environment for power_Resume
by logging into Chrome and open ARC (where available). However,
to make sure that we cover all 3 types of devices: with ARC, with
Chrome but not ARC, without Chrome, we split our work into 2 parts.
In power_Resume, we measure power numbers. This will run on all
devices. In power_UiResume, we log into Chrome and open ARC where
available, and then call power_Resume to measure power numbers.
This part will only run on devices with Chrome/ARC. In both cases,
power_Resume calls power_suspend.py, which has the option to
measure ARC suspend to resume time.
We realize that on devices with Chrome/ARC, power_Resume will
basically run twice. However, with the limitations of ebuild, this
is our optimal solution right now.
We are recycling power_UiResume because it hasn't run for a long
time in the lab and its old content was basically duplicating
power_Resume.
BUG=chromium:748191
TEST=test_that power_Resume on minnie and link
test_that power_UiResume on minnie and link
cros_workon_make autotest-chrome on minnie and link
cros_workon_make autotest-chrome on veyron_rialto fail as expected
cros_workon_make autotest-tests-power on minnie, link and
veyron_rialto
Change-Id: I1cb8ff23f9f26a15c1f90c0f40d98a9438fe45d0
Reviewed-on: https://chromium-review.googlesource.com/726743
Commit-Ready: Mengqi Guo <mqg@chromium.org>
Tested-by: Mengqi Guo <mqg@chromium.org>
Reviewed-by: Todd Broch <tbroch@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.