platform_hardware_interfaces/media/omx/1.0/vts/functional
Ram Mohan M 4e39ff9235 Increase Timeout for dequeue message
In vp9 encoder component, the callback responses are being recevied
after timeout. This is seen only in vp9. Even when no buffer processing
is done, Flush test, state transitions test fail due to slow responses.
This behavior is not seen in other components. This requires deeper
understanding of what is main culprit. But for now increase the timeout

Test: VtsHalMediaOmxV1_0Host
Bug: 37501531
Change-Id: I08abfefcf0cb38d312a4a2dc10908e24f88c54fd
2017-06-09 20:08:13 -07:00
..
audio Merge "AudioDec Test: Ignore output port configuration" into oc-dev 2017-06-09 03:12:08 +00:00
common Increase Timeout for dequeue message 2017-06-09 20:08:13 -07:00
component Vts Omx Tests: Disable test that are not IOMX compatible 2017-06-07 17:53:26 -07:00
master Omx vts tests 2017-06-07 17:50:50 -07:00
video Merge "bug fix: fix encoder input port configuration issues" into oc-dev 2017-06-10 01:23:30 +00:00
README.md Omx vts tests. 2017-05-31 12:53:37 -07:00

Omx Hal @ 1.0 tests


Overview :

The scope of the tests presented here is not restricted solely to testing omx hal @ 1.0 API but also test to omx core functionality and to an extent omx components as well. The current directory contains the following folders: audio, common, component, master and video. Besides common all other folders contain test fixtures for testing AV decoder, encoder components. Common constitutes files that are used across by these test applications.

master :

Functionality of master is to enumerate all the omx components (and the roles it supports) available in android media framework.

usage: VtsHalMediaOmxV1_0TargetMasterTest -I default

component :

This folder includes test fixtures that tests aspects common to all omx compatible components. For instance, port enabling/disabling, enumerating port formats, state transitions, flush, ..., stay common to all components irrespective of the service they offer. Test fixtures here are directed towards testing these (omx core). Every standard OMX compatible component is expected to pass these tests.

usage: VtsHalMediaOmxV1_0TargetComponentTest -I default -C -R

audio :

This folder includes test fixtures associated with testing audio encoder and decoder components such as simple encoding of a raw clip or decoding of an elementary stream, end of stream test, timestamp deviations test, flush test and so on. These tests are aimed towards testing the plugin that connects the component to the omx core.

usage:

VtsHalMediaOmxV1_0TargetAudioDecTest -I default -C -R audio_decoder. -P /sdcard/media/

VtsHalMediaOmxV1_0TargetAudioEncTest -I default -C -R audio_encoder. -P /sdcard/media/

video :

This folder includes test fixtures associated with testing video encoder and decoder components such as simple encoding of a raw clip or decoding of an elementary stream, end of stream test, timestamp deviations test, flush test and so on. These tests are aimed towards testing the plugin that connects the component to the omx core.

usage:

VtsHalMediaOmxV1_0TargetVideoDecTest -I default -C -R video_decoder. -P /sdcard/media/

VtsHalMediaOmxV1_0TargetVideoEncTest -I default -C -R video_encoder. -P /sdcard/media/

While tesing audio/video encoder, decoder components, test fixtures require input files. These input are files are present in the folder 'res'. Before running the tests all the files in 'res' have to be placed in '/media/sdcard/' or a path of your choice and this path needs to be provided as an argument to the test application