You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/08/23 13:20:30 UTC

[jira] Created: (JCR-1081) bad test assumptions in org.apache.jackrabbit.test.api.lock

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
            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.


[jira] Updated: (JCR-1081) bad test assumptions in org.apache.jackrabbit.test.api.lock

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1081:
-------------------------------

    Affects Version/s: 1.2.1
                       1.2.2
                       1.2.3
                       1.3
                       1.3.1
        Fix Version/s: 1.3.2

Merged to the 1.3 branch in revision 577859.

> 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
>    Affects Versions: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.3.2
>
>
> 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.


[jira] Resolved: (JCR-1081) bad test assumptions in org.apache.jackrabbit.test.api.lock

Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Assigned: (JCR-1081) bad test assumptions in org.apache.jackrabbit.test.api.lock

Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke reassigned JCR-1081:
-----------------------------------

    Assignee: Julian Reschke

> 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.