[CMIS-431] TCK expects PWC object to have cmis:isLatestVersion=true

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: OpenCMIS 0.5.0
• Fix Version/s: OpenCMIS 0.7.0
• Component/s: opencmis-tck
• Assignee: Florian Müller
• Reporter: jay brown
• Created: 15/Sep/11 16:28
• Updated: 15/Dec/17 07:49
• Resolved: 27/Apr/12 10:52

Description

First a bit of clarification on the spec so that we are all on the same page. In case I am making an incorrect assumption.

The spec treats PWC's as a separate class of objects from Versions. That is; a PWC is not the latest version until it is checked in. Before that it is not a version. (section 2.1.9.4.1 states "...Until it is checked in (using the checkIn service), the PWC MUST NOT be considered the LatestMajorVersion in the Version Series. )

So if I have a version series with 3 objects as follows
V1.0 - V2.0 - pwc
then the values of cmis:isLatestVersion should be as follows:
V1.0 (false) - V2.0 (true) - pwc (false)

If we are in agreement on this point (are we?) Then the TCK class ...tck.tests.versioning.CheckedOutTest (method - checkPWCs )
at line 73 causes a failure to be added if the pwc's isLatestVersion property is false.
addResult(assertIsTrue(pwc.isLatestVersion(), null, f));

This should be changed to assert that the pwc's value should == false.