Skip to content

Commit c03c073

Browse files
Updates Test_TC_SU_2_3.yaml, Test_TC_SU_2_5.yaml, Test_TC_SU_3_3.yaml
Removes Test_TC_SU_4_2.yaml Adds Test_TC_SU_5_1.yaml
1 parent dbfc029 commit c03c073

File tree

5 files changed

+42
-233
lines changed

5 files changed

+42
-233
lines changed

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

-8
Original file line numberDiff line numberDiff line change
@@ -119,11 +119,3 @@ tests:
119119
verification: |
120120
Out of scope
121121
disabled: true
122-
123-
- label:
124-
"Step 6: Perform the OTA Update on DUT using vendor specific
125-
mechanism."
126-
PICS: MCORE.OTA.VendorSpecific
127-
verification: |
128-
Use vendor specific steps to initiate OTA Update and verify that the software image is transferred to the DUT
129-
disabled: true

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

-8
Original file line numberDiff line numberDiff line change
@@ -157,11 +157,3 @@ tests:
157157
[1653636406.637617][11116:11121] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_000A DataVersion: 1527020963
158158
[1653636406.637708][11116:11121] CHIP:TOO: SoftwareVersion: 1
159159
disabled: true
160-
161-
- label:
162-
"Step 6: Apply the OTA Update on DUT using vendor specific mechanism."
163-
PICS: MCORE.OTA.VendorSpecific
164-
verification: |
165-
Use vendor specific steps to apply OTA Update and verify that the DUT starts updating its software.
166-
Once the update is finished verify the software version on the DUT to match the version downloaded for the software update.
167-
disabled: true

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

-8
Original file line numberDiff line numberDiff line change
@@ -121,11 +121,3 @@ tests:
121121
verification: |
122122
Out of scope
123123
disabled: true
124-
125-
- label:
126-
"Step 6: Perform the OTA Update from DUT using vendor specific
127-
mechanism."
128-
PICS: MCORE.OTA.VendorSpecific
129-
verification: |
130-
Use vendor specific steps to initiate OTA Update and verify that the software image is transferred from the DUT
131-
disabled: true

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

-209
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
# Copyright (c) 2021 Project CHIP Authors
2+
#
3+
# Licensed under the Apache License, Version 2.0 (the "License");
4+
# you may not use this file except in compliance with the License.
5+
# You may obtain a copy of the License at
6+
#
7+
# http://www.apache.org/licenses/LICENSE-2.0
8+
#
9+
# Unless required by applicable law or agreed to in writing, software
10+
# distributed under the License is distributed on an "AS IS" BASIS,
11+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12+
# See the License for the specific language governing permissions and
13+
# limitations under the License.
14+
# Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default
15+
16+
name: 46.11.1. [TC-SU-5.1] Verifying vendor specific OTA implementation on DUT
17+
18+
PICS:
19+
- MCORE.OTA.VendorSpecific
20+
21+
config:
22+
nodeId: 0x12344321
23+
cluster: "Basic Information"
24+
endpoint: 0
25+
26+
tests:
27+
- label:
28+
"Step 1: Perform the OTA Update on DUT using vendor specific
29+
mechanism. Verify that the DUT starts updating its software. Once the
30+
update is finished, verify the SoftwareVersion attribute from the
31+
Basic Information cluster on the DUT to match the version downloaded
32+
for the software update."
33+
verification: |
34+
Perform the OTA Update on DUT using vendor specific mechanism.
35+
36+
After the OTA-transfer is finished successfully , verfiy the software version is update:
37+
38+
./chip-tool basicinformation read software-version 321 0
39+
40+
[1653636406.637617][11116:11121] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_000A DataVersion: 1527020963
41+
[1653636406.637708][11116:11121] CHIP:TOO: SoftwareVersion: 2
42+
disabled: true

0 commit comments

Comments
 (0)