> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: jeudi 4 novembre 2004 18:47 > To: 'Cactus Developers List' > Subject: RE: Maven test case namings > > > > > -----Original Message----- > > From: Felipe Leme [mailto:[EMAIL PROTECTED] > > Sent: jeudi 4 novembre 2004 19:29 > > To: [EMAIL PROTECTED] > > Subject: Re: Maven test case namings > > > > On Thu, 4 Nov 2004 16:55:02 +0100, "Vincent Massol" > <[EMAIL PROTECTED]> > > wrote: > > > > > I don't like too much the test case names (test*) as they don't > > represent > > > anything. Couldn't we replace them with what they are doing? For > example > > > instead of test06, I would prefer testIncludeResourcesInCactifiedWar. > > What > > > do you think? > > > > I'm fine with that - I just followed the pattern used in another maven > > plugins. Anyway, another think that we could improve is cleaning up the > > target directory after the test. > > Why would cleaning after the test be an improvement? I always prefer to > delete *before* the test in order to ensure test result consistency. But > deleting after the test is not good I think because then if the test > fails, > you cannot check the build result... :-)
I've just realized that you're going to say that clean should be last step so that if the test fails it would not clean... :-) That's true but I still feel not comfortable not keeping the build result should they be needed. I often go back to check build results long after the last build to check things. I'm not completely against cleaning after the build but I don't see any real advantage. Is there any? [snip] -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
