Test Added Nov 30 (#23831)

* Added test TC-ACL-2.3 TC-ALOGIN-12.1 TC-BRBINFO-1.1 TC-BRBINFO-2.1 TC-CNET-1.3 TC-DRLK-2.6 TC-WAKEONLAN-4.1 * Auto generated files * Restyled by whitespace * Restyled by prettier-yaml * Modified DGTHREAD PICS * Auto generated files * Modifed WakeOnLan script * Auto generated files * Removed BRBINFO -2.1 test from Darwin Json file * Auto generated files Co-authored-by: Restyled.io <commits@restyled.io>
project-chip · Aug 1, 2023 · 1008743 · 1008743
1 parent 084bcb9
commit 1008743
Show file tree

Hide file tree

Showing 16 changed files with 7,814 additions and 2,716 deletions.
diff --git a/examples/darwin-framework-tool/templates/tests/ciTests.json b/examples/darwin-framework-tool/templates/tests/ciTests.json
@@ -6,6 +6,7 @@
  "TestEvents",
  "TestDiscovery",
  "TestGroupMessaging",
+ "Test_TC_BRBINFO_2_1",
  "Test_TC_DGTHREAD_2_1",
  "Test_TC_DGTHREAD_2_2",
  "Test_TC_DGTHREAD_2_3",

diff --git a/src/app/tests/suites/certification/PICS.yaml b/src/app/tests/suites/certification/PICS.yaml
@@ -3714,10 +3714,10 @@ PICS:
  id: DGTHREAD.S.A0039
 
  - label: "Does the DUT-server support the Delay attribute?"
- id: DGTHREAD.S.A003A
+ id: DGTHREAD.S.A003a
 
  - label: "Does the DUT-server support the SecurityPolicy attribute?"
- id: DGTHREAD.S.A003B
+ id: DGTHREAD.S.A003b
 
  - label: "Does the DUT-server support the ChannelPage0Mask attribute?"
  id: DGTHREAD.S.A003c
@@ -4589,6 +4589,16 @@ PICS:
  - label: "Does the DUT(server) support the ReachableChanged event?"
  id: BINFO.S.E03
 
+ #Features
+ - label: "Does the device implement the Wi-Fi related features ?"
+ id: CNET.S.F00
+
+ - label: "Does the device implement the Thread related features"
+ id: CNET.S.F01
+
+ - label: "Does the device implement the Ethernet related features ?"
+ id: CNET.S.F02
+
  #Client Attributes
  - label: "Does the DUT(Client) support the DataModelRevision attribute?"
  id: BINFO.C.A0000

diff --git a/src/app/tests/suites/certification/Test_TC_ACL_2_3.yaml b/src/app/tests/suites/certification/Test_TC_ACL_2_3.yaml
diff --git a/src/app/tests/suites/certification/Test_TC_ALOGIN_12_1.yaml b/src/app/tests/suites/certification/Test_TC_ALOGIN_12_1.yaml
@@ -20,74 +20,77 @@ PICS:
 
 config:
  nodeId: 0x12344321
- cluster: "Basic"
- endpoint: 0
+ cluster: "Account Login"
+ endpoint: 3
+ TempAccountIdentifier:
+ type: char_string
+ defaultValue: "1111"
+ catalogVendorId:
+ type: int16u
+ defaultValue: 123
+ applicationId:
+ type: char_string
+ defaultValue: "exampleid"
 
 tests:
- - label: "Precondition"
- verification: |
- Test Setup: Commission DUT to TH, if not done so already. In some cases, such as with a Casting Video Player, the DUT commissions the TH (eg. tv-casting-app).
- disabled: true
+ - label: "Wait for the commissioned device to be retrieved"
+ cluster: "DelayCommands"
+ command: "WaitForCommissionee"
+ arguments:
+ values:
+ - name: "nodeId"
+ value: nodeId
 
- - label:
-  "Make sure there is a Content App endpoint implementing the Account
-  Login cluster. Product maker may provide pre-setup steps"
- verification: |
-  The TH commands for this test step can be invoked using chip-tool (when DUT is a commissionee) or tv-casting-app (when DUT is a commissioner).
-
- The following command on the example tv-app will launch a content app on endpoint 4:
- ./chip-tool applicationlauncher launch-app "{"catalogVendorId": 123, "applicationId": "exampleid"}" 1 1
- ./chip-tv-casting-app applicationlauncher launch-app "{"catalogVendorId": 123, "applicationId": "exampleid"}" 1 1
-
- Verify in TH Log:
- [1654004240716] [9799:7814889] CHIP: [DMG] Received Command Response Data, Endpoint=1 Cluster=0x0000_050C Command=0x0000_0003
- [1654004240717] [9799:7814889] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_050C Command 0x0000_0003
- [1654004240717] [9799:7814889] CHIP: [TOO] LauncherResponse: {
-  [1654004240717] [9799:7814889] CHIP: [TOO] status: 0
- [1654004240717] [9799:7814889] CHIP: [TOO] data: 64617461
- [1654004240717] [9799:7814889] CHIP: [TOO] }
- disabled: true
+ - label: "Launch an app with the provided a application ID"
+ PICS: APPLAUNCHER.S.C00.Rsp
+ cluster: "Application Launcher"
+ command: "LaunchApp"
+ arguments:
+ values:
+  - name: "Data"
+  value: "Hello World"
+  - name: "application"
+ value:
+  {
+  catalogVendorId: catalogVendorId,
+  applicationId: applicationId,
+    }
+ response:
+ values:
+  - name: "status"
+  value: 0
 
  - label:
  "TH sends a GetSetupPIN command to the DUT with test values provided
  by the product maker."
  PICS: ALOGIN.S.C00.Rsp
- verification: |
- The TH commands for this test step can be invoked using chip-tool (when DUT is a commissionee) or tv-casting-app (when DUT is a commissioner):
- ./chip-tool accountlogin get-setup-pin 1111 1 4 --timedInteractionTimeoutMs 1000
- ./chip-tv-casting-app accountlogin get-setup-pin 1111 1 4 --timedInteractionTimeoutMs 1000
-
- On TH Verify that the DUT responds with a valid GetSetupPINResponse.
- [1654004273684] [9851:7821178] CHIP: [DMG] Received Command Response Data, Endpoint=4 Cluster=0x0000_050E Command=0x0000_0001
- [1654004273684] [9851:7821178] CHIP: [TOO] Endpoint: 6 Cluster: 0x0000_050E Command 0x0000_0001
- [1654004273684] [9851:7821178] CHIP: [TOO] GetSetupPINResponse: {
- [1654004273684] [9851:7821178] CHIP: [TOO] setupPIN: 34567890
- [1654004273684] [9851:7821178] CHIP: [TOO] }
- disabled: true
+ command: "GetSetupPIN"
+ timedInteractionTimeoutMs: 10000
+ arguments:
+ values:
+ - name: "TempAccountIdentifier"
+ value: TempAccountIdentifier
+ response:
+ values:
+ - name: "setupPIN"
+ saveAs: setupPIN
 
  - label:
  "TH sends a Login command to the DUT with test values provided by the
  product maker."
  PICS: ALOGIN.S.C02.Rsp
- verification: |
-  The TH commands for this test step can be invoked using chip-tool (when DUT is a commissionee) or tv-casting-app (when DUT is a commissioner):
-  ./chip-tool accountlogin login 11111 34567890 1 4 --timedInteractionTimeoutMs 1000
- ./chip-tv-casting-app accountlogin login 11111 34567890 1 4 --timedInteractionTimeoutMs 1000
-
- On TH Verify that the DUT responds with a standard command response.
- [1654004350009] [9951:7836487] CHIP: [DMG] Received Command Response Status for Endpoint=4 Cluster=0x0000_050E Command=0x0000_0002 Status=0x0
- disabled: true
+ command: "Login"
+ timedInteractionTimeoutMs: 10000
+ arguments:
+ values:
+ - name: "tempAccountIdentifier"
+  value: TempAccountIdentifier
+  - name: "setupPIN"
+  value: setupPIN
 
  - label:
  "TH sends a Logout command to the DUT with test values provided by the
  product maker."
  PICS: ALOGIN.S.C03.Rsp
- verification: |
- The TH commands for this test step can be invoked using chip-tool (when DUT is a commissionee) or tv-casting-app (when DUT is a commissioner):
- ./chip-tool accountlogin logout 1 4 --timedInteractionTimeoutMs 1000
- ./chip-tv-casting-app accountlogin logout 1 4 --timedInteractionTimeoutMs 1000
-
- On TH Verify that the DUT responds with a standard command response.
-
- [1654004400892] [9988:7841997] CHIP: [DMG] Received Command Response Status for Endpoint=4 Cluster=0x0000_050E Command=0x0000_0003 Status=0x0
- disabled: true
+ command: "Logout"
+ timedInteractionTimeoutMs: 10000