-
Notifications
You must be signed in to change notification settings - Fork 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
[matter_yamltests] Add events supports #24831
[matter_yamltests] Add events supports #24831
Conversation
PR #24831: Size comparison from df4ad95 to 4634e5e Increases (4 builds for bl602, nrfconnect, telink)
Decreases (14 builds for bl602, bl702, cc13x2_26x2, nrfconnect, psoc6, qpg, telink)
Full report (53 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
@vivien-apple any chance this makes more tests pass? Could you (after master merge) update |
I don't know the state of the |
4634e5e
to
1c7e269
Compare
PR #24831: Size comparison from a894041 to 1c7e269 Increases (4 builds for bl602, bl702, k32w)
Decreases (2 builds for qpg)
Full report (13 builds for bl602, bl702, cc32xx, k32w, linux, mbed, qpg)
|
Yeah I have local changes to |
1c7e269
to
670a174
Compare
PR #24831: Size comparison from 4982399 to 670a174 Full report (1 build for cc32xx)
|
670a174
to
300ef40
Compare
PR #24831: Size comparison from 062b770 to 300ef40 Full report (1 build for cc32xx)
|
[matter_yamltests] Update TestEvents.yaml to fail is there is unexpected events responses
300ef40
to
a7edcac
Compare
PR #24831: Size comparison from 2e0737c to a7edcac Increases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
Problem
matter_yamltests
does not support having multiple expected values as a response.This is an issue for everything that is testing events in yaml, but more generally this is needed when we will add tests for commands that contains multiple paths (or wildcards).
A simple example would be reading multiple attributes...
As an example, this allow to write things such as:
Using the
chip-tool
adapter I'm able to getTestEvents
and all theTest_ACL_*
that are using events to pass.