Fixes issue: 564 & 590

Test_TC_BOOL_2_2
Test_TC_BRBINFO_1_1
Test_TC_CC_1_1
Test_TC_DD_1_7
Test_TC_IDM_4_2
TC_TCCM_2_1
TC_TCCM_3_1
TC_TCCM_3_2
TC_TCCM_3_3
New manual tests:
TC_IDM_10_1
TC_IDM_11_1
TC-CADMIN-1.25
TC-CADMIN-1.26

src/app/tests/suites/certification/PICS.yaml

@@ -336,6 +336,11 @@ PICS:
  "Does commissionee provide a Firmware Information field in the
  AttestationResponse?"
  id: MCORE.DA.ATTESTELEMENT_FW_INFO
+ #
+ #IDM
+ #
+ - label: "Does the device implement the ICD Management cluster as a server?"
+ id: ICDM.S
 
  - label: "Is the device a Server"
  id: MCORE.IDM.S

src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml

@@ -13,7 +13,7 @@
 # limitations under the License.
 # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default
 
-name: 68.2.2. [TC-BOOL-2.2] Primary functionality with server as DUT
+name: 69.2.2. [TC-BOOL-2.2] Primary Functionality with Server as DUT
 
 PICS:
  - BOOL.S
@@ -73,7 +73,7 @@ tests:
  - label: "Step 4a: Set up subscription to StateChange event."
  PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
  verification: |
- Need an SDK implementation required
+ This event is not supported in all clusters app, so there are no reference logs.
 
  Run the below command to start interactive mode
  ./chip-tool interactive start
@@ -86,27 +86,29 @@ tests:
  - label: "Step 4b: Bring the DUT into a state so StateValue is FALSE."
  PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
  verification: |
- Verify the StateValue value is FALSE On TH(chip-tool), below is the sample log provided for the raspi platform
+ Verify the StateValue value is FALSE On TH(chip-tool), if the state-change event is generated
  disabled: true
 
  - label: "Step 4c: TH reads the StateValue attribute from the DUT."
  PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
  verification: |
+ This event is not supported in all clusters app, so there are no reference logs.
+
  booleanstate read state-value 1 1
 
- Verify the StateValue value is FALSE On TH(chip-tool), below is the sample log provided for the raspi platform
+ Verify the StateValue value is FALSE On TH(chip-tool)
  disabled: true
 
  - label: "Step 4d: Bring the DUT into a state so StateValue is TRUE."
  PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
  verification: |
- Verify the StateValue value is TRUE On TH(chip-tool), below is the sample log provided for the raspi platform
+ Verify the StateValue value is TRUE On TH(chip-tool),  if the state-change event is generated
  disabled: true
 
  - label: "Step 4e: TH reads the StateValue attribute from the DUT."
  PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
  verification: |
  booleanstate read state-value 1 1
 
- Verify the StateValue value is TRUE On TH(chip-tool), below is the sample log provided for the raspi platform
+ Verify the StateValue value is TRUE On TH(chip-tool)
  disabled: true

src/app/tests/suites/certification/Test_TC_BRBINFO_1_1.yaml

@@ -34,13 +34,26 @@ tests:
  - name: "nodeId"
  value: nodeId
 
+ #Issue https://github.com/project-chip/connectedhomeip/issues/26602
  - label: "Step 2: TH reads the ClusterRevision from DUT"
- command: "readAttribute"
- attribute: "ClusterRevision"
- response:
- value: 1
- constraints:
- type: int16u
+ verification: |
+ ./chip-tool bridgeddevicebasicinformation read cluster-revision 1 3
+
+ Via the TH (chip-tool), verify: 
+ -that the ClusterRevision attribute contains value as 2. 
+ -that value is in the type of uint16.
+
+ [1657695910.794487][15411:15416] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_FFFD DataVersion: 2577979325
+ [1657695910.794568][15411:15416] CHIP:TOO: ClusterRevision: 2
+ cluster: "LogCommands"
+ command: "UserPrompt"
+ PICS: PICS_USER_PROMPT
+ arguments:
+ values:
+ - name: "message"
+ value: "Please enter 'y' for success"
+ - name: "expectedValue"
+ value: "y"
 
  - label: "Step 3: TH reads the FeatureMap from DUT"
  command: "readAttribute"

src/app/tests/suites/certification/Test_TC_CC_1_1.yaml

@@ -31,13 +31,25 @@ tests:
  - name: "nodeId"
  value: nodeId
 
+ #Issue: https://github.com/project-chip/connectedhomeip/issues/26598
  - label: "Step 2: read the global attribute: ClusterRevision"
- command: "readAttribute"
- attribute: "ClusterRevision"
- response:
- value: 5
- constraints:
- type: int16u
+ verification: |
+ ./chip-tool colorcontrol read cluster-revision 1 1
+
+ Verify "ClusterRevision" value is of unit16 and reflects the highest revision number, in RPI the value of ClusterRevision is 6 on the TH(Chip-tool) Log and below is the sample log provided for the raspi platform:
+
+ [1649660967.485745][7940:7945] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0300 Attribute 0x0000_FFFD DataVersion: 4087274515
+ [1649660967.485839][7940:7945] CHIP:TOO: ClusterRevision:5
+ [1649660967.485946][7940:7945] CHIP:EM: Sending Standalone Ack for MessageCounter:1573389 on exchange 13361i
+ cluster: "LogCommands"
+ command: "UserPrompt"
+ PICS: PICS_USER_PROMPT
+ arguments:
+ values:
+ - name: "message"
+ value: "Please enter 'y' for success"
+ - name: "expectedValue"
+ value: "y"
 
  - label: "Step 3a: Read the global attribute: FeatureMap"
  PICS: ( !CC.S.F00 && !CC.S.F01 && !CC.S.F02 && !CC.S.F03 && !CC.S.F04 )

src/app/tests/suites/certification/Test_TC_DD_1_7.yaml

@@ -38,9 +38,9 @@ tests:
 
  - Printed using a minimum font size of 6 points, typically producing a typeface height of 2.1 mm (6/72 inches)
 
- - Include dashes between the groups of Manual Pairing Code digits (e.g. "MATTER 1234-5678-901")
+ - Include dashes between the groups of Manual Pairing Code digits with the following spacing:
 
- - If the code is presented in audio format it SHOULD be read in groups of 4 digits, with the last group being only 3 or 1 digits depending on overall size.
+ - For 11 or 21-digit codes, the first row spacing is 4-3-4 (First Row: "1234-567-8901")
 
- - If a Matter logo cannot be printed alongside the code then the code SHOULD be prefixed with MATTER (e.g. "MATTER 1234-5678-901")
+ - For 21-digit codes, the second row spacing is 4-3-2-1 (Second Row:"9876-543-21-0")
  disabled: true