project-chip / project-chip/matter-test-scripts
[Matter 1.5 TE#2] TC-JFADMIN-2.2 Lack of qualifiable logging
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:
TC-JFADMIN-2.2 lacks visibility of values in the logging and does not have logging of the omission of step 8 which was skipped due to the SDK not supporting that aspect.
Description:
The script has not been written with verbose logging enabled which means that the log file provides no evidence of the contents of DUT response being assessed. Step 8 is not indicated at all providing no logged reason as to why it was not run (which is due to the SDK not implementing support for this aspect).
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 TE#2
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
Locate the test script for TC-JFADMIN-2.2 and review its logging behavior, using the harness output under backend/logs as a reference. Check how DUT response values are assessed and how the skipped step 8 is represented. Done means the log provides evidence for the assessed values and explains why step 8 was not run.
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
- 48/100