[jira] [Updated] (STREAMS-537) Integration Tests should not assume presence of any specific system property values not controlled via SCM or maven lifecycle

["Steve Blackmon (JIRA)" <ji...@apache.org>]

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

Steve Blackmon updated STREAMS-537:
-----------------------------------
           Sprint: 0.5.1
    Fix Version/s: 0.5.1

> Integration Tests should not assume presence of any specific system property values not controlled via SCM or maven lifecycle
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: STREAMS-537
>                 URL: https://issues.apache.org/jira/browse/STREAMS-537
>             Project: Streams
>          Issue Type: Improvement
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>             Fix For: 0.5.1
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Currently to run integration tests requires a specific sort of typesafe file that is not checked into SCM in any form or managed by the maven lifecycle.  This is not ideal.  Each .conf file used in an integration test should source environment details and credentials from a few known location without relying on the tested to supply -DargLine=-Dconfig.file= when running maven.
> Provided project documentation regarding integration testing has been followed, mvn clean verify -DskipITs=false should work.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)