[
https://issues.apache.org/jira/browse/SLING-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-3151.
----------------------------------------
Resolution: Fixed
Implemented in http://svn.apache.org/r1538994
An example test that uses this feature is RepositoryNameTest [1].
I also simplified the launchpad/testing pom setup: instead of using our own
class to collect the tests (which reduced them all to JUnit3 tests, losing the
categories), I'm now using the "dependenciesToScan" option of
maven-failsafe-plugin, which seems to work fine.
The run the tests with Oak, use -Dsling.run.modes=oak on the mvn command-line,
as before. No option needed to run the tests on Jackrabbit.
[1]
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/RepositoryNameTest.java
> Add Junit JackrabbitOnly and OakOnly JUnit test categories
> ----------------------------------------------------------
>
> Key: SLING-3151
> URL: https://issues.apache.org/jira/browse/SLING-3151
> Project: Sling
> Issue Type: Sub-task
> Components: Testing
> Reporter: Antonio Sanso
>
> It would be nice to have a Junit JackrabbitOnly category in order to
> differentiate those tests that makes sense to be executed only in Sling
> running on Jackrabbit (and do not makes sense to run for Sling on Oak)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
