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

# 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: 3.1.4. [TC-BINFO-2.4]  Events [DUT - Client]

PICS:
    - BINFO.C

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

tests:
    - label: "Simulate a Reachable attribute change on the TH"
      PICS: BINFO.C.E03
      verification: |
          "reachable-changed" Event is an Optional event

          As its an optional event we cannot generate the event as of now , hence no example logs provided.

          ./chip-tool basic read-event  reachable-changed 1 0
      disabled: true

    - label: "Simulate a shutdown on the TH"
      PICS: BINFO.C.E01
      verification: |
          Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner) and TH as all-clusters-app.


          To verify shutdown event follow the below commands,

          1. Launch chip-tool into interactive mode with using the below command
          ./chip-tool interactive start


          2.  run below subscribe-event  command in interactive mode shell and then Turn down the TH (all-clusters-app)
          basic subscribe-event shut-down 20 100 1 0

          On DUT as a client side, ,verify that Shutdown event has priority set as CRITICAL

          CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Event 0x0000_0001
          [1653050528.900202][119367:119372] CHIP:TOO:          Event number: 5
          [1653050528.900295][119367:119372] CHIP:TOO:          Priority: Critical
          [1653050528.900386][119367:119372] CHIP:TOO:          Timestamp: 289436805
          [1653050528.900630][119367:119372] CHIP:TOO:   ShutDown: {
          [1653050528.900732][119367:119372] CHIP:TOO:    }
          [1653050528.900892][119367:119372] CHIP:DMG: Refresh LivenessCheckTime for 28000 milliseconds with SubscriptionId = 0x27408c83 Peer = 01:0000000000000
      disabled: true

    - label: "Simulate a (re)start on the TH after the previous shutdown"
      PICS: BINFO.C.E00
      verification: |
          ./chip-tool basic read-event start-up 1 0

           verify that StartUp event has priority set as CRITICAL and software version field on TH(all-clusters-app) log

          [1657193007.841105][5422:5427] CHIP:DMG:         ],
          [1657193007.841137][5422:5427] CHIP:DMG:
          [1657193007.841162][5422:5427] CHIP:DMG:         SuppressResponse = true,
          [1657193007.841186][5422:5427] CHIP:DMG:         InteractionModelRevision = 1
          [1657193007.841209][5422:5427] CHIP:DMG: }
          [1657193007.841358][5422:5427] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Event 0x0000_0000
          [1657193007.841387][5422:5427] CHIP:TOO:          Event number: 0
          [1657193007.841409][5422:5427] CHIP:TOO:          Priority: Critical
          [1657193007.841431][5422:5427] CHIP:TOO:          Timestamp: 132146
          [1657193007.841531][5422:5427] CHIP:TOO:   StartUp: {
          [1657193007.841570][5422:5427] CHIP:TOO:     SoftwareVersion: 1
          [1657193007.841594][5422:5427] CHIP:TOO:    }
          [1657193007.841691][5422:5427] CHIP:EM: Sending Standalone Ack for MessageCounter:91740387 on exchange 60385i"
      disabled: true

    - label: "Simulate a leave current fabric operation on the TH"
      PICS: BINFO.C.E02
      verification: |
          To verify leave event follow the below commands

          1. ./chip-tool interactive start
          2. basic subscribe-event leave 1 100 1 0
          3. operationalcredentials remove-fabric 1 1 0

          verify that leave event has priority as INFO on TH (all-clusters-app)

          [1655369668.996192][2323:2328] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Event 0x0000_0002
          [1655369668.996235][2323:2328] CHIP:TOO:          Event number: 2
          [1655369668.996273][2323:2328] CHIP:TOO:          Priority: Info
          [1655369668.996311][2323:2328] CHIP:TOO:          Timestamp: 659361
          [1655369668.998931][2323:2328] CHIP:TOO:   Leave: {
          [1655369668.998986][2323:2328] CHIP:TOO:    }
      disabled: true