project-chip / project-chip/matter-test-scripts
TC-CC-5.2 Range variance in steps vs Test Plan. [Matter1.4 TE#2]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
Please follow the below template to file issues/concerns/feature enhancement against Test Scripts:
Summary Title:
There is a large range accepted by the test script for the values read back from the DUT during a change that the test plan list as absolute values.
Description:
In step 1a the DUT is set to known starting points and then in steps 2b, 2c , 2d these values are checked. The target expectations are given as absolute values however the test script offers a fairly large acceptable range for each step. Example here is step 2b, attribute CurrentX has an expected value of 32000 though the range the script offers is Min: 27200 Max: 36800. The step does not reference a tolerance nor does it give an indication to +-n% range on the changing variable.
Does the script need bringing in line more with the test plan, or does the test plan need this acceptable range factoring in?
Steps to reproduce:
Observe CurrentX and CurrentY changes through the full 30s transition state vs Test Plan.
Logs:
Noted in Matter1.4 TE#2 as a test house reviewer. Submitter will need to upload the logs.
Additional Info:
N/A
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 test script steps 1a, 2b, 2c, and 2d alongside the Matter1.4 TE#2 test plan. Observe the CurrentX and CurrentY changes through the full 30-second transition and obtain the referenced logs; done means the source of the range discrepancy is established and the script or test-plan expectation is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100