[
https://issues.apache.org/jira/browse/CMIS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735263#action_12735263
]
Gabriele Columbro commented on CMIS-38:
---------------------------------------
Already at:
https://svn.alfresco.com/repos/contrib/chemistry-tck-atompub/
it's possible to run
mvn test -Pvendor
with a specific profile per vendor, so that the different compatibility levels
can be tested and maintained by the single vendor.
Also:
mvn test -Pvendor site:run
publishes the reports in the surefire-report of the mvn site (run on
localhost:8081 by default)
> Add a proper Maven Test lifecycle configuration (test and integration-test)
> to run TCK against different services
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CMIS-38
> URL: https://issues.apache.org/jira/browse/CMIS-38
> Project: Chemistry
> Issue Type: Improvement
> Components: tck
> Reporter: Gabriele Columbro
> Assignee: Gabriele Columbro
> Original Estimate: 16h
> Remaining Estimate: 16h
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
