[
https://issues.apache.org/jira/browse/SLING-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573354#comment-14573354
]
Petr Shypila edited comment on SLING-4541 at 6/4/15 8:51 PM:
-------------------------------------------------------------
Hello Robert and Bertrand,
Currently I'm trying to set up some new tests for ContentCreator. There are
already few implemented test cases. And the problem is that they are using
JMock framework. But as I know we prefer to use Mockito to mock objects.
So in which way should I go:
1. Set up new tests with JMock?
2. I could replace JMock with Mockito as well.
3. Or I could start use Sling Mocks as well, but it adds new dependencies to
our pom file(BTW [~rombert] I don't see these dependencies in pom.xml).
4. ?
-Petr
UPD: Could you probably also give me any advice in which way is better to
design tests for this module. As I see all these modules are very dependent on
JCR API. Nodes, Bundles, BundleHelpers etc. classes usage is almost everywhere.
was (Author: petr.shypila):
Hello Robert and Bertrand,
Currently I'm trying to set up some new tests for ContentCreator. There are
already few implemented test cases. And the problem is that they are using
JMock framework. But as I know we prefer to use Mockito to mock objects.
So in which way should I go:
1. Set up new tests with JMock?
2. I could replace JMock with Mockito as well.
3. Or I could start use Sling Mocks as well, but it adds new dependencies to
our pom file(BTW [~rombert] I don't see these dependencies in pom.xml).
4. ?
-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
>
>
> 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)
