|author||Wu-Cheng Li <email@example.com>||Tue Mar 28 14:16:37 2017 +0800|
|committer||chrome-bot <firstname.lastname@example.org>||Thu Mar 30 07:29:41 2017 -0700|
Add video_VDASanity. video_VDASanity runs video_decode_accelerartor_unittest with a list of short videos for sanity testing. The test fails if the kernel crashes or VDA unittest crashes. It is OK for VDA unittest to fail. This autotest should run very fast. To ensure that, rendering of VDA unittest is off and the test videos should be as short as possible. Here's how VP9 videos were generated. bear-1280x720.mp4 is from in chrome_src/media/test/data. avconv -i bear-1280x720.mp4 -s 320x180 -c:v rawvideo -pix_fmt yuv422p \ -frames 30 bear_422.yuv avconv -i bear-1280x720.mp4 -s 320x180 -c:v rawvideo -pix_fmt yuv420p \ -frames 30 bear_420.yuv COMMON=" --codec=vp9 -w 320 -h 180 --ivf --kf-min-dist=0 --kf-max-dist=150 --lag-in-frames=24 --drop-frame=0 --target-bitrate=140 --cq-level=23 --min-q=4 --max-q=56 --static-thresh=1000 --arnr-maxframes=7 --arnr-strength=5 --arnr-type=3 --cpu-used=1 --good --tile-columns=1 --passes=2 --threads=1 --end-usage=cq --auto-alt-ref=1 --bias-pct=50 --minsection-pct=0 --maxsection-pct=2000 --undershoot-pct=100" ./vpxenc bear_422.yuv -o bear_profile1.vp9 --profile=1 --i422 $COMMON ./vpxenc bear_420.yuv -o bear_profile2.vp9 --profile=2 --i420 \ --bit-depth=10 $COMMON ./vpxenc bear_422.yuv -o bear_profile3.vp9 --profile=3 --i422 \ --bit-depth=10 $COMMON BUG=b:35936915 TEST=Run video_VDASanity on elm. CQ-DEPEND=CL:461737 Change-Id: I622a2ed70354db6c811baad95e86f8bf35fe8fc7 Reviewed-on: https://chromium-review.googlesource.com/461760 Commit-Ready: Wu-cheng Li <email@example.com> Tested-by: Wu-cheng Li <firstname.lastname@example.org> Reviewed-by: Wu-cheng Li <email@example.com>
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
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.