[
https://issues.apache.org/jira/browse/SLING-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Shypila updated SLING-4541:
--------------------------------
Attachment: week2-part3-single-jcrmock-test.patch
week2-part2-defaultcontentcreator.patch
week2-part1-pathentry.patch
I created new unit tests.
week2-part1-pathentry.patch - contains test for internal.PathEntry class.
week2-part2-defaultcontentcreator.patch - contains tests for
internal.DefaultContentCreator using JMock and updated reference to parent POM
file.
week2-part3-single-jcrmock-test.patch - contains a single test for
DefaultContentCreator#createNode method using JCR Mocks. I'm not sure that this
test make much sense. It requires new dependency and poorly tests only one
method. To cover createNode method better it looks like we still need to use
some mock framework.
Best regards,
Petr
> 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
>
> Attachments: week2-part1-pathentry.patch,
> week2-part2-defaultcontentcreator.patch, week2-part3-single-jcrmock-test.patch
>
>
> 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)
