RE: [EXT] Re: Automated Testing of Flows

2017-11-17 Thread Chris Herrera
> approach if the API's are easily accessible. > https://github.com/apache/nifi/pull/2251 > > > > > -Original Message- > From: Scott Aslan [mailto:scottyas...@gmail.com] > Sent: Friday, November 17, 2017 12:39 > To: dev@nifi.apache.org > Subject: [EXT] Re: Auto

RE: [EXT] Re: Automated Testing of Flows

2017-11-16 Thread Peter Wicks (pwicks)
if the API's are easily accessible. https://github.com/apache/nifi/pull/2251 -Original Message- From: Scott Aslan [mailto:scottyas...@gmail.com] Sent: Friday, November 17, 2017 12:39 To: dev@nifi.apache.org Subject: [EXT] Re: Automated Testing of Flows Just brain storming here You

Re: Automated Testing of Flows

2017-11-16 Thread Scott Aslan
Just brain storming here You could use travis or Jenkins to setup a job where you use mvn and npm to build and start NiFi. Assuming the test template was available from within the environment maybe you could use the protractor e2e testing suite to script the clicks necessary to load the

Automated Testing of Flows

2017-11-15 Thread Peter Wicks (pwicks)
I would like to find a way to automatically run integration/upgrade tests on flows, rather than just one or two processors like the mock framework supports. Preferably something Template driven, where I can provide a template xml file, and an accompanying config file to setup the test, then run