martinzink commented on code in PR #2044:
URL: https://github.com/apache/nifi-minifi-cpp/pull/2044#discussion_r2469159630


##########
extensions/standard-processors/tests/features/attributes_to_json.feature:
##########
@@ -15,17 +15,16 @@
 
 @CORE
 Feature: Writing attribute data using AttributesToJSON processor
-  Background:
-    Given the content of "/tmp/output" is monitored
 
   Scenario: Write selected attribute data to file
     Given a GetFile processor with the "Input Directory" property set to 
"/tmp/input"
-    And a file with filename "test_file.log" and content "test_data" is 
present in "/tmp/input"
+    And a directory at "/tmp/input" has a file ("test_file.log") with the 
content "test_data"
     And a AttributesToJSON processor with the "Attributes List" property set 
to "filename,invalid"
     And the "Destination" property of the AttributesToJSON processor is set to 
"flowfile-content"
     And the "Null Value" property of the AttributesToJSON processor is set to 
"true"
     And a PutFile processor with the "Directory" property set to "/tmp/output"
     And the "success" relationship of the GetFile processor is connected to 
the AttributesToJSON
     And the "success" relationship of the AttributesToJSON processor is 
connected to the PutFile
+    And PutFile's success relationship is auto-terminated
     When the MiNiFi instance starts up
-    Then a flowfile with the JSON content 
"{"filename":"test_file.log","invalid":null}" is placed in the monitored 
directory in less than 10 seconds
+    Then there is a single file with 
"{"invalid":null,"filename":"test_file.log"}" content in the "/tmp/output" 
directory in less than 20 seconds

Review Comment:
   good idea, 
https://github.com/apache/nifi-minifi-cpp/commit/6f9dc2cecae94a8c5d4c86b089c60aa3f5c1484e



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to