project-chip / project-chip/matter-test-scripts
[Matter 1.5 TE#2] TC-CADMIN-1.27 Divergences
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:
Script for TC-CADMIN-1.27 test steps de-sync with test plan step numbering. Script step 7 has been commented out with no logging info for test logs.
Description:
Script for TC-CADMIN-1.27 test steps fall out of sync after script step 6 as it collates several into a single grouping. The script continues with script step 7 which now is not reflective of test plan step 7.
Script step 7 is commented out with no information logging to show that the step has been removed pending correction from //github.com/project-chip/connectedhomeip/issues/40836 without looking into the python script itself. Script steps 6 - 8 have no logging and present in the evidence only the step header with no confirmation that any TH required actions have been performed.
Steps to reproduce:
N/A
Logs:
Please provide Test Harness and the DUT logs. Test Harness logs can also be found at "backend/logs" folder. Note and mention the time at which the issue occurred.
Additional Info:
Matter 1.5 TE2
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 TC-CADMIN-1.27 test script with its test plan, focusing on script steps 6–8 and the correction discussed in issue 40836. Review the available evidence and backend/logs for the expected Test Harness and DUT actions. Done means the script numbering matches the test plan and the affected steps provide logging that confirms required actions or explains a pending removal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100