project-chip / project-chip/matter-test-scripts
TC-CC-3.4 Test case queries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
I'm wondering how the test goes to commission TH when the DUT selects the client role of the cluster, the DUT itself is a commissionee, except that it contains client clusters. could it be that the DUT here needs to run a chip-tool tool? The example is as follows
tests:
#- label: "Wait for the device to be commissioned"
# cluster: "DelayCommands"
# command: "WaitForCommissioning"
- label: "PreCondition: Set TH OnOff to On"
cluster: "On/Off"
wait: "On"
- label: "DUT sends MoveToHue command to TH an Hue with _TransitionTime 300"
wait: "MoveToHue"
PICS: CC.C.C00.Tx && CC.C.F00
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
Read the TC-CC-3.4 test case and the shown YAML steps, then verify how the DUT and TH should interact when the DUT selects the client role and contains client clusters. Done means clarifying whether chip-tool is required and documenting the expected commissioning and MoveToHue sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100