chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jay brown (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CMIS-521) Empty non-required ID properties on documents are mistakenly flagged as a test failures
Date Thu, 05 Apr 2012 16:04:22 GMT


jay brown resolved CMIS-521.

    Resolution: Not A Problem

Problem was on vendor side. Not with TCK.  
> Empty non-required ID properties on documents are mistakenly flagged as a test failures
> ---------------------------------------------------------------------------------------
>                 Key: CMIS-521
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-tck
>    Affects Versions: OpenCMIS 0.7.0
>         Environment: n/a
>            Reporter: jay brown
>            Priority: Minor
>              Labels: test
>             Fix For: OpenCMIS 0.7.0
> I just noticed that we have failures when we run against our public P8 CMIS server
> (Ask Florian for url/creds/etc for our test server - he has them)
> Here is what is happening.    The class CMISScalars is a test class with a bunch of test
properties to exercise property persistence.
> CMISObject is a not-required prop of type ID. 
> When it is not set (as it is not usually set in our tests) is comes across in the XML
responses like this:
>   <cmis:propertyId queryName="CMISObject" displayName="CMISObject" localName="CMISObject"
> That is - empty, which is valid. 
> But the TCK test fails in several places when it encounters objects with this unset property
with this message:
>  FAILURE: PWC check: idd_FA946B30-018C-42C2-AE69-E4EDACCB894F (
>     FAILURE: Property CMISObject (
>       FAILURE: Property is not included in response! (
>         INFO: Object is null!
> AbstractSessionTest.checkProperty is getting called for this prop and it is dutifully
returning a failure since its null.  (at least that is what it looks like)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message