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

[Matter 1.5 TE#2] TC-JFADMIN-2.1 Lack of evidence

Open
#700 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-JFADMIN-2.1 does not provide visibility of the values received from the DUT after performing actions in the logging.

Description:

TC-JFADMIN-2.1 is not enabling verbose logging so we have no recordable evidence of the values provided by the DUT in the logs.

Steps to reproduce:

N/A

Logs:

Example of step 2 logging. Step is to compare value received has the same FabricID as the AdministratorFabricIndex read in step 1:
09-23 15:17:25.564 INFO ***** Test Step 2 : TH1 read Fabrics attribute from Operation Cluster on EP0.
09-23 15:17:25.565 INFO Found an existing secure session to [6:0000000000000001]!
09-23 15:17:25.567 INFO 0 data version filters provided, 0 not relevant, 0 encoded, 0 skipped due to lack of space
09-23 15:17:25.567 INFO <<< [E:18405i S:1837 M:41438762] (S) Msg TX from 0000000000000065 to 6:0000000000000001 [F828] [UDP:[fe80::250:56ff:fe90:fc7d%ens192]:5238] --- Type 0001:02 (IM:ReadRequest) (B:51)
09-23 15:17:25.568 INFO ??1 [E:18405i S:1837 M:41438762] (S) Msg Retransmission to 6:0000000000000001 scheduled for 397ms from now [State:Active II:500 AI:300 AT:4000]
09-23 15:17:25.568 INFO >>> [E:18405i S:1837 M:260295238 (Ack:41438762)] (S) Msg RX from 6:0000000000000001 [F828] to 0000000000000065 --- Type 0001:05 (IM:ReportData) (B:156)
09-23 15:17:25.570 INFO <<< [E:18405i S:1837 M:41438763 (Ack:260295238)] (S) Msg TX from 0000000000000065 to 6:0000000000000001 [F828] [UDP:[fe80::250:56ff:fe90:fc7d%ens192]:5238] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)

Additional Info:

Matter 1.5 TE#2

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-JFADMIN-2.1 test script and its logging configuration, then review the logging around step 2 and the Fabrics attribute read. Reproduce the test if possible and confirm that the values returned by the DUT, including the FabricID comparison value, are recorded in the logs. Done means the test provides recordable evidence of those received values.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.