directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-137) Add system properties in tests kicked off by maven
Date Fri, 22 Jan 2016 14:56:39 GMT

    [ https://issues.apache.org/jira/browse/FC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112494#comment-15112494
] 

Shawn McKinney commented on FC-137:
-----------------------------------

This system property:

-Dtenant=whatever

when passed in on command line via mvn tests or loads will constraint the operations to that
particular tenant.  

This works for fortress xml data loads and the junit tests.  The old way of setting a context
tag in xml load file containing the tenant id is still supported as well.

> Add system properties in tests kicked off by maven
> --------------------------------------------------
>
>                 Key: FC-137
>                 URL: https://issues.apache.org/jira/browse/FC-137
>             Project: FORTRESS
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-RC40
>            Reporter: Shawn McKinney
>             Fix For: 1.0.0-RC41
>
>
> Pass system properties in though maven to enable features like multitenancy.
> For example:
> mvn test -Dtest=FortressJUnitTest -Dtenant=Client123
> Scope the unit tests to tenant Client123.
> Another setting works for fortress load utility.  By adding this to the xml input file:
>             <addcontext>
>                 <context name="${tenant}"/>
>             </addcontext>
> and this to build.properites:
> tenant=Client123
> The load will be scoped to Client123 tenant data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message