Hmm yes, but Torsten said that was exactly what he wanted to avoid. In addition to naming conventions for unit & integration tests, we use a separate module for our heavier, end-to-end functional tests.
Kalle On Thu, May 29, 2008 at 10:06 AM, Paul Davis <[EMAIL PROTECTED]> wrote: > Another option is to place the integration tests into a separate module. > > On Thu, May 29, 2008 at 8:12 AM, Kalle Korhonen < > [EMAIL PROTECTED]> > wrote: > > > Standard answer is with naming convention, see > > http://www.mail-archive.com/users@maven.apache.org/msg81355.html. > > > > Kalle > > > > On Thu, May 29, 2008 at 7:54 AM, <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > Actually, we have mixed JUnit Testcases in our modules - some of them > can > > > be run "standalone" with no database connection or any other > environment, > > > others need environment. > > > > > > I now want to separate those tests into different categories, but I > don´t > > > want to > > > - manually create a DatabaseTestSuite where I need to add all > > > database-testcases > > > - create a new Maven Module to separate the testcases > > > > > > Can I use JUnit 4.x with its annotations like @RunWith @Ignore and so > on > > > to do so ? > > > > > > For example the "simple testcases" should be bound to the "test" phase, > > > the "database-testcases" should be bound to the "integration-test" > phase. > > > > > > Any ideas, links, cookbooks? > > > > > > Thanx, Torsten > > > > > > > > >
