Re: Big memory demanding tests problem

On 7/3/07, David Saff <[email protected]> wrote:
>  Jonathan,
>
> I have not used Spring directly, so learning a bit more will probably
> help me in the future.  Are you directly shutting down the application
> contexts, or should that happen automatically at garbage collection?
> If you create a lot of application contexts in a loop, do you see
> similar results to what you saw for JUnit?

You really only use one. It's the big container keeping all the
objects. I have looked around a bit more and discovered that Spring
actually have alot of  classes made especially for JUnit 3 that helps
with these kind of things.

> JUnit 3 did indeed create all of the instance fields for all test
> objects at once, but this is intentionally fixed in JUnit 4.  Can you
> give me an example of how your tests look that would help me figure
> out whether JUnit can do something more to help your situation?

What I meant in claiming that the problem is not really solved was
based on this text:
<http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/>

>     David

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/