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

[Matter 1.5 TE#2] Test Steps are interleaved with packet decoding

Open
#708 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
19
Forks
7
Avg merge
3d 17h
Merged PRs (30d)
3

Description

Summary Title:

TC-CHIME-2.1 , TCH-CHIME-2.2 logs from Matter 1.5 TE#2 - the Test Steps are interleaved with packet decoding in TH logs.

Description:

See log examples

Steps to reproduce:

Please provide detailed "steps to reproduce" whenever applicable.

Logs:

Example 1 - TC-CHIME-2.1:
[MatterTest] 09-24 22:37:13.872 INFO }
[MatterTest] 09-24 22:37:13.873 INFO >>> [E:2414i S:22538 M:39750994 (Ack:76533045)] (S) Msg RX from 1:0000000012344321 [3A7C] to 000000000001B669 --- Type 0001:05 (IM:ReportData) (B:150)
[MatterTest] 09-24 22:37:13.916 INFO {
[MatterTest] 09-24 22:37:13.919 INFO ***** Test Step 3 : Verify that all of the ChimeIDs in InstalledChimeSounds are unique
[MatterTest] 09-24 22:37:13.920 INFO "event" : "MessageSend",
[MatterTest] 09-24 22:37:13.923 INFO "messageTotalSize" : 34,
[MatterTest] 09-24 22:37:13.924 INFO "messageType" : "Secure",
[MatterTest] 09-24 22:37:13.926 INFO "packetHeader" :
[MatterTest] 09-24 22:37:13.927 INFO {
[MatterTest] 09-24 22:37:13.928 INFO ***** Test Step 4 : Verify that all of the Names in InstalledChimeSounds are unique
[MatterTest] 09-24 22:37:13.929 INFO "flags" : 0,
[MatterTest] 09-24 22:37:13.931 INFO "msgCounter" : 76533048,
[MatterTest] 09-24 22:37:13.933 INFO "securityFlags" : 0,
[MatterTest] 09-24 22:37:13.935 INFO "sessionId" : 41662
[MatterTest] 09-24 22:37:13.936 INFO ***** Test Step 5 : Read and verify SelectedChime attribute
[MatterTest] 09-24 22:37:13.937 INFO },
[MatterTest] 09-24 22:37:13.939 INFO "payload" :
[MatterTest] 09-24 22:37:13.941 INFO {
[MatterTest] 09-24 22:37:13.943 INFO "decoded" :
[MatterTest] 09-24 22:37:13.944 INFO {
[MatterTest] 09-24 22:37:13.945 INFO "mrp_ack" : ""

Example 2 - TC-CHIME-2.2:
[MatterTest] 09-24 22:37:12.762 INFO "payload" :
[MatterTest] 09-24 22:37:12.785 INFO {
[MatterTest] 09-24 22:37:12.807 INFO "decoded" :
[MatterTest] 09-24 22:37:12.830 INFO {
[MatterTest] 09-24 22:37:12.854 INFO "mrp_ack" : ""
[MatterTest] 09-24 22:37:12.877 INFO },
[MatterTest] 09-24 22:37:12.900 INFO "hex" : "",
[MatterTest] 09-24 22:37:12.907 INFO "size" : 0
[MatterTest] 09-24 22:37:12.930 INFO },
[MatterTest] 09-24 22:37:12.954 INFO "payloadHeader" :
[MatterTest] 09-24 22:37:12.958 INFO Running test on endpoint 1
[MatterTest] 09-24 22:37:12.959 INFO {
[MatterTest] 09-24 22:37:12.961 INFO ***** Test Step 1 : Commissioning, already done
[MatterTest] 09-24 22:37:12.962 INFO "ackMessageCounter" : 39750993,
[MatterTest] 09-24 22:37:12.964 INFO "exchangeFlags" : 3,
[MatterTest] 09-24 22:37:12.966 INFO "exchangeId" : 2413,
[MatterTest] 09-24 22:37:12.967 INFO ***** Test Step 2 : Read InstalledChimeSounds, verify list and field value conformance
[MatterTest] 09-24 22:37:12.968 INFO "initiator" : true,
[MatterTest] 09-24 22:37:12.970 INFO "messageType" : 16,
[MatterTest] 09-24 22:37:12.971 INFO "needsAck" : false,
[MatterTest] 09-24 22:37:12.973 INFO "protocolId" : 0
[MatterTest] 09-24 22:37:12.976 INFO }
[MatterTest] 09-24 22:37:12.978 INFO }
[MatterTest] 09-24 22:37:12.980 INFO <<< [E:2413i S:22538 M:76533042 (Ack:39750993)] (S) Msg TX from 000000000001B669 to 1:0000000012344321 [3A7C] [UDP:[fe80::ebf:74ff:fe00:2ef%eth0]:5540] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)
[MatterTest] 09-24 22:37:12.990 INFO {
[MatterTest] 09-24 22:37:12.991 INFO "event" : "MessageReceived",
[MatterTest] 09-24 22:37:12.992 INFO "messageTotalSize" : 228,

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 reproducing TC-CHIME-2.1 and TC-CHIME-2.2 and comparing their MatterTest logs with the examples in this issue. Trace how test-step messages and packet-decoding output are emitted, then verify that each log's test steps and decoded packet fields remain in the intended order.

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
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.