[
https://issues.apache.org/jira/browse/OAK-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved OAK-53.
------------------------------
Resolution: Fixed
Fix Version/s: 0.2
Assignee: Jukka Zitting
I took the liberty of replacing the smoke-test profile with an
integrationTesting profile that works in the opposite way. Instead of disabling
long-running tests, the integrationTesting profile explicitly enables the tests
that are now by default disabled.
Ideally running a unit test in the default "mvn clean install" build shouldn't
take much longer than compiling the relevant classes. Any longer-running tests
should only be executed when the integrationTesting profile is enabled (which
should be the case in automatic CI builds).
To mark a test as time-consuming or otherwise a part of the integration test
suite, name it SomethingIT (as in "integration test") instead of SomethingTest.
See the Maven Failsafe plugin documentation for more details.
> exclude longer running tests in the default maven profile
> ---------------------------------------------------------
>
> Key: OAK-53
> URL: https://issues.apache.org/jira/browse/OAK-53
> Project: Jackrabbit Oak
> Issue Type: Test
> Reporter: Stefan Guggisberg
> Assignee: Jukka Zitting
> Fix For: 0.2
>
>
> the current maven build using the default profile takes ~3min on my machine
> which is IMO way too long.
> 'mvn clean install' should IMO allow quick turn around cycles during
> development and finish within a couple of seconds.
> requiring the developers to use a custom maven profile dring development (as
> suggested in OAK-52) is IMO not acceptable. custom profiles are hard to
> remember when working on different projects.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
