[
https://issues.apache.org/jira/browse/SLING-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874759#action_12874759
]
Ian Boston commented on SLING-1495:
-----------------------------------
Here is a patch that moves all the test classes out.
http://codereview.appspot.com/1425042
Unfortunately codereview cant really cope with the patch set (too big) so here
are the bits that matter, and the App Engine its on appears to be struggling.
All classes and resources moved from testing to a new project integration-tests
http://codereview.appspot.com/1425042/patch/1/67003 (testing/pom.xml)
http://codereview.appspot.com/1425042/patch/1/55006 ( a new TestAll class)
http://codereview.appspot.com/1425042/patch/1/4001 (a new
integration-tests/pom.xml)
It uses a TestSuite that scans the classpath with the same pattern as used by
the Surefire plugin. It has to use a non manifest only jar to make the
classpath visible to the test suite when it starts up.
At the moment there are 2 things to do.
1. Check that the pattern used to select the classes gets correctly converted
into a regex for the scan (from the command line)
2. Fix the integration tests that were assuming a location of files on the file
system, rather than files from the classpath. (about 4)
One other impact of this change. All the test cases happen in a single Suite,
so it all logs to a single file. I dont know if thats desirable, but I have
found it easier to locate failing tests in use.
I will fix the other problems,
If anyone can see a reason not to do this please shout. (thanks)
> 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.
