# 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.3.2. [TC-DGGEN-3.2] Command generated at client as DUT

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

tests:
    - label: "Commission TH to DUT"
      verification: |
          verification step to be updated.
      disabled: true

    - label:
          "Provision DUT with EnableKey with 128 bit value provided and matched
          a value chosen by the manufacturer and configured on the TH using
          manufacturer-specific means. EventTrigger value is configured and
          SHALL indicate the test or test mode which DUT wants to trigger the
          testing use by manufacturers."
      PICS: DGGEN.C.C00.Tx
      verification: |
          1. Read if TestEventTriggersEnabled attribute is set to true using ./chip-tool generaldiagnostics read test-event-triggers-enabled  1 0

          Spec Issue:-5265
           ./chip-tool generaldiagnostics read   test-event-triggers-enabled  1 0

          Verify in DUT as client side:

          [1655188892.957794][2868:2873] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0033 Attribute 0x0000_0008 DataVersion: 3562689442
          [1655188892.957869][2868:2873] CHIP:TOO:   TestEventTriggersEnabled: FALSE
          [1655188892.957999][2868:2873] CHIP:EM: Sending Standalone Ack for MessageCounter:133140817 on exchange 23176i

          2. when this attribute is false, do not need to verify rest of the below commands.
          3. When this attribute is true, the Node has been configured with one or more test event triggers by virtue of the internally programmed EnableKey value by the product vendor
          4. Use the manufacturer-provided EnableKey value and the EventTrigger value and send command using "./chip-tool generaldiagnostics test-event-trigger <EnableKey> <EventTrigger destination-id> " 1 0 and verify if the DUT generated the desired event.
      disabled: true