| commit | a67cc7e8150fb5ea4b3f7e4fcc811c14d3753469 | [log] [tgz] |
|---|---|---|
| author | Wai-Hong Tam <waihong@google.com> | Tue Sep 26 15:19:34 2017 -0700 |
| committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | Fri Sep 29 18:09:04 2017 +0000 |
| tree | 31756440dd20dab7a013fda6d77897e65296e349 | |
| parent | 4a7cb8f0131ca0ead8c87e84b35782fd726ff010 [diff] |
multimedia: Introduce a way to save and show the log messages from the client
Server tests use the multimedia facade framework to call the client
library, such that the existing client library can be reused in server
tests. The implementation is done by RPC. The Autotest logging system
is unable to know the log output from the client. It is hard for debug.
This change introduces a way to save the log by running a tail command
in background. The stdout and stderr are piped to the Autotest logging
system. On every RPC call, the log is processed, meaning showed to
the Autotest log.
BUG=chromium:766631
TEST=Ran a multimedia test cases, with --debug, saw the log, like:
16:54:36 INFO | autoserv| Waiting for calibration image to stabilize...
16:54:47 INFO | autoserv| [client] 14:54:46 INFO | Dispatching method
<bound method DisplayFacadeNative.func_retry of
<autotest_lib.client.cros.multimedia.display_facade_native.DisplayFacadeNative
object at 0x7f5cb558c2d0>> with args ()
16:54:47 INFO | autoserv| [client] 14:54:46 DEBUG| Running 'modetest -c'
16:54:47 INFO | autoserv| [client] 14:54:46 DEBUG| Running 'modetest -p'
16:54:47 INFO | autoserv| [client] 127.0.0.1 - - [26/Sep/2017 14:54:46]
"POST /RPC2 HTTP/1.1" 200 -
16:54:47 INFO | autoserv| RPC 'display.get_external_resolution'((), {})
returns [1920, 1080].
16:54:47 INFO | autoserv| Checking the resolutions of Chameleon and
CrOS...
16:54:47 INFO | autoserv| Resolutions across CrOS and Chameleon match:
1920x1080
16:54:47 INFO | autoserv| Capturing the screen on Chameleon...
16:54:52 INFO | autoserv| Capturing the external screen on CrOS...
Also tested the cases, like DUT reboot, RPC error.
Change-Id: I870052d82cc489acd71b90dc009e470005a0d4ce
Reviewed-on: https://chromium-review.googlesource.com/685310
Commit-Ready: Wai-Hong Tam <waihong@google.com>
Tested-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Cheng-Yi Chiang <cychiang@chromium.org>
Reviewed-by: Armando Miraglia <armax@chromium.org>
Reviewed-by: Harpreet Grewal <harpreet@chromium.org>
Reviewed-by: Denis Tosic <dtosic@chromium.org>
(cherry picked from commit 610b49cad27e9904bbc7f2665b7f6e2f4ed6447b)
Reviewed-on: https://chromium-review.googlesource.com/692998
Commit-Queue: Harpreet Grewal <harpreet@chromium.org>
Tested-by: Harpreet Grewal <harpreet@chromium.org>
Trybot-Ready: Harpreet Grewal <harpreet@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.