chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Caruana (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CMIS-38) Add a proper Maven Test lifecycle configuration (test and integration-test) to run TCK against different services
Date Tue, 18 Aug 2009 14:35:14 GMT

     [ https://issues.apache.org/jira/browse/CMIS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Caruana resolved CMIS-38.
-------------------------------

    Resolution: Fixed

> 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.


Mime
View raw message