Yes, you are correct. Then the next question usually is "so which module do we attach the common test code to?", and it is probably an arbitrary decision, unless a "common" module already exists that the others use. So that has lead to creating the separate one in my experience.
-----Original Message----- From: Wim Deblauwe [mailto:[email protected]] Sent: Sunday, January 11, 2009 7:49 AM To: Maven Users List Subject: Re: where to place Test support/reusable fixture classes? You don't have to create a separate project if you don't want to. You can export the test classes in a separate jar with the 'test' classifier and depend on that jar. regards, Wim 2009/1/10 Jeff Jensen <[email protected]> > I suggest creating a separate project, e.g. "TestFramework", and place > those > types of reusable test classes in its src/main/java. Then, the other > projects can depend on it for the test scope. > > > -----Original Message----- > From: Giovanni Azua [mailto:[email protected]] > Sent: Friday, January 09, 2009 1:15 PM > To: 'Maven Users List' > Subject: where to place Test support/reusable fixture classes? > > Hi, > > I have a multi module project and in one of the top nodes of the dependency > tree I would like to place a Test support class i.e. > > AbstractHibernateHSQLTestCase extends junit.framework.TestCase > > This class provides automatic database shutdown of HSQL in memory based > test > cases to prevent the creation of the inconvenient test.lck and test.log > files. > > My problem is that I don't know where to place this utility class. Ideally > I > would place it in the test branch of module A but then it will not be > inherited by sub-modules that depend on A say B and C. On the other hand if > I place it under the java branch of module A, then A will compile/runtime > depend on JUnit which I want to avoid at all costs. > > I remember I had this same problem trying to define reusable test fixtures > classes but in the hurry I ended up duplicating the fixture classes under > each sub-module. > > TIA, > Regards, > Giovanni > > > > --------------------------------------------------------------------- > 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]
