jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-540) AbstractJCRTest fails on level 1 repositories
Date Fri, 11 Aug 2006 08:18:17 GMT
    [ http://issues.apache.org/jira/browse/JCR-540?page=comments#action_12427467 ] 
Marcel Reutegger commented on JCR-540:

> I'd still like to see an easy way to find out whether a repository supports L1 completely.

Yes, there is the official TCK, which comes with a test harness that executes the various
test cases grouped in the specified compliance levels and optional features. There you can
easily see which level 1 tests failed.


Please note that the currently available TCK is based on the test cases present in the jackrabbit
branch ri-1.0. While you are the test cases from jackrabbit trunk, which will eventually go
into a maintenance release of the TCK at some time.

> AbstractJCRTest fails on level 1 repositories
> ---------------------------------------------
>                 Key: JCR-540
>                 URL: http://issues.apache.org/jira/browse/JCR-540
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: JCR TCK
>            Reporter: Julian Reschke
>            Priority: Minor
>         Attachments: JCR-540-svn430367.patch, JCR-540.diff.txt, JCR-540.diff.txt
> If a test case indicates that it's not read-only, org.apache.jackrabbit.test.AbstractJCRTest
tries to cleanup the test root in the setUp method. This will cause the test case to fail,
because a Level 1 repository will throw an UnsupportedOperationException here.
> Proposal: before trying the cleanup, check for L2 functionality and throw a NotExecutableException
>             if (! isSupported(Repository.LEVEL_2_SUPPORTED)) {
>               cleanUp();
>               String msg = "Test case requires level 2 functionality";
>               throw new NotExecutableException(msg);
>             }

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message