ngax...@gmail.com <kangax...@gmail.com> on behalf of Haimo Liu
<haimoli...@gmail.com>
Sent: Thursday, July 13, 2017 2:07 PM
To: dev@nifi.apache.org
Subject: Re: MINIFI-350 minifi-cpp end-to-end integration testing framework
great idea Andy! I can see this being extremely valua
great idea Andy! I can see this being extremely valuable even outside of
the MINIFI cpp context. Specifically, to migrate my dataflow from one
environment to another (DEV to QA to PROD), an integration testing
framework could be very helpful for flow validation purposes.
in addition to testing
Thanks for the feedback. I will put together a proof of concept which we can
further evaluate/refine/merge upstream.
-Andy
On 7/13/17, 11:30 AM, "Kevin Doran" wrote:
Great idea, Andy! Additional types of automated tests would help the
minifi-cpp project
Great idea, Andy! Additional types of automated tests would help the minifi-cpp
project significantly, and I think your proposal is an appropriate way to add
integration tests for the minifi agent. This sounds like a great way to verify
expected behavior of processors and the system of
Yes, I envision having a directory of declarative test cases. Each would
include a flow yaml, one or more input files, and expected outputs.
I’d like to document the convention before writing the implementation because
if the conventions are solid, we can change out the actual test driver
Hi Andy,
I think this is a great idea to test integrating MiNiFi among multiple
system components. Do you have a feel for how you will allow others to
create test cases? Will you attempt to minimize the footprint of
contributed tests by creating a bats based framework? I ask because it
would be