For instance, to only run the TestDecodeTimeMedian test, one can specify -gtest_filter="*TestDecodeTimeMedian*". The -gtest_filter option can be used to specify a pattern of test names to run. The list of available tests can be retrieved using the -gtest_list_tests option.īy default, all tests are run, which can be a bit too much, especially when bringing up a new codec. video_decode_accelerator_unittest -help will list all valid options. So in order to run all h264 tests, one would invoke. The correct value of test_video for each test file follows: Where test_video is of the form filename:width:height:numframes:numfragments:minFPSwithRender:minFPSnoRender:profile video_decode_accelerator_unittest -disable_rendering -single-process-tests -test_video_data=test_video Running the VDAtest can be done as follows.
md5 counterpart, which contains the md5 checksums of valid thumbnails. The media/test/data folder in Chromium's source tree contains files with encoded video data ( test-25fps.h264, test-25fps.vp8 and test-25fps.vp9). It should work across all ARM targets.įor unlisted Intel boards, any other Intel target (preferably with the same chipset) should be usable with libva. If you are building for an ARM board that is not yet supported by the simplechrome workflow, use arm-generic as the board. The unittests can be built by specifying the video_decode_accelerator_unittest and video_encode_accelerator_unittest targets to ninja. Similarly, a /dev/video-enc0 symbolic link should point to the encoder device node. The required kernel drivers should be loaded, and there should exist a /dev/video-dec0 symbolic link pointing to the decoder device node (e.g.
This document is a walk though the prerequisites for running these programs, as well as their most common options. Running these tests manually can be very useful when bringing up a new codec, or in order to make sure that new code does not break hardware decoding and/or encoding. They includes a variety of tests to validate the decoding and encoding stacks with h264, vp8 and vp9. VDAtest (or video_decode_accelerator_unittest) and VEAtest (or video_encode_accelerator_unittest) are unit tests that embeds the Chrome video decoding/encoding stack without requiring the whole browser, meaning they can work in a headless environment. Using the Video Decode/Encode Accelerator Unittests Manually
0 kommentar(er)
