project-chip / project-chip/matter-test-scripts
python framework: Clean up commissioning to make this more intuitive for authors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
Right now, the test harness is using the is_commissioning flag on the test steps to determine if a test requires that the device be commissioned. This was not what this flag was intended for originally, there's no check that it's correct in the CI and it's confusing to authors.
There needs to be a better way.
Tests should have an explicit way to declare whether or not they require commissioning, and should detect if the device requires commissioning before running.
You will need to work with the TH team to refine an approach here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test harness and its use of the is_commissioning flag on test steps, then review how commissioning requirements are represented and checked in CI. Work with the TH team to refine the approach. Done means tests explicitly declare whether commissioning is required and detect whether the device needs commissioning before running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100