Add TBRM_2_5 and TBRM_2_6 test cases #38013
Open
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
… tbrm_dev_type_2nd_if_tc
… tbrm_dev_type_2nd_if_tc
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.
Add new TC_TBRM_2_5 and TC_TBRM_2_6 test cases for devices that support SNI.
Test scenario PR: https://github.com/CHIP-Specifications/chip-test-plans/pull/4600
Test cases cannot be executed over CI as they require for the DUT to connect to a Thread network in order to do the validation required. In order to validate that the Secondary Network Interface device type works properly raw TLV values must be extracted from Thread dataset to compare what the DUT receive as parameter and what it actually save in Network Commissioning cluster.
Testing
Test was done on NXP FRDM-RW612 platform using the Thermostat application with Matter over Wi-Fi and OpenThread Border Router
TBRM Logs.zip