-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix TC-SC-5.1 Step 9b Failure for Devices Without Groups Cluster Support #38171
base: master
Are you sure you want to change the base?
Fix TC-SC-5.1 Step 9b Failure for Devices Without Groups Cluster Support #38171
Conversation
PR #38171: Size comparison from 97ffa50 to d045200 Full report (75 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Now, the fabricIndex is read dynamically instead of being hardcoded, so there won't be any issues if a new fabric value is used—the test will handle it automatically. |
PR #38171: Size comparison from 97ffa50 to af41aed Increases above 0.2%:
Full report (75 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
FabricIndex: 1, | ||
FabricIndex: CurrentFabricIndexValue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change? Value is ignored on write anyway. If this should be changed at all, should be changed to 0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. I’ve left it at 0 on writesAttribute. Thanks for the clarification!
value: | ||
[ | ||
{ | ||
FabricIndex: CurrentFabricIndexValue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, this value is ignored on write. Should be 0 or something, or no changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. I’ve set this to 0 on this one as well. Thanks for the review!
value: | ||
[ | ||
{ | ||
FabricIndex: CurrentFabricIndexValue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, it's important to keep CurrentFabricIndexValue instead of 0 since this comes from readAttribute, not writeAttribute. Otherwise, if the fabric changes for some reason, this test step could fail.
@@ -319,7 +340,7 @@ tests: | |||
value: | |||
[ | |||
{ | |||
FabricIndex: 1, | |||
FabricIndex: CurrentFabricIndexValue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did the same—set this to 0. Thank you for the review!
This PR addresses issue project-chip/matter-test-scripts#463, where Step 9b of TC-SC-5.1 was failing when the device does not support the Groups Cluster.
Summary of Fix:
Testing
Tested on the following apps:
chip-all-clusters-app 1.0