jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@gmx.net>
Subject Re: TCK tests for optional predefined node types
Date Wed, 26 Jul 2006 08:30:39 GMT
Hi David,

Thank you for pointing out this issue. This is indeed a problem in the 
1.0 Version of the TCK and has already been addressed. The current 
(unreleased) version of the PredefinedNodeTypeTest does exactly what 
you suggest.

See: 
http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit/src/test/java/org/apache/jackrabbit/test/api/nodetype/PredefinedNodeTypeTest.java

A maintenance release of the TCK will be available as soon as the 
1.0.1 spec is final and released.

regards
  marcel

David Sanders wrote:
> The JSR-170 Final Release TCK tests fail for optional predefined node 
> types that a vendor may not support.
> For example, a test fails when nt:unstructured is not supported even 
> though the
> 1.0.1 spec says that node type is optional.   There are several other 
> optional node types that the TCK tests
> for, and whose nonexistence causes a test error.
> 
> junit.framework.AssertionFailedError: Node Type
> nt:unstructured not found
>     at junit.framework.Assert.fail(Assert.java:47)
>     at
> org.apache.jackrabbit.test.api.nodetype.PredefinedNodeTypeTest.testPredefinedNodeType

> 
> (PredefinedNodeTypeTest.java(Compiled
> Code))
>     at
> org.apache.jackrabbit.test.api.nodetype.PredefinedNodeTypeTest.testUnstructured(PredefinedNodeTypeTest.java:119)

> 
> 
> 
> Maybe, the TCK should interpret such test results similar to the way 
> unsupported features are handled (by throwing NotExecutableException).
> 
> 

Mime
View raw message