| commit | a35bf3efb39eaa0120e4aac545bd191ed63d8454 | [log] [tgz] |
|---|---|---|
| author | Ed Baker <edward.baker@intel.com> | Thu Sep 27 14:45:18 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sat Dec 01 01:08:41 2018 -0800 |
| tree | 2451b7dab30703726916615fd20775883b310c57 | |
| parent | a0281e27347381fd4533d000e629a545153ffa8b [diff] |
Update video_YouTubePage tests
For all subtests, the test URL was hoisted out of video_YouTubePage
and passed as an argument from the control files. The URL was also
updated since web-release-qa.youtube.com responds with a 404. Quickly
checking The Wayback Machine seems to indicate it was last up around
July 15th 2013.
The seek time in perform_ending_test was increased since such a short
amount of time was not actually cycling from playing to ended. YouTube
seemed to transition from playing to paused, counted down for the next
autoplay, and cycled back to playing on the next video clip.
Calculating dropped frames percentages was moved into the main
injected JavaScript file and simple wrapper functions added to
the video_YouTubePage class. A fullscreen event listener was also
added to the JavaScript.
Finally, a new subtest was added to verify dropped frame percentages
while cycling fullscreen modes. To fullscreen a YouTube video this test
uses the normal 'f' hotkey. Note that this new subtest uses a Google
Earth video published by Google.
BUG=chromium:894606
TEST=All video_YouTubePage tests pass.
`test_that --board=${BOARD} ${DUT_IP} e:video_YouTubePage.*`
Change-Id: I141e06d6a9ad28c76e03f5164bccb678a0b0f356
Signed-off-by: Edward Baker <edward.baker@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/1255362
Commit-Ready: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Casey G Bowman <casey.g.bowman@intel.com>
Reviewed-by: Ilja H. Friedel <ihf@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.