-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
This library looks like a great way to automate testing a flow, but it looks like it requires Java code that is separate from the flows I build in the UI. If it were able to connect to NiFi Registry and automatically build a flow from there, then the test code could focus on creating inputs and evaluating outputs. To write tests for a full flow would likely require some mocking (for instance, for a relational database service that NiFi pulls data from). But even without that, I could picture focusing a test on a particular processor group. Send some flow files to the input port, see what comes out of the output port(s).
Is this in line with the direction you'd like this project to go?
Reference
- NiFi Registry API
- Endpoint to get the latest version of a flow: /buckets/{bucketId}/flows/{flowId}/versions/latestGet
katyprogrammer
Metadata
Metadata
Assignees
Labels
No labels