project-chip / project-chip/matter-test-scripts
TC-SC-1.3: Bring back and Automate. Consider adding timing.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
- is the PICS correct on this? This seems like it would apply to any device that was capable of initiating messages. This basically means clients.
- needs plumbing in the TH
For the most part, we haven't seen DUTs in the field not sending re-transmissions. What we SHOULD check is that the timing parameters are respected.
Going to mark this as on-hold for now since the current test doesn't check anything that has been causing actual problems in the field. Should re-think checking timing parameters properly.
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
Review the current TC-SC-1.3 test and determine whether its PICS applies to all message-initiating clients. Trace the required plumbing in the TH, then define how retransmission timing parameters should be checked. Done means the scope is agreed and the timing behavior is automated rather than only retransmission occurrence being tested.
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
- 30/100