Hi Vincent, Still your -1 is based on the fact that <you> don't like to work that way.
> -1 for the same reasons already described. If you don't want tests, > don't write them or exclude them from a build. But it the tests are run > they must pass. I want tests, but sometimes they don't pass, but I still want to build everything (nice to have website feedback, or even build... eg) It could also be nice if this can be used in automated builds, where a build failed on the command line really doesn't give me feedback on what happened. You say, in indirect words, first write your code, then your tests, which is perfectly fine. Some people try to write tests first and then the code, which makes builds fail, if the code isn't finished yet. I am just reaching here to let you see that some people would like to have some flexibility on this behaviour, which isn't allowed at the moment, unless you change the default maven:test calls or change the plugin test build.xml . If you don't like the property : please think about (or explain me) a nice (workable) solution, without involving changing maven, copy and paste the do-test stuff from the plugin test build.xml or changing my test code (which isn't going to happen anyway, unless you were my dictator ;)) Just want an alternative.. Mvgr, Martin > > > I really don't want to start my own bracch, just because I miss this > one > > feature.. > > > > Mvgr, > > Martin > > > > On Thu, 2002-05-30 at 02:01, [EMAIL PROTECTED] wrote: > > > > > > Martin, > > > > > > personal preferences here: I'd rather not make it allowable to pass > the > > > build with a bad test. Seriously it's a motivation for either coding > the > > > tests right and having a stable product. > > > > > > If you want to see what the current behaviour of something is, when > I do > > > it, i simply write to system out what it is that I'm interested in > as > > part > > > of the test, rather than placing it in an assert statement. > > > -- > > > dIon Gillard, Multitask Consulting > > > Work: http://www.multitask.com.au > > > Developers: http://adslgateway.multitask.com.au/developers > > > > > > > > > > > > Martin van den > > > Bemt To: Turbine Maven > > Developers List > > > <[EMAIL PROTECTED] <turbine-maven- > > [EMAIL PROTECTED]> > > > et> cc: > > > Subject: Test behaviour > > > 05/30/02 01:00 > > > AM > > > Please respond > > > to "Turbine > > > Maven > > > Developers > > > List" > > > > > > > > > > > > > > > > > > > > > Hi everyone, > > > > > > The default test behaviour of maven is to fail the build, > > > Since I don't want that in some cases, since I am failing tests > > > intentionally (why?? : I am writing testcases for something I don't > > > know the intended behaviour of and the current behaviour strikes me > as > > > odd or buggy, I will write the test as I see fit, and ask someone > who > > > knows to get it the it's supposed to be -; hope you still with me..) > > > > > > For this to work I have attached a patch, which allows a property to > be > > > set in your favorit properties file. Default behaviour is still to > fail > > > the test though.. > > > > > > Have fun.. > > > > > > Mvgr, > > > Martin > > > > > > > > > (See attached file: dontfailontests.diff)-- > > > To unsubscribe, e-mail: < > > > mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: < > > > mailto:[EMAIL PROTECTED]> > > > > > > ---- > > > > > > > > -- > > > To unsubscribe, e-mail: <mailto:turbine-maven-dev- > > [EMAIL PROTECTED]> > > > For additional commands, e-mail: <mailto:turbine-maven-dev- > > [EMAIL PROTECTED]> > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:turbine-maven-dev- > > [EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:turbine-maven-dev- > > [EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
