jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriele Columbro (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCRCMIS-5) [WS] Setup integration testing framework at build time
Date Tue, 23 Dec 2008 13:55:44 GMT

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

Gabriele Columbro updated JCRCMIS-5:
------------------------------------

    Description: 
For the AtomPub component a programmatic Jetty server creation approach was used (still hanging
ATM).

Another way (generically used by maven projects) is to startup jetty embedded server in maven
and run integration testing from there.

We'll test this approach for the WS server component and then investigate if the approach
can be reused/shared also with the AtomPub component ( by moving to the server/pom.xml)

This task comprises:

- Find a mean to separate unit from integration tests (e.g. add integration tests  in a specific
package, e.g. org.apache.jackrabbit.*.integration*) 
- Configure surefire to skip integration tests in the 'test' phase (see here http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing)
- Configure maven-jetty-plugin to be started up in the 'pre-integration-test' phase
- have  jackrabbit.war with the jcr-cmis-ws extension deployed in jetty
- Have surefire run all integration tests in the 'integration-test' phase against the running
server (using some cxf ws-client support)
- Configure jetty to be stopped just after that in the 'post-integration-test' phase

  was:
For the AtomPub component a programmatic Jetty server creation approach was used (still hanging
ATM).

Another way (generically used by maven projects) is to startup jetty embedded server in maven
and run integration testing from there.

We'll test this approach for the WS server component and then investigate if the approach
can be reused/shared also with the AtomPub component ( by moving to the server/pom.xml)

This task comprises:

- Find a mean to separate unit from integration tests (e.g. add integration tests  in a specific
package, e.g. org.apache.jackrabbit.*.integration*) 
- Configure surefire to skip integration tests in the 'test' phase (see here http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing)
- Configure maven-jetty-plugin to be started up in the 'pre-integration-test' phase and deploy
the jackrabbit.war with the jcr-cmis-ws extension
- Have surefire run all integration tests in the 'integration-test' phase against the running
server (using some cxf ws-client support)
- Configure jetty to be stopped just after that in the 'post-integration-test' phase


> [WS] Setup integration testing framework at build time
> ------------------------------------------------------
>
>                 Key: JCRCMIS-5
>                 URL: https://issues.apache.org/jira/browse/JCRCMIS-5
>             Project: Jackrabbit CMIS Sandbox
>          Issue Type: Task
>            Reporter: Gabriele Columbro
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> For the AtomPub component a programmatic Jetty server creation approach was used (still
hanging ATM).
> Another way (generically used by maven projects) is to startup jetty embedded server
in maven and run integration testing from there.
> We'll test this approach for the WS server component and then investigate if the approach
can be reused/shared also with the AtomPub component ( by moving to the server/pom.xml)
> This task comprises:
> - Find a mean to separate unit from integration tests (e.g. add integration tests  in
a specific package, e.g. org.apache.jackrabbit.*.integration*) 
> - Configure surefire to skip integration tests in the 'test' phase (see here http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing)
> - Configure maven-jetty-plugin to be started up in the 'pre-integration-test' phase
> - have  jackrabbit.war with the jcr-cmis-ws extension deployed in jetty
> - Have surefire run all integration tests in the 'integration-test' phase against the
running server (using some cxf ws-client support)
> - Configure jetty to be stopped just after that in the 'post-integration-test' phase

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