You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2017/03/31 17:12:41 UTC

[jira] [Assigned] (MINIFI-242) Automated integration tests with docker-compose

     [ https://issues.apache.org/jira/browse/MINIFI-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aldrin Piri reassigned MINIFI-242:
----------------------------------

    Assignee: Bryan Rosander

> Automated integration tests with docker-compose
> -----------------------------------------------
>
>                 Key: MINIFI-242
>                 URL: https://issues.apache.org/jira/browse/MINIFI-242
>             Project: Apache NiFi MiNiFi
>          Issue Type: Test
>            Reporter: Bryan Rosander
>            Assignee: Bryan Rosander
>             Fix For: 0.2.0
>
>
> Docker-compose has a lot of potential to make integration-level tests a lot easier and faster to perform.  As most people won't have Docker installed, these should only be run when the docker profile is active.
> Initial implementation can take v1 and v2 tests from https://github.com/brosander/minifi-testkit and modify them to run using the palantir docker-compose-rule-junit4 to allow for easy spin-up and down of minifi instances.
> This has value in ensuring that older templates can be transformed to the current version of the configuration schema.  It also tests that the config.yml files from old minifi toolkits still upconvert and run properly.
> From there it should be straightforward to use docker-compose files to model more complex configurations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)