Re: Big memory demanding tests problem

It is the Spring application context. I solved it now by using just one
static reference to one aplication context instead so now I guess I have
quite some time until I will run out of memery next time...

The principal problem still exists for JUnit though...

On 7/3/07, David Saff <[email protected]> wrote:
>
> (I accidentally dropped the thread from the list.  CC'ing the list to
> get them up to date.)
>
> My best guess is that the "fork" being discussed is the option on the
> junit task in ant.
>
> What are you allocating memory-wise for each test?  Thanks,
>
>    David
>
> On 7/3/07, Jonathan Alvarsson <[email protected]> wrote:
> > On 6/28/07, David Saff <[email protected]> wrote:
> > > Jonathan,
> > >
> > > Are you using JUnit 3?  If so, a move to JUnit 4 should help a lot.
> > > It will require a small amount of rewrite of the test code, but the
> > > memory usage profile should be much more reasonable.  Thanks,
> >
> > Okey so I changed some code into JUnit 4 compatible. But this didn't
> > change much. It's still the same. When I run all tests in my package
> > the test run turns really slow after just about half of the tests but
> > those tests run at normal speed if runned separately...
> >
> > Someone said somthing about fork. Do you know anything about that?
> >
> > // Jonathan
> >
>



-- 
// Jonathan

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

_______________________________________________
Junit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/junit-devel