project-chip / project-chip/matter-test-scripts
TC-SC-2.3: 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
-
test case needs a bit of a re-vamp to not assume a factory reset device
-
consider whether this DOES need to be handled for both initial commissioning (ie, needs an explicit factory reset) and subsequent commissioning.
-
consider whether this needs to be done for ECM and BCM if supported
-
consider splitting this test case into two - passcode error verification, which needs to be handled in the three scenarios (initial commissioning, ECM, BCM) and further error verification.
-
if the passcode error case is split out, this is actually a really easy case to automate and is a good addition to the test suite
-
might want to add additional error cases
-
suggest consulting with Amine, who has recently done fuzzing on this area of the codebase.
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 existing TC-SC-2.3 test case and its handling of factory-reset assumptions. Consult Amine's recent fuzzing work, then determine the scope across initial commissioning, ECM, and BCM; done means the passcode error coverage is automated and any additional error cases are explicitly defined.
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