Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <32696223.1154535314756.JavaMail.jira@brutus>
Date: Wed, 2 Aug 2006 09:15:14 -0700 (PDT)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-511) TCK: Node types selected by
 SetValueValueFormatExceptionTest may lead to incorrect test failure
In-Reply-To: <2448191.1153957093911.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-511?page=all ]

Marcel Reutegger resolved JCR-511.
----------------------------------

    Fix Version/s: 1.1
       Resolution: Fixed

I re-wrote major parts of the test cases in SetValueValueFormatExceptionTest. All test cases are now configurable wrt node types and property names that should be used for the test.

Fixed in svn revision: 428041

Thank you for reporting this issue.

> TCK: Node types selected by SetValueValueFormatExceptionTest may lead to incorrect test failure
> -----------------------------------------------------------------------------------------------
>
>                 Key: JCR-511
>                 URL: http://issues.apache.org/jira/browse/JCR-511
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: test
>            Reporter: David Pitfield
>             Fix For: 1.1
>
>
> During setup, the test selects two node types, one with a BOOLEAN property and one with a DATE property, and creates nodes of these types as children of the target node.  Having the TCK select these node types creates two problems:  First, JSR-170 does not require an implementation to provide deterministic, stable ordering of node types returned by NodeTypeManager.  Consequently, the node types selected during test setup may vary from run to run, making test configuration difficult or impossible.  Second, if a repository imposes implementation-specific type constraints not discoverable through JSR-170, the TCK may select a node type inappropriate as a child of the test node.
> Proposal: introduce configuration properties which, if set, override the property definition and node type selected by NodeTypeUtil.

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