Suraj Seenivasan
Suraj Seenivasan
## Problem Steps 2 - 7: remove th_xpan network, add THREAD_2ND_OPERATIONALDATASET, Connect to THREAD_2ND_OPERATIONALDATASET After Step 7 : `./chip-tool networkcommissioning connect-network hex:1161111128222222 1 0 --Breadcrumb 2` not able to proceed...
### Reproduction steps 1. Use V1.0 commit as chip-tool 2. Either Master or V1.0 commit as DUT 3. After test Step 6a : `Set up subscription to InitialPress, ShortRelease, MultiPressOngoing,...
### Feature Area Other ### Test Case TC-CNET-1.3 ### Reproduction steps 1. Bring up the DUT with all-clusters-app. 2. Pair the DUT using chip-tool through "ble-wifi" transport. 3. Run the...
### Feature Area Other ### Test Case TC-CNET-4.11 ### Summary TH should be able to connect DUT using 1st ACCESSPOINT with connected status as TRUE when the fail-safe is disarmed...
## Description **XML has to be updated as per spec:** In MeasurementRangeStruct, the Constraint has to be added for below mentioned fields. - EndTimestamp - MaxTimestamp - EndSystime - MaxSystime
### Feature description Currently, there is no discernible advantage in segregating Python test cases into two different suites. The test cases can be effectively organized and managed within a single...
### Describe the bug Test cases in the "Python Testing Suite - Legacy" fail when executed alongside test cases from both the "Python Testing Suite" and "Python Testing Suite -...
### Feature description Executing Python test cases through the UI takes longer; for instance, completing a test case with three steps via UI requires approximately 3 minutes. This duration exceeds...
### Feature description UI should not prompt for DUT commissioning when more than one Python test case is executed concurrently.  ### Use Cases During the execution of multiple Python...
### Feature description Currently, when multiple automation tests are executed simultaneously, the logs are consolidated into a single file upon completion. However, for enhanced traceability and debugging purposes, it would...