project-chip / project-chip/matter-test-scripts

[Matter 1.5 TE#2] TC-JFDS-2.2 Lack of logging, indication of commented out steps.

Open
#699 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1.5-qa-required
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-JFDS-2.2 lack of qualifiable evidence and omitted steps/validation of steps

Description:

TC-JFDS-2.2 does not print to the logs the contents of received messages and has multiple examples of steps that have been commented out due to a lack of SDK support with no indication in the logging as well as the validation of step 1 which is commented out with no indication provided within the logs.

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:

Please include any other additional or relevant information here. Example: Spec version, PICS version, Test plan version, PICS XML files used for testing PICS, Configuration of the project, related issues,  etc.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the TC-JFDS-2.2 test script and reviewing its existing logging and commented-out steps. Use the Test Harness and DUT logs in backend/logs as a baseline. Done means received message contents are logged and omitted steps, including step 1 validation, are clearly indicated in the test output.

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
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.