[
https://issues.apache.org/jira/browse/SLING-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574610#comment-14574610
]
Bertrand Delacretaz commented on SLING-4541:
--------------------------------------------
It would also be nice to bring the relevant integration tests currently found
under {{launchpad/integration-tests}} closer to this module, ideally under
src/test with the IT.java suffix.
AFAICS those are:
ContentLoaderMiscPropertyTest which uses initial content set by
{{src/main/resources/SLING-INF/content/property-types-test.json}} from the
sibling {{test-services}} module. If needed, test bundles can be created on the
fly using https://ops4j1.jira.com/wiki/display/ops4j/Tinybundles, there's some
of examples of that in our codebase and many more in the Felix codebase.
Also PostServletImportTest as mentioned earlier in this ticket.
And maybe InitialContentTest but that looks more like an actual integration
test that makes sense against the full Sling launchpad.
Moving these tests is second priority, but would be nice if that's not too much
work, and maybe leave just a basic "content loader is present" test in the
launchpad. And maybe the other tests that Petr or Robert will create will cover
that already.
> Provide an extensive test suite for the JCR content loader
> ----------------------------------------------------------
>
> Key: SLING-4541
> URL: https://issues.apache.org/jira/browse/SLING-4541
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.10
> Reporter: Radu Cotescu
> Assignee: Petr Shypila
> Fix For: JCR ContentLoader 2.2.0
>
>
> The JCR content loader is a sensible bundle. An extensive IT suite should be
> written to make sure that code changes don't affect core functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
