blob: e2543a3f38c01c31af711f5f24132e53e46848fa [file] [log] [blame]
# 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.4.6. [TC-APPLAUNCHER-3.8.1] Stop Application Verification (DUT as Client)
config:
nodeId: 0x12344321
cluster: "Basic"
endpoint: 0
tests:
- label: "DUT sends StopApp command to TH"
PICS: APPLAUNCHER.C.C0001
verification: |
product maker needs to provide instructions for how to trigger the command:
Refer to device or application documentation for special argument values to each command, and/or additional steps required to put device into in correct state to exhibit test behavior.
The following chip-tool command simulates the interaction of the DUT and the log below shows the resulting log on the TH.
./chip-tool applicationlauncher stop-app '{"catalogVendorId": 123, "applicationId": "exampleid"}' 1 1
[1646163695248] [9384:3955170] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_050C Command 0x0000_0003
[1646163695249] [9384:3955170] CHIP: [TOO] LauncherResponse: {
[1646163695249] [9384:3955170] CHIP: [TOO] status: 0
[1646163695249] [9384:3955170] CHIP: [TOO] data: 64617461
[1646163695249] [9384:3955170] CHIP: [TOO] }
disabled: true