You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/app/tests/suites/certification/Test_TC_ALOGIN_12_2.yaml
+37
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,43 @@ tests:
27
27
- label: "Preconditions"
28
28
verification: |
29
29
Commission TH to DUT, if not done so already. In some cases, such as with a Casting Video Player, the TH commissions the DUT.
30
+
31
+
Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner) or tv-casting-app (when DUT is a commissionee):
32
+
33
+
The following command on the example tv-app will launch a content app on endpoint 4:
- label: "Step 2: TH reads the ClusterRevision attribute from the DUT"
36
-
verification: |
37
-
./chip-tool modeselect read cluster-revision 1 1
38
-
39
-
Verify the "ClusterRevision" value is of unit16 and reflects the highest revision number 2 on the TH(Chip-tool) and below is the sample log provided for the raspi platform:
0 commit comments