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] Updated: (GERONIMO-789) builder tests are ridiculously overcomplicated
Date Sat, 27 Aug 2005 23:30:05 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-789?page=all ]

Aaron Mulder updated GERONIMO-789:
----------------------------------

    Fix Version: 1.0

I've noticed myself that it's hard to set up test for certain issues for this reason.  Like,
fi you wanted to test what happens if an EAR is deployed with no geronimo-application.xml,
you'd have to create a test that constructs the bulk of a Geronimo server.  I'm not sure if
it would be easier to change the builder style or to reincarnate the geronimo-itest module
and actually have a running Geronimo that you can run tests against.

> builder tests are ridiculously overcomplicated
> ----------------------------------------------
>
>          Key: GERONIMO-789
>          URL: http://issues.apache.org/jira/browse/GERONIMO-789
>      Project: Geronimo
>         Type: Improvement
>   Components: deployment
>     Versions: 1.0-M4, 1.0-M5
>     Reporter: David Jencks
>      Fix For: 1.0

>
> Most of the builder tests jump through endless hoops setting up 99% of a running geronimo
implementation, only to check  the count of gbeans at the end.  Perhaps we could redesign
the builders so they can be tested by supplying a spec dd, a plan (XmlObjects) , and a classloader.

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