You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TC-ACT-3.2 specifies in the test plan pdf file that the TH has an action with id 0xA001. As "expected outcome", verify that the received ActionID containts 0xA001.
But the bridge app does not have an action with this id. Instead it has 0x1001 (4097). The Test_TC_ACT_3_2.yaml file instructs the tester to use 4097 rather than 0xA001.
This was tested on RPi Matter 1.2 Test Harness.
Bug prevalence
N/A
GitHub hash of the SDK that was being used
Whatever the Matter 1.2 TH uses
Platform
core
Platform Version(s)
No response
Anything else?
Please fix so we have consistency about the action id to use for the test. Either change the id in the pdf spec to 4097 or modify the bridge app software, yaml file and the excel test plan verification file to use 0xA001 instead.
The text was updated successfully, but these errors were encountered:
Reproduction steps
TC-ACT-3.2 specifies in the test plan pdf file that the TH has an action with id 0xA001. As "expected outcome", verify that the received ActionID containts 0xA001.
But the bridge app does not have an action with this id. Instead it has 0x1001 (4097). The Test_TC_ACT_3_2.yaml file instructs the tester to use 4097 rather than 0xA001.
This was tested on RPi Matter 1.2 Test Harness.
Bug prevalence
N/A
GitHub hash of the SDK that was being used
Whatever the Matter 1.2 TH uses
Platform
core
Platform Version(s)
No response
Anything else?
Please fix so we have consistency about the action id to use for the test. Either change the id in the pdf spec to 4097 or modify the bridge app software, yaml file and the excel test plan verification file to use 0xA001 instead.
The text was updated successfully, but these errors were encountered: