jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1081) bad test assumptions in org.apache.jackrabbit.test.api.lock
Date Thu, 23 Aug 2007 11:52:31 GMT

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

Julian Reschke resolved JCR-1081.
---------------------------------

    Resolution: Fixed

Fixed with revision 568942.


> bad test assumptions in org.apache.jackrabbit.test.api.lock
> -----------------------------------------------------------
>
>                 Key: JCR-1081
>                 URL: https://issues.apache.org/jira/browse/JCR-1081
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: JCR TCK
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>
> These tests make a lot of assumptions that may not be true for a compliant repository,
such as:
> - ability to add nodes without specifiying the node type
> - assumption that ordering and same name siblings are supported
> - assumption that addMixin(lockable) is required on newly added nodes
> Furthermore, some repositories may not support shallow locks on leaf nodes. That's not
compliant, but failure to do so should not abort a test that tests something else.

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


Mime
View raw message