commit | f98b8bdba015f83d32a13b113e73162a97c774cc | [log] [tgz] |
---|---|---|
author | Hirokazu Honda <hiroh@chromium.org> | Wed May 30 15:19:07 2018 +0900 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Jun 05 05:42:18 2018 -0700 |
tree | 39d9d2cc915a9f98f4845d56a14122b5c58c409e | |
parent | 60cc4b4d21caca5a8bae923923117683fccde804 [diff] |
video_PlaybackPerf: Remove 4k_video DEPENDCIES video_PlaybackPerf measures end-to-end Chrome video playback performance with both software and hardware decoder. Hardware decoder has device capability (i.e. some devices do not support 4K video hardware decode). However, for software decoder, it has no such limitation. Hence, all devices can play 4K video regardless performance. Currently, the test skips 4K video test if the device does not support hardware decoding for 4k video. However, it should still measure software decoder performance so that we can monitor decoders' performance and see if Chrome video stack changes improve or degrade performance. The cost of this change is the increment of test running time. And this shall be the cost worth to spend. By enabling us to monitor playback performance results, we can understand playback peroformance on Chrome OS device as of today, and improve Chrome video stack if chance. BUG=chromium:789866 TEST=4k video_PlaybackPerf on minnie and eve Change-Id: I829371d8caf13b54125a7652c099ef2f1b5b0dcf Reviewed-on: https://chromium-review.googlesource.com/1077872 Commit-Ready: Hirokazu Honda <hiroh@chromium.org> Tested-by: Hirokazu Honda <hiroh@chromium.org> Reviewed-by: Pin-chih Lin <johnylin@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.