sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Edelson (JIRA)" <>
Subject [jira] Commented: (SLING-1495) Make the Sling integration test cases available as a dependency
Date Wed, 02 Jun 2010 16:25:28 GMT


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.
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:
>             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
> 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.

View raw message