hmm, my fingers are bad. I meant, point test resource in your project.xml to the dummy one
On Tue, 10 Aug 2004 14:57:06 -0700, dan tran <[EMAIL PROTECTED]> wrote: > How about this! ;-) > > Create 2 test suites. One is a dummy one, and the other one has all > tests you want to run. > > Point test resource in your project.xml so that maven will invoke > after compilation. > it happens very fast since no test to run. > > Create a goal in your maven.xml to run your real test suite using test:single > goal. and run it any time you want > > > -D > > > > > On Tue, 10 Aug 2004 22:40:13 +0100, Charles Daniels <[EMAIL PROTECTED]> wrote: > > > > > > > -----Original Message----- > > > From: Jeffrey D. Brekke [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, August 10, 2004 8:37 PM > > > To: Maven Users List > > > Subject: Re: Use of maven.test.skip > > > > > > > > > > > > I recommend you forget that the flag exists and make the tests faster. > > > > That doesn't necessarily help. If all of his tests take 0.1 second on > > average, but he has 1000 tests, it still takes 100 seconds to run them all, > > which may still be unacceptably long to wait when running frequently. > > > > > > > > >>>>> On Tue, 10 Aug 2004 13:49:06 +0100, Kenny MacLeod > > > <[EMAIL PROTECTED]> said: > > > > > > > Folks, I currently have a project where the unit tests take a > > > > considerable amount of time to run (5 minutes or so), and as a > > > > result, running them every time I do a build is proving impractical. > > > > Initially, I just added the maven.test.skip flag to my > > > > project.properties, but this isn't a good solution, mainly because > > > > if I explicitly want to run the unit tests, I have to take the flag > > > > out again. > > > > > > > What I want is for the unit tests not to be run when i do a build, > > > > but I do want them to run if I explicitly say so. The interactions > > > > between the Java and Test plugins don't seem to be flexible enough > > > > to allow this. > > > > > > > My current solution is to move the unit tests out to a seperate > > > > project, but that seems like an arse-backwards way of going about > > > > it. Can anyone suggest a better approach? > > > > > > I think you may be onto something here. If they are so long, maybe > > > they aren't unit tests and should be moved. > > > > > > -- > > > ===================================================================== > > > Jeffrey D. Brekke [EMAIL PROTECTED] > > > Wisconsin, USA [EMAIL PROTECTED] > > > [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]
