You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2015/03/24 14:10:53 UTC

[jira] [Commented] (SLING-4541) Provide an extensive test suite for the JCR content loader

    [ https://issues.apache.org/jira/browse/SLING-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377815#comment-14377815 ] 

Tomek Rękawek commented on SLING-4541:
--------------------------------------

There are already two tests covering some parts of the content loader:

* [InitialContentTest|https://github.com/apache/sling/blob/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/InitialContentTest.java]
* [PostServletImportTest|https://github.com/apache/sling/blob/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/PostServletImportTest.java]

The first one checks if the Sling initial content is loaded correctly. The second imports different kind of content. Probably we'd need some low-level tests, testing the ContentImporter, ContentReader and maybe ContentCreator services.

> 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
>             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)