docker/test/integration/features/fetch_modbus_tcp.feature

# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You 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.

@x86_x64_only
@CORE
Feature: Minifi C++ can act as a modbus tcp master

  Background:
    Given the content of "/tmp/output" is monitored

  Scenario: MiNiFi can fetch data from a modbus slave
    Given a FetchModbusTcp processor
    And a JsonRecordSetWriter controller service is set up with "One Line Per Object" output grouping
    And a PutFile processor with the "Directory" property set to "/tmp/output"
    And the "Unit Identifier" property of the FetchModbusTcp processor is set to "255"
    And the "Record Set Writer" property of the FetchModbusTcp processor is set to "JsonRecordSetWriter"
    And there is an accessible PLC with modbus enabled
    And PLC register has been set with h@52=123 command
    And PLC register has been set with h@5678/f=1.75 command
    And PLC register has been set with h@4444=77 command
    And PLC register has been set with h@4445=105 command
    And PLC register has been set with h@4446=78 command
    And PLC register has been set with h@4447=105 command
    And PLC register has been set with h@4448=70 command
    And PLC register has been set with h@4449=105 command

    And the "success" relationship of the FetchModbusTcp processor is connected to the PutFile
    And the "foo" property of the FetchModbusTcp processor is set to "holding-register:52"
    And the "bar" property of the FetchModbusTcp processor is set to "405678:REAL"
    And the "baz" property of the FetchModbusTcp processor is set to "4x4444:CHAR[6]"

    When both instances start up
    Then a flowfile with the JSON content "{"foo":123,"bar":1.75,"baz":["M", "i", "N", "i", "F", "i"]}" is placed in the monitored directory in less than 10 seconds