project-chip / project-chip/matter-test-scripts
TC-SC-1.4: 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 is going to require a decent amount of plumbing and some thought about how we can determine that the DUT took no further action on a message. This is all do-able, but not sure this is the best use of time right now, so leaving as on-hold for now. The test itself seems reasonable.
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 by reviewing the TC-SC-1.4 test and how the current test flow determines whether the DUT takes further action on a message. The work is done when this scenario is automated with a reliable way to verify that no further action occurred.
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
- 25/100