blob: f8d07da34446a9a012d9750c6bf8b86d9c3ae25c [file] [log] [blame]
# Copyright (c) 2023 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.
name: 202.2.4. [TC-OPSTATE-2.4] Mandatory Events with DUT as Server
PICS:
- OPSTATE.S
config:
nodeId: 0x12344321
cluster: "Operational State"
endpoint: 1
tests:
- label: "Step 1: Commission DUT to TH"
cluster: "DelayCommands"
command: "WaitForCommissionee"
arguments:
values:
- name: "nodeId"
value: nodeId
- label: "Step 2: Set up a subscription to the OperationalError event"
PICS: OPSTATE.S.E00
command: "subscribeEvent"
event: "OperationalError"
minInterval: 10
maxInterval: 5000
- label:
"Step 3: At the DUT take the vendor defined action to generate an
OperationalError event"
PICS: OPSTATE.S.E00 && PICS_SKIP_SAMPLE_APP
verification: |
After the subscription interval via the TH (chip-tool) verify:
- reception of an OperationalError Event
- ErrorStateID is a defined error
- If the ErrorStateID is manufacturer specific, inclusion of an ErrorStateLabel, not present otherwise
- Optionally an ErrorStateDetails
NOTE : There's a PIXIT value controlling the ability to execute that ({PIXIT_ERROREVENTGEN}), which as the test case notes, requires vendor specific actions to generated the error at the DUT. This is dependent on the vendor app supporting this. The SDK as it stands won't provide the error, this may be testable by some of the vendors depending on their implementations.
[1692859386.707176][6658:6660] CHIP:EM: Rxd Ack; Removing MessageCounter:212756536 from Retrans Table on exchange 36888i
[1692859386.707295][6658:6660] CHIP:DMG: ReportDataMessage =
[1692859386.707360][6658:6660] CHIP:DMG: {
[1692859386.707416][6658:6660] CHIP:DMG: SubscriptionId = 0x97bb846c,
[1692859386.707477][6658:6660] CHIP:DMG: InteractionModelRevision = 10
[1692859386.707533][6658:6660] CHIP:DMG: }
[1692859386.707621][6658:6660] CHIP:DMG: MoveToState ReadClient[0xffff80011a90]: Moving to [AwaitingSu]
[1692859386.707815][6658:6660] CHIP:EM: <<< [E:36888i S:54523 M:212756537 (Ack:12760634)] (S) Msg TX to 1:0000000000000001 [853D] --- Type 0001:01 (IM:StatusResponse)
[1692859386.707901][6658:6660] CHIP:IN: (S) Sending msg 212756537 on secure session with LSID: 54523
[1692859386.708167][6658:6660] CHIP:DL: HandlePlatformSpecificBLEEvent 32793
[1692859386.708237][6658:6660] CHIP:DL: HandlePlatformSpecificBLEEvent 32793
[1692859386.749217][6658:6660] CHIP:EM: >>> [E:36888i S:54523 M:12760635 (Ack:212756537)] (S) Msg RX from 1:0000000000000001 [853D] --- Type 0001:04 (IM:SubscribeResponse)
[1692859386.749285][6658:6660] CHIP:EM: Found matching exchange: 36888i, Delegate: 0xffff80011aa0
[1692859386.749350][6658:6660] CHIP:EM: Rxd Ack; Removing MessageCounter:212756537 from Retrans Table on exchange 36888i
[1692859386.749417][6658:6660] CHIP:DMG: SubscribeResponse is received
[1692859386.749489][6658:6660] CHIP:DMG: SubscribeResponseMessage =
[1692859386.749538][6658:6660] CHIP:DMG: {
[1692859386.749584][6658:6660] CHIP:DMG: SubscriptionId = 0x97bb846c,
[1692859386.749637][6658:6660] CHIP:DMG: MaxInterval = 0x6,
[1692859386.749687][6658:6660] CHIP:DMG: InteractionModelRevision = 10
[1692859386.749734][6658:6660] CHIP:DMG: }
[1692859386.749787][6658:6660] CHIP:DMG: Subscription established with SubscriptionID = 0x97bb846c MinInterval = 5s MaxInterval = 6s Peer = 01:0000000000000001
[1692859386.749843][6658:6660] CHIP:DMG: MoveToState ReadClient[0xffff80011a90]: Moving to [Subscripti]
cluster: "LogCommands"
command: "UserPrompt"
arguments:
values:
- name: "message"
value: "Enter 'y' after success"
- name: "expectedValue"
value: "y"
- label: "Step 4: TH reads from the DUT the OperationalState attribute"
PICS: OPSTATE.S.A0004 && PICS_SKIP_SAMPLE_APP
command: "readAttribute"
attribute: "OperationalState"
response:
value: 0x03
constraints:
type: enum8