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

[Feature] Python yamltest parsing that runs using chip-repl #24600

Open
17 of 21 tasks
tehampson opened this issue Jan 23, 2023 · 0 comments
Open
17 of 21 tasks

[Feature] Python yamltest parsing that runs using chip-repl #24600

tehampson opened this issue Jan 23, 2023 · 0 comments
Assignees

Comments

@tehampson
Copy link
Contributor

tehampson commented Jan 23, 2023

Feature description

This is a list of work items that we need to close out to get chip-repl version of the yaml test up to the chip-tool code gen parity

Nice to get to:

  • Look into error spew from IDL parser. This was fixed iteratively over time
  • Integrate chip-repl runner into scripts/tests/yaml/runner.py that was added here.
  • Implement CommissionerCommands::Unpair pseudo cluster. This is a nice to have since currently I don't see any YAML test that currently has this, but it is needed for codegen feature parity.
  • Why are global attributes missing from spec definition from IDL parser. Search for comment "When we cannot find the attribute it is because it is a global attribute like" in src/controller/python/chip/yaml/runner.py
  • Audit all ParseErrors, most should be converted to UnexpectedParseError to make them fatal. Example of one that should remains as a ParseError is inside InvokeAction when command is not found. Increase strictness of error that are raised by chip-repl runner/adapter #25357

General Tracking for things discovered while working on this:

Platform

python

Platform Version(s)

1.1

Anything else?

No response

@tehampson tehampson self-assigned this Jan 23, 2023
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

No branches or pull requests

1 participant