RDKB-51761 : Test Suite Enhancements #184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 scenario to cover multiple rbus_open() call Reason for change: Update unit_tests.yml after fixing multiRbusOpenMethodConsumer crash
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]>
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]>
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]>
karuna2git
pushed a commit
that referenced
this pull request
Dec 26, 2023
* 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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RDKB-51761 Test scenario to cover multiple rbus_open() call
Reason for change: modifying unit_tests.yml to fix unit test failure of multiRbusOpenMethodConsumer
Test Procedure: verify .github/workflows/unit_tests.yml
Risks: Medium
Priority: P1