[jira] [Resolved] (METAMODEL-45) Simplify and unify way integration tests are configured

["Kasper Sørensen (JIRA)" <ji...@apache.org>]

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

Kasper Sørensen resolved METAMODEL-45.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1

Now all should be good. Also JDBC integration tests are now configured through .properties file.

> Simplify and unify way integration tests are configured
> -------------------------------------------------------
>
>                 Key: METAMODEL-45
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-45
>             Project: Metamodel
>          Issue Type: Improvement
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>             Fix For: 4.1
>
>         Attachments: METAMODEL45-Initial-changes-of-HBase.patch
>
>
> We have a number of integration tests that are all configured in various ways. Common for them is that they only run if some configuration is available externally or if some server is responding.
> Off the top of my head, here are the variations:
>  * In the JDBC module there's a separate source folder for integration tests to MySQL, Oracle, DB2, PostgreSQL.
>  * HBase module currently has an integration test that ALWAYS runs, which will cause big pains for people doing a casual build.
>  * Salesforce and SugarCRM modules both read from a file in user home (but not the same file of course, that would be too elegant :-))
>  * MongoDB and CouchDB modules simply try to connect to localhost, and if they fail, the unittest is skipped.
> So I propose we consolidate the integration test configuration. Let's have a single .properties file and let all modules read from this to figure out if certain tests should be run, and with which configuration properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)