| commit | 7f999c572196aba7d6803cde7f327996c417e22d | [log] [tgz] |
|---|---|---|
| author | Harry Pan <harry.pan@intel.com> | Thu Mar 28 22:27:08 2019 +0800 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Apr 19 14:45:35 2019 -0700 |
| tree | 903f8a45bff52a8615d760d0d073d5d98b5ea8f2 | |
| parent | bcca5fb828c0d4592a520d9c0d1ce961293ed14a [diff] |
sys_power: refactor wakealarm usage for suspend tests In terms of suspend stress tests, pre-programing wakealarm before issuing a suspend request could be flaky because of: - Test has no sense how the power manager daemon implements - Power manager has no idea the wakealarm has been programmed when it receives a suspend request The detail conflict is listed at chromium:941846 for native test client and script. In order to tackle this odd, we can pass wakealarm programming to power manager daemon, let the daemon knows this option, once suspender is ready to suspend, pass this option to the setuid helper script, such that, it would have some benifits: - Suspend time parameter is more approaching to the time machine stays in the low power mode rather than a budget time - For lab testing, we don't need to increase this parameter to align to the worse case for software ready-to-suspend in each iteration, this saves the total time for test iterations BUG=chromium:941846 TEST=run 'test_that --board=$BOARD $IP f:.*power_SuspendStress/control.bare', examine the log to justify the test pass wakealarm to powerd Change-Id: Ibe952e9986f5672f5da4d016aa77d84128790b7b Signed-off-by: Harry Pan <harry.pan@intel.com> Reviewed-on: https://chromium-review.googlesource.com/1549807 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Reviewed-by: Dan Erat <derat@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.