Attached is an updated version of the JUnitTestTask.java - you should replace the current version of the source then from /tools/magic do the following:
$ ant clean update Next, set the following properties in a build.properties file under your project: project.test.compile.fork = true project.test.fork.mode = preTest The fork mode value can be set to one of 'once', 'perBatch' or 'perTest'. Running with a forked test results in a 'once' behavior and given that only once batch is created - the real change is when you switch to perTest fork mode. Steve. > -----Original Message----- > From: David Leangen [mailto:[EMAIL PROTECTED] > Sent: 04 October 2004 18:55 > To: Avalon framework users > Subject: RE: OutOfMemoryError when running unit tests > > > Stephen, Peter, > > Thank you for your awesome support, as always. > > It would be my pleasure to run the tests for you with the updated version. > In the meantime, I'm creating a memory profile as you suggested over IRC. > I > can show you the "before" and "after" versions. > > Thankfully, my test classes inherit from my own test class derived from > TestCase, so this is easy for me to do. > > > Regards, > Dave > > > > > > -----Original Message----- > > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > Sent: 5 October 2004 1:49 > > To: 'Avalon framework users'; [EMAIL PROTECTED] > > Subject: RE: OutOfMemoryError when running unit tests > > > > > > > > > > > -----Original Message----- > > > From: David Leangen [mailto:[EMAIL PROTECTED] > > > Sent: 04 October 2004 17:22 > > > To: Avalon framework users > > > Subject: RE: OutOfMemoryError when running unit tests > > > > > > > > > Hi, Peter, > > > > > > > Did yo do "svn update" to get the latest magic source? You MUST have > > the > > > > patch applied (see the dev list) since in the unpatched source, the > > for > > > > property is set too early and does not have any effect. > > > > > > Well, just to be sure, I just did a complete rebuild of avalon > > following, > > > of > > > course, an svn update. I know this is a bit overkill, but I figured it > > was > > > about time to do this anyway. Also, I am sure that the property > > > project.test.compile.fork is set to true. > > > > > > Unfortunately, though, this didn't solve the problem. I'm wondering > > what > > > I'm doing wrong now... > > > > Setting the "project.test.compile.fork" to "true" results in the unit > > tests be executed in a separate jvm, however, the JUnitTask includes > > support for the execution of a forked jvm per test (which is a much > > finer level of granularity). You mentioned on IRC that the tests are > > running in Eclipse but not under Magic - as such the only thing that > > seems to make sense is that Eclipse is forking per test. > > > > I'm going to add option to Magic's JUnit task and I'll be interested in > > feedback on the results of running with different fork modes. > > > > Cheers, Stephen. > > > > > > > > > > Any ideas? > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
