-
Notifications
You must be signed in to change notification settings - Fork 2.1k
/
Copy pathTest_TC_MC_11_1.yaml
146 lines (122 loc) · 7.45 KB
/
Test_TC_MC_11_1.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
# Copyright (c) 2021 Project CHIP Authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# 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:
19.13.1. [TC-MC-11.1] Casting Video Player via User-Directed Commissioning
Verification (DUT as Server)
PICS:
- MC.S.M.UDCLOGIN
config:
nodeId: 0x12344321
cluster: "Basic Information"
endpoint: 0
tests:
- label: "Note"
verification: |
Refer to device or application documentation for supported DUT configuration.
For step 3 (prompt user), manufacturer may utilize a custom method for obtaining user consent other than an on-screen prompt.
Refer to manufacturer provided instructions for special argument values to each command, and/or additional steps required to put DUT into correct state to exhibit test behavior.
disabled: true
- label: "Pre-Conditions"
verification: |
1. DUT and Harness support Commissioner Discovery feature
2. DUT is already in the network
3. DUT supports AccountLogin cluster for certain Content Apps
disabled: true
- label:
"Step 1: TH start scanning for available commissioners using
Commissioner Discovery"
verification: |
./chip-tv-casting-app
The shell should show a discovered commissioner, similar to the following:
[1653089767279] [88361:1149415] CHIP: [SVR] Discovered Commissioner #0
[1653089767279] [88361:1149415] CHIP: [DIS] Hostname: 147dda9ac00a
[1653089767279] [88361:1149415] CHIP: [DIS] IP Address #1: 169.254.81.148
[1653089767279] [88361:1149415] CHIP: [DIS] Port: 5650
[1653089767279] [88361:1149415] CHIP: [DIS] Mrp Interval idle: 5000 ms
[1653089767279] [88361:1149415] CHIP: [DIS] Mrp Interval active: 2000 ms
[1653089767279] [88361:1149415] CHIP: [DIS] Device Name: Test TV
[1653089767279] [88361:1149415] CHIP: [DIS] Vendor ID: 65521
[1653089767279] [88361:1149415] CHIP: [DIS] Product ID: 32769
[1653089767279] [88361:1149415] CHIP: [DIS] Device Type: 35
[1653089767279] [88361:1149415] CHIP: [DIS] Instance Name: 3DC86F5236D636CB
[1653089767279] [88361:1149415] CHIP: [DIS] Commissioning Mode: 0
[1653089767279] [88361:1149415] CHIP: [SVR] 1 commissioner(s) discovered. Select one (by number# above) to request commissioning from:
[1653089767279] [88361:1149415] CHIP: [SVR] Example: cast request 0
disabled: true
- label:
"Step 2: TH is instructed to select the commissioner found in step 1"
verification: |
Into the shell, enter "cast request 0" to send a user-directed-commissioning request to the DUT
> cast request 0
[1653179218011] [47890:1899175] CHIP: [DL] request
[1653179218011] [47890:1899175] CHIP: [SVR] ------- PrepareForCommissioning
[1653179218011] [47890:1899175] CHIP: [SVR] Server initializing...
disabled: true
- label:
"Step 3: DUT prompt user for onboarding by giving an option to accept
or reject the commissioning of TH ."
verification: |
UX will vary by product maker. The following is the tv-app shell output:
[1653179219087] [89108:1898759] CHIP: [CTL] ------PROMPT USER: Test TV casting app is requesting permission to cast to this TV, approve? [0x0000_FFF1,0x0000_8001,E0707BB1AFFA6F23,020096D16895275F1B49A07221F0E588E06B]
[1653179219087] [89108:1898759] CHIP: [CTL] ------Via Shell Enter: controller ux ok|cancel
disabled: true
- label:
"Step 4: DUT start the commissioning procedure with TH, when user
accepts the commissioning"
verification: |
Into the DUT UX, accept request for commissioning. Manufacturer may utilize a custom method for obtaining user consent other than an on-screen prompt.
The following is the tv-app shell command to accept the request
> controller ux ok
The commissioning success completion is indicated in the TH with the following shell output:
[1653088463910] [86837:1122544] CHIP: [SVR] Commissioning completed successfully
disabled: true
- label: "Step 5: TH reads the endpoints from the DUT"
verification: |
Into the shell, enter " cast cluster descriptor read device-type-list 0 1" to read the device list of the descriptor cluster on endpoint 1
> cast cluster descriptor read device-type-list 0 1
....
[1653180010083] [48426:1914389] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_001D Attribute 0x0000_0000 DataVersion: 2009082322
[1653180010083] [48426:1914389] CHIP: [TOO] device list: 1 entries
[1653180010083] [48426:1914389] CHIP: [TOO] [1]: {
[1653180010083] [48426:1914389] CHIP: [TOO] Type: 35
[1653180010083] [48426:1914389] CHIP: [TOO] Revision: 1
[1653180010083] [48426:1914389] CHIP: [TOO] }
disabled: true
- label: "Step 6: TH reads the endpoints from the DUT"
verification: |
Into the shell, enter "cast cluster descriptor read device-type-list 0 2" to read the device list of the descriptor cluster on endpoint 2
> cast cluster descriptor read device-type-list 0 2
....
[1653180162379] [48426:1917385] CHIP: [TOO] Endpoint: 2 Cluster: 0x0000_001D Attribute 0x0000_0000 DataVersion: 631462374
[1653180162379] [48426:1917385] CHIP: [TOO] device list: 1 entries
[1653180162379] [48426:1917385] CHIP: [TOO] [1]: {
[1653180162379] [48426:1917385] CHIP: [TOO] Type: 34
[1653180162379] [48426:1917385] CHIP: [TOO] Revision: 1
[1653180162379] [48426:1917385] CHIP: [TOO] }
disabled: true
- label: "Step 7: TH reads the endpoints from the DUT"
verification: |
Into the shell, enter "cast cluster descriptor read device-type-list 0 4" to read the device list of the descriptor cluster on endpoint 4
Descriptor cluster is supporting endpoint 1 and 2 in RPI platform hence if TH tried to read the device list of the descriptor cluster on endpoint 4 from the DUT, DUT should send the response as UNSUPPORTED_ENDPOINT,
It may vary based the DUT
> cast cluster descriptor read device-type-list 0 4
....
[1653180214397] [48426:1919098] CHIP: [TOO] Endpoint: 6 Cluster: 0x0000_001D Attribute 0x0000_0000 DataVersion: 4094146641
[1653180214397] [48426:1919098] CHIP: [TOO] device list: 1 entries
[1653180214397] [48426:1919098] CHIP: [TOO] [1]: {
[1653180214397] [48426:1919098] CHIP: [TOO] Type: 36
[1653180214397] [48426:1919098] CHIP: [TOO] Revision: 1
[1653180214397] [48426:1919098] CHIP: [TOO] }
disabled: true