[CMIS-38] Add a proper Maven Test lifecycle configuration (test and integration-test) to run TCK against different services

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.1.0-incubating
• Component/s: tck
• Assignee: Gabriele Columbro
• Reporter: Gabriele Columbro
• Due: 31/Jul/09
• Created: 15/Jul/09 17:29
• Updated: 02/May/13 02:29
• Resolved: 18/Aug/09 14:33

Description

It would be nice, once the TCK is completed, to run CMIS compatibility tests directly in the build process of the tck module (with specifc profiles) against different platforms:

• Surefire will run TCK Unit Tests (for Frameworks who want to Test CMIS compatibility in process) in the 'test' phase
• Surefire will run TCU Integration Tests (for Frameworks who want to Test CMIS compatibility providing a remote service) in the 'integration-test' phase

Every platform that support CMIS (mostly everyone has a committer) can maintain the specific Maven profile that configures Surefire to run tests against its own platform.

I can try to set this up in quite short time, as soon as the base TCK code is committed.

Issue Links

• depends upon: CMIS-25 Contribute Alfresco AtomPub client test suite to form starting point TCK
• is depended upon by: CMIS-39 Arrange shapshots deploy to http://incubator.apache.org/chemistry/