Re: [Engine-devel] Forking unit tests

From: "Allon Mureinik" <amureini(a)redhat.com&gt; To: "Mike Kolesnik" <mkolesni(a)redhat.com&gt; Sent: Thursday, June 14, 2012 12:12:54 PM Subject: Re: Forking unit tests ----- Original Message ----- > From: "Mike Kolesnik" <mkolesni(a)redhat.com&gt; > To: "Allon Mureinik" <amureini(a)redhat.com&gt; > Cc: "Laszlo Hornyak" <lhornyak(a)redhat.com&gt;, "engine-devel" > <engine-devel(a)ovirt.org&gt; > Sent: Wednesday, June 13, 2012 1:28:36 PM > Subject: Re: Forking unit tests > > > Hi guys, > > > > If you're using settings.xml as published in Building the oVirt > > Engine page, you'd see we're forking for every test, in every > > subproject. > > This behaviour was introduced to handle memory leaks in PowerMock > > we > > use in some subprojects, but is redundant in others. > > > > Over the past month or so I've been working on removing PowerMock > > from as many places as possible (many thanks to mkolesni and > > lhornyak!), and we've got to the stage that forking is only > > needed > > in to subprojects - bll and resttypes. > > +1 - great job! 10x! > > Would it be possible to have this as a parameter (defaul true) that > can be overridden, such as -Dengine.forkTests=false ? couldn't find a good way to do it <forkMode> doesn't seem to work when given a property as a value, sorry. :-(

> > > The forking was defined explicitly in those two projects, so if > > you > > want to speed up your tests, just take the latest version of > > settings.xml from > > http://ovirt.org/wiki/Building_oVirt_engine#Maven_personal_settings. > > > > > > -Allon > > >