[
https://issues.apache.org/jira/browse/SLING-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887380#comment-16887380
]
Oliver Lietz commented on SLING-4075:
-------------------------------------
You usually don't have to specify a version as the test just picks the current
build artifact as an additional bundle/option.
With the current approach there is a slight chance to not test the current
build artifact (it has to be installed and read from local Maven repo!).
To be back on the safe side you can reassemble the {{slingDistribution}}
option in the test and leave core bundle out or remove the core bundle easily
from {{slingDistribution}} via {{ModifiableCompositeOption}} (available since
PaxExam Testing 3.0).
Example
[ContentloaderTestSupport|https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/test/java/org/apache/sling/jcr/contentloader/it/ContentloaderTestSupport.java]:
{noformat}
[...]
final Option contentloader =
mavenBundle().groupId("org.apache.sling").artifactId("org.apache.sling.jcr.contentloader").version(SlingOptions.versionResolver.getVersion("org.apache.sling",
"org.apache.sling.jcr.contentloader"));
final ModifiableCompositeOption quickstart =
quickstart().remove(contentloader);
[...]
{noformat}
> Improve test coverage of SCD
> ----------------------------
>
> Key: SLING-4075
> URL: https://issues.apache.org/jira/browse/SLING-4075
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Reporter: Tommaso Teofili
> Assignee: Timothee Maret
> Priority: Major
>
> Currently we moved lots of testing to the IT module but it'd be good to have
> a better test coverage via unit testing in core module, at least to test
> basic use cases and maybe some edge cases.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
