project-chip / project-chip/matter-test-scripts
[Smoke & CO Alarm Cluster] Subscription step mismatch between Test Plan and YAML scripts (TC-SMOKECO-2.4, 2.5, 2.6)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
During validation of the Smoke and CO Alarm Cluster, mismatches were found between the Test Plan and the corresponding YAML test scripts.
In multiple steps, the YAML script includes a subscription operation that is not specified in the Test Plan.
Affected Test Cases:
- TC-SMOKECO-2.4
- Mismatch in Step 47 — the Test Plan does not specify a subscription, but the script performs one.
- Note: Step 38 also includes a subscription, but it is aligned with the Test Plan.
- TC-SMOKECO-2.5
- Same issue observed in Steps 52, 56, 62, 68, and 72.
- TC-SMOKECO-2.6
- Same issue observed in Steps 9, 11, 13, 15, 17, 23, 26, 29, and 32.
Expected Behavior:
- YAML scripts should match the Test Plan behavior.
- Subscription steps should be implemented only where the Test Plan explicitly defines them.
Proposed Fix:
- Review and remove (or justify) the unintended subscription steps from the YAML scripts.
- Ensure script steps are consistent with the Test Plan expectations for each test case.
Test-plan Reference : https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/smco.adoc#test-cases
Script Reference :
- https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_SMOKECO_2_4.yaml
- https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_SMOKECO_2_5.yaml
- https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_SMOKECO_2_6.yaml
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 comparing the listed steps in Test_TC_SMOKECO_2_4.yaml, Test_TC_SMOKECO_2_5.yaml, and Test_TC_SMOKECO_2_6.yaml with the referenced Smoke and CO test-plan cases. Check each reported subscription operation against the plan, then remove or document only the mismatches. Done means all three YAML scripts follow the explicitly defined subscription behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100