geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1860) Tests of optional ConfigID components
Date Tue, 25 Apr 2006 17:30:07 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1860?page=comments#action_12376300 ] 

Aaron Mulder commented on GERONIMO-1860:
----------------------------------------

I was just thinking...  We're going to need a number of simple sample apps for this.  I think
we should check them all in (perhaps to the sandbox) and maybe set up batch / shell scripts
to run the deployments and check for errors.  It can be a manual process for now (start server,
kick off script, stop server) and maybe someone can make an itest-like module out of it later.
 But it would be nice to build up a supply of simple test apps for this purpose.

> Tests of optional ConfigID components
> -------------------------------------
>
>          Key: GERONIMO-1860
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1860
>      Project: Geronimo
>         Type: Test
>     Security: public(Regular issues) 
>   Components: general
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Paul McMahan
>     Priority: Blocker
>      Fix For: 1.1

>
> Before shipping 1.1, we need to make sure the following things work:
>  - deploy a web app with no Geronimo plan
>  - redeploy the same web app with no Geronimo plan
>  - deploy a module with a Geronimo plan with an environment with no configId
>  - redeploy the same module with a Geronimo plan with an environment with no configId
>  - deploy a module with a Geronimo plan with no type in the configId
>  - redeploy the same module with a Geronimo plan with no type in the configId
>  - deploy a module with a Geronimo plan with no version in the configId
>  - redeploy the same module with a Geronimo plan with no version in the configId
>  - deploy a module with a Geronimo plan with no type or version in the configId
>  - redeploy the same module with a Geronimo plan with no type or version in the configId
>  - deploy a module with a Geronimo plan with only an artifactId in the configId
>  - redeploy the same module with a Geronimo plan with only an artifactId in the configId
>  - deploy a module with a JAR dependency where only the artifactId is specified
>  - deploy a module with a JAR dependency where only the artifactId and groupId are specified
>  - deploy a module with a JAR dependency where the type is not specified
>  - deploy a module with a JAR dependency where the version is not specified
>  - deploy a module with a configuration dependency where only the artifactId is specified
>  - deploy a module with a configuration dependency where only the artifactId and groupId
are specified
>  - deploy a module with a configuration dependency where the type is not specified
>  - deploy a module with a configuration dependency where the version is not specified

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message