[
https://issues.apache.org/jira/browse/NIFIREG-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219049#comment-16219049
]
ASF GitHub Bot commented on NIFIREG-44:
---------------------------------------
GitHub user kevdoran opened a pull request:
https://github.com/apache/nifi-registry/pull/28
NIFIREG-44 Refactor integration test framework and add secure tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevdoran/nifi-registry NIFIREG-44-it-refactor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/28.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #28
----
commit 6ca1856b49edd821426fb71485035bfa6fceaebf
Author: Kevin Doran <[email protected]>
Date: 2017-10-25T00:42:36Z
Refactor integration test framework to sandbox configuration classes in
Spring profiles.
----
> Add integration tests for secure NiFi Registry
> ----------------------------------------------
>
> Key: NIFIREG-44
> URL: https://issues.apache.org/jira/browse/NIFIREG-44
> Project: NiFi Registry
> Issue Type: Test
> Reporter: Kevin Doran
> Assignee: Kevin Doran
>
> Currently, the automated integration tests on master only run an unsecured
> NiFi Registry instance.
> This task is to add test suites that setup a secure connection between the
> client and the Registry.
> This will require a refactoring in order to prevent secure and non-secure
> configuration beans from ending up in the same application context. Instead
> of the \@RunWith and \@SpringBootTest annotations on the IntegrationBaseTest
> class, they will need to be moved to subclasses and configuration needs to by
> explicitly imported or limited to a profile active for that test suite.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
