Skip to content
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

Add mapping or lookup method of Cluster IDs for verification on Test Harness. #8575

Closed
trombadore-google opened this issue Jul 22, 2021 · 2 comments · Fixed by #8749
Closed
Assignees

Comments

@trombadore-google
Copy link

Problem

We need access to the Cluster IDs present in XML and ZAP files within the test harness. We need this as a source of truth for verification against the cluster IDs we get from DUTs' responses to different cluster commands during testing.

Proposed Solution

Please add some mapping or lookup capability that we can use to validate the cluster IDs we get from DUT responses against the valid cluster IDs that are predefined by spec and hard coded already within the xml and zap file.

Please note that the test harness does not have access to these xml or zap file as we just take in the built code itself.

This issue is blocking (please refer to it for further context) : https://github.com/chip-csg/chip-certification-tool/issues/201

@trombadore-google
Copy link
Author

@erjiaqing can you assign this effort to yourself? I don't know why I do not have permissions to assign you...

@SaileeG @Xiole-KKE @wahajsyed

@trombadore-google
Copy link
Author

trombadore-google commented Jul 30, 2021

Follow-up notes from @erjiaqing and I's sync:

  • We want the look-up method to take in a Cluster ID # and pass back the cluster name and commands.
  • We want the look-up method to be apart of the controller and not apart of the app side.
  • The data that method looks up should be autogenerated from spec at build time of the whl pkg (which you demonstrated that it already is during zap file generation.)

Please ping me if you have any further questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants