| commit | 19e0ab3547756bbced5ef7e1b7abb645bc831720 | [log] [tgz] |
|---|---|---|
| author | Alex Khouderchah <akhouderchah@chromium.org> | Fri Jul 06 17:03:21 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sat Jul 14 18:11:39 2018 -0700 |
| tree | d564e1a3e882e7c74f29d12a3a852084f09ddf4d | |
| parent | c916e4e6c8423353cb5bc9494e84b3cd52d845fa [diff] |
autotest: Allow setting CPU governor from server tests
The autotest_lib.client.bin.utils package provides various functions
for setting and restoring the CPU governor of a client system. This
change modifies these functions to allow a custom host to be
specified. The default behavior of these functions remains unchanged.
BUG=chromium:860844
TEST=Ran video_PlaybackPerf.vp8 test to ensure that a regular call to
ensure that a regular call to set_high_performance_mode would
still work.
TEST=Made calls to set_high_performance_mode and
restore_scaling_governor_states from video_HangoutHardwarePerf test
to ensure that calls to those functions will still work without
change, despite the move from bin.utils to common_lib.utils.
TEST=Manually tested with modified server test to ensure that the
functions work when specifying a remote host.
Change-Id: I4d1bc263d36f848aa8d3f7f46ecf6fab912d0f1f
Reviewed-on: https://chromium-review.googlesource.com/1128445
Commit-Ready: Alex Khouderchah <akhouderchah@chromium.org>
Tested-by: Alex Khouderchah <akhouderchah@chromium.org>
Reviewed-by: Kirtika Ruchandani <kirtika@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.