gh513 Change videodevice_term to last#514
gh513 Change videodevice_term to last#514hjourdain-ryvr wants to merge 1 commit intordkcentral:mainfrom
Conversation
For the VideoDevice tests to be successful, they need to be run after videodevice_init and before videodevice_term.
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
| UT_add_test( pSuite, "SetZoomMode", test_l3_dsVideoDevice_SetZoomMode); | ||
| UT_add_test( pSuite, "GetZoomMode", test_l3_dsVideoDevice_dsGetZoomMode); | ||
| UT_add_test( pSuite, "GetVideoCodecInfo", test_l3_dsVideoDevice_GetVideoCodecInfo); | ||
| UT_add_test( pSuite, "VideoDevice_Term", test_l3_dsVideoDevice_Term); |
There was a problem hiding this comment.
Since this is an L3 test, the order of test cases doesn’t matter because the host/Python script controls the execution sequence
|
If you run the test suites manually, you can select the test suite to run, then run all the tests in it automatically. I believe you can do the same with automated testing. |
|
The purpose of the VTS is also to provide a scope for the developer who may need to debug. The L3 tests can run in steps if required by selecting the init, any action-related api, and term in the necessary sequence. If we need to run this in automation, we also use the tests available in tests, which are already sequenced. Refer to https://github.com/rdkcentral/rdk-halif-test-device_settings/tree/main/host/tests/L3_TestCases/dsVideoDevice for the tests in sequence. |
For the VideoDevice tests to be successful, they need to be run after videodevice_init and before videodevice_term. Currently, videodevice_term is called just after videodevice_init in the test suite. Move it to the last position.