You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/02/15 20:09:28 UTC

[jira] Updated: (JCR-2493) Unit tests for persistence managers

     [ https://issues.apache.org/jira/browse/JCR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2493:
-------------------------------

    Attachment: JCR-2493.patch

Patch attached. It covers the modern pool/bundle PMs for Derby and H2 and also test the old-style persistence managers. Currently this adds only about 3% to the time it takes to run the jackrabbit-core test suite, so I'm thinking of simply including it in the default test run, but if people prefer we can also put it in a separate integration test profile.

> Unit tests for persistence managers
> -----------------------------------
>
>                 Key: JCR-2493
>                 URL: https://issues.apache.org/jira/browse/JCR-2493
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>         Attachments: JCR-2493.patch
>
>
> Currently we only test our persistence managers indirectly via JCR-level test cases. The downside of this approach is that we can only test one persistence manager implementation at a time, and need separate build profiles to switch from one implementation to another. To ensure better coverage and consistent behaviour across all our persistence managers I implemented a simple unit test that works directly against the PersistenceManager interface.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.