Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
RDKB-51761 : Test Suite Enhancements (#181)
* RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh OR verify with unit_test.yml Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]> RDKB-51761 : Test Suite Enhancements (#175) * RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]> * RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]> * RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]> * RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]> * Update unit_tests.yml RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: added unit tests verified on GitHub yml Test Procedure: very unit_tests.yml success Risks: Medium Priority: P1 --------- Signed-off-by: Deepak_m <[email protected]> RDKB-51761 : Test Suite Enhancements (#179) * RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh OR verify with unit_test.yml Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]> RDKB-51761 : Test Suite Enhancements (#184) * RDKB-51761 Test scenario to cover multiple rbus_open() call Reason for change: Need to cover test app and unit test to have a test cases which covers multiple rbus_open() with same component name without rbus_close() call. The test scenario should also cover regDataElements, rbus_set, rbus_get, addrow and methodinvoke after doing multiple rbus_open() function call Test Procedure: Start rtrouted and ./rbus_test.sh OR verify with unit_test.yml Risks: Medium Priority: P1 RDKB-52662 Update the multi rbusopen Tests (#188) Reason for change: Fix for multiRbusOpenRbusGetProvider crash on device Test Procedure: Start rtrouted and ./rbus_test.sh OR verify with unit_test.yml Risks: Medium Priority: P1 Signed-off-by: Deepak_m <[email protected]>
- Loading branch information