[GitHub] [nifi-minifi-cpp] lordgamez commented on a change in pull request #1216: MINIFICPP-1290 Create test coverage for OPC processors

[GitBox <gi...@apache.org>]

lordgamez commented on a change in pull request #1216:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1216#discussion_r760884568



##########
File path: docker/test/integration/features/opcua.feature
##########
@@ -0,0 +1,153 @@
+Feature: Putting and fetching data to OPC UA server
+  In order to send and fetch data from an OPC UA server
+  As a user of MiNiFi
+  I need to have PutOPCProcessor and FetchOPCProcessor
+
+  Background:
+    Given the content of "/tmp/output" is monitored
+
+  Scenario Outline: Create and fetch data from an OPC UA node
+    Given a GetFile processor with the "Input Directory" property set to "/tmp/input" in the "create-opc-ua-node" flow
+    And a file with the content "<Value>" is present in "/tmp/input"
+    And a PutOPCProcessor processor in the "create-opc-ua-node" flow
+    And a FetchOPCProcessor processor in the "fetch-opc-ua-node" flow
+    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "fetch-opc-ua-node" flow
+    And these processor properties are set:
+      | processor name    | property name               | property value                  |
+      | PutOPCProcessor   | Parent node ID              | 85                              |
+      | PutOPCProcessor   | Parent node ID type         | Int                             |
+      | PutOPCProcessor   | Target node ID              | 9999                            |
+      | PutOPCProcessor   | Target node ID type         | Int                             |
+      | PutOPCProcessor   | Target node namespace index | 1                               |
+      | PutOPCProcessor   | Value type                  | <Value Type>                    |
+      | PutOPCProcessor   | OPC server endpoint         | opc.tcp://opcua-server:4840/    |
+      | PutOPCProcessor   | Target node browse name     | testnodename                    |
+      | FetchOPCProcessor | Node ID                     | 9999                            |
+      | FetchOPCProcessor | Node ID type                | Int                             |
+      | FetchOPCProcessor | Namespace index             | 1                               |
+      | FetchOPCProcessor | OPC server endpoint         | opc.tcp://opcua-server:4840/    |
+      | FetchOPCProcessor | Max depth                   | 1                               |
+
+    And the "success" relationship of the GetFile processor is connected to the PutOPCProcessor
+    And the "success" relationship of the FetchOPCProcessor processor is connected to the PutFile
+
+    And an OPC UA server is set up
+
+    When all instances start up
+    Then at least one flowfile with the content "<Value>" is placed in the monitored directory in less than 60 seconds
+
+  Examples: Topic names and formats to test
+    | Value Type   | Value   |
+    | String       | Test    |
+    | UInt32       | 42      |
+    | Double       | 123.321 |
+    | Boolean      | False   |
+
+  Scenario Outline: Update and fetch data from an OPC UA node

Review comment:
       Yes, the test server application which is started from the container image already defines a list of demo values for each node type of OPC UA.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org