Improve Tuner VTS: Generate DVR Record Combos
This CL allows the VTS to read a vendor's configuration file, determine if the given devices could support the DVR Record dataflow, and runs the integration tests with all valid combinations. 2 functions were added to help drive the testing logic. generateRecordCombinations() generates all valid record dataflow configurations, and the integration tests call generateRecordCombinations() to analyze whether to generate these combinations or use the data flow provided by the vendor (if there is one). Additionally, when dynamically configuring DVR_Record, a bug was exposed in the VTS that came about from recycling the function recordSingleFilterTest(). When LnbRecord was initialized with a software frontend, the VTS was looking to the record dataflow's dvr source for input. If record is not hardcoded by the vendor, the VTS would crash. To fix this error, an enum class was added as a parameter to RecordSingleFilterTest() to take into consideration which dataflow (lnbRecord or record [no Lnb]) was calling the function. New behavior is defined to take into account both cases. Also, lnbRecord will not be tested if there are no hardware frontends, as this is not very likely to be configured by vendors. Bug: b/182519645 Test: vts-tradefed run vts --module VtsHalTvTunerTargetTest. Manual tests with different input configuration files. Change-Id: I76c05ca2e33767e4bdcd2072db5144d495d623b0
Loading
Please register or sign in to comment