You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/04/21 18:11:49 UTC
[jira] Updated: (SLING-1495) Make the Sling integration test cases
available as a dependency
[ https://issues.apache.org/jira/browse/SLING-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated SLING-1495:
---------------------------------
Attachment: 0001-SLING-1495-Make-the-Sling-integration-test-cases-av.patch
See the attached patch for a first shot at doing this. The patch adds an assembly for the test classes and resources in org.apache.sling.launchpad.testing.
A better approach would be to split the test classes to a separate component that org.apache.sling.launchpad.testing could then depend on.
> 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
> 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.