[
https://issues.apache.org/jira/browse/SLING-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874644#action_12874644
]
Justin Edelson commented on SLING-1495:
---------------------------------------
> How much disruption would it represent to people to split out the test
> classes ?
Ideally, none :)
> Its just as easy to do as to apply the patch, I am happy either way.
I'm not sure about this. AFAIK, the way surefire detects classes to run is by
scanning the test source directory. This directory (in launchpad.testing) will
be empty. What has to be done is the creation of some test suites in the new
tests project and then a trivial invocation of this from the testing module.
This is basically what Jackrabbit does.
http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-spi2dav/src/test/java/org/apache/jackrabbit/test/TestAll.java
references tests on the classpath. But without this suite, the tests wouldn't
be invoked.
> Make the Sling integration test cases available as a dependency
> ---------------------------------------------------------------
>
> Key: SLING-1495
> URL: https://issues.apache.org/jira/browse/SLING-1495
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Jukka Zitting
> Assignee: Ian Boston
> Priority: Minor
> Attachments:
> 0001-SLING-1495-Make-the-Sling-integration-test-cases-av.patch
>
>
> Currently the integration tests in launchpad/testing are designed so that
> you'll need to manually run that Maven build with specific options if you
> want to test an external Sling instance.
> It would be great if a downstream project could instead import those test
> cases as a test dependency to their own integration test suite.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
