project-chip / project-chip/matter-test-scripts
TC-SC-1.2: Bring back and automate
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
This will need some re-phrasing on the test plan, but mostly just clarifications to avoid saying we're checking things on the DUT. This will need a bit of plumbing on the controller side to mark when / where the acks were received. I'm not sure we have a good way to send unreliable messages through the current set of development controllers.
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 TC-SC-1.2 test plan and the development-controller code; the issue does not name specific files or tests. Clarify the test-plan wording, determine how the controller can record when and where acknowledgements arrive, and assess how unreliable messages can be sent. Done means the clarified plan and automated controller-side checks work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100