Skip to content

Commit

Permalink
Updates Test_TC_SU_2_3.yaml, Test_TC_SU_2_5.yaml, Test_TC_SU_3_3.yaml
Browse files Browse the repository at this point in the history
Removes Test_TC_SU_4_2.yaml
Adds Test_TC_SU_5_1.yaml
  • Loading branch information
raul-marquez-csa committed Mar 18, 2024
1 parent dbfc029 commit c03c073
Show file tree
Hide file tree
Showing 5 changed files with 42 additions and 233 deletions.
8 changes: 0 additions & 8 deletions src/app/tests/suites/certification/Test_TC_SU_2_3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -119,11 +119,3 @@ tests:
verification: |
Out of scope
disabled: true

- label:
"Step 6: Perform the OTA Update on DUT using vendor specific
mechanism."
PICS: MCORE.OTA.VendorSpecific
verification: |
Use vendor specific steps to initiate OTA Update and verify that the software image is transferred to the DUT
disabled: true
8 changes: 0 additions & 8 deletions src/app/tests/suites/certification/Test_TC_SU_2_5.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -157,11 +157,3 @@ tests:
[1653636406.637617][11116:11121] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_000A DataVersion: 1527020963
[1653636406.637708][11116:11121] CHIP:TOO: SoftwareVersion: 1
disabled: true

- label:
"Step 6: Apply the OTA Update on DUT using vendor specific mechanism."
PICS: MCORE.OTA.VendorSpecific
verification: |
Use vendor specific steps to apply OTA Update and verify that the DUT starts updating its software.
Once the update is finished verify the software version on the DUT to match the version downloaded for the software update.
disabled: true
8 changes: 0 additions & 8 deletions src/app/tests/suites/certification/Test_TC_SU_3_3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -121,11 +121,3 @@ tests:
verification: |
Out of scope
disabled: true

- label:
"Step 6: Perform the OTA Update from DUT using vendor specific
mechanism."
PICS: MCORE.OTA.VendorSpecific
verification: |
Use vendor specific steps to initiate OTA Update and verify that the software image is transferred from the DUT
disabled: true
209 changes: 0 additions & 209 deletions src/app/tests/suites/certification/Test_TC_SU_4_2.yaml

This file was deleted.

42 changes: 42 additions & 0 deletions src/app/tests/suites/certification/Test_TC_SU_5_1.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# 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: 46.11.1. [TC-SU-5.1] Verifying vendor specific OTA implementation on DUT

PICS:
- MCORE.OTA.VendorSpecific

config:
nodeId: 0x12344321
cluster: "Basic Information"
endpoint: 0

tests:
- label:
"Step 1: Perform the OTA Update on DUT using vendor specific
mechanism. Verify that the DUT starts updating its software. Once the
update is finished, verify the SoftwareVersion attribute from the
Basic Information cluster on the DUT to match the version downloaded
for the software update."
verification: |
Perform the OTA Update on DUT using vendor specific mechanism.
After the OTA-transfer is finished successfully , verfiy the software version is update:
./chip-tool basicinformation read software-version 321 0
[1653636406.637617][11116:11121] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_000A DataVersion: 1527020963
[1653636406.637708][11116:11121] CHIP:TOO: SoftwareVersion: 2
disabled: true

0 comments on commit c03c073

Please sign in to comment.