Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2004-09-28 14:25:37
|
That's true: We have "*Tests" and "*TestSuite", sort of mixed. = All-embracing tests are often called "*TestSuite", while specific ones = are usually called "*Tests". That's not really a strict rule, though: = The choice is often arbitrary. I've thought about unifying those names myself repeatedly. I'd vote for = "*Tests", as we're already using that for most tests anyway. This would = simply mean renaming all "*TestSuite" classes to "*Tests". Can we do = that efficiently, in a batch maybe? Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Dmitriy Kopylenko Sent: Tuesday, September 28, 2004 3:13 PM To: spr...@li... Subject: [Springframework-developer] Naming convention for JUnint test classes Juergen, everybody, I've noticed a long time ago that some of our test classes are named as=20 xxxTestSuite and some are named as xxxTests. I'd like to see a=20 consistent naming pattern throughout the code base. So, what would be=20 the consistent naming convention for test classes? Thoughts? Regards, Dmitriy. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Oliver H. <Ol...@ou...> - 2004-10-13 22:48:34
|
> -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Olivier Jolly > > I'd vote for xxxTest, without presuming if it contains one or more=20 > tests. If I'm not mistaken, that's the standard enforced by Eclipse=20 > plugin for instance. Eclipse doesn't care what you name your tests. It simply looks for classes that extend TestCase. Ollie |
|
From: Colin S. <col...@ex...> - 2004-09-28 15:57:41
|
If we actually set about renaming tests, I suggest we just go to *Test. It's basically the defacto standard for junit TestCase naming, and a number of tools and the like default to that. Not to mention that people have that baked into their heads. Almost any time I've created a Spring test I've accidentally created it as *Test, and then had to rename it. The tests would lose the CVS history, but for test cases I don't think that's a big deal... Colin jürgen höller [werk3AT] wrote: >That's true: We have "*Tests" and "*TestSuite", sort of mixed. All-embracing tests are often called "*TestSuite", while specific ones are usually called "*Tests". That's not really a strict rule, though: The choice is often arbitrary. > >I've thought about unifying those names myself repeatedly. I'd vote for "*Tests", as we're already using that for most tests anyway. This would simply mean renaming all "*TestSuite" classes to "*Tests". Can we do that efficiently, in a batch maybe? > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf >Of Dmitriy Kopylenko >Sent: Tuesday, September 28, 2004 3:13 PM >To: spr...@li... >Subject: [Springframework-developer] Naming convention for JUnint test >classes > > >Juergen, everybody, > >I've noticed a long time ago that some of our test classes are named as >xxxTestSuite and some are named as xxxTests. I'd like to see a >consistent naming pattern throughout the code base. So, what would be >the consistent naming convention for test classes? > >Thoughts? > >Regards, >Dmitriy. > > |
|
From: Dmitriy K. <dko...@ru...> - 2004-09-28 15:08:26
|
I lean towards "*Tests" myself (and that's how we name it here at work). +1 for "*Tests" Dmitriy. jürgen höller [werk3AT] wrote: >That's true: We have "*Tests" and "*TestSuite", sort of mixed. All-embracing tests are often called "*TestSuite", while specific ones are usually called "*Tests". That's not really a strict rule, though: The choice is often arbitrary. > >I've thought about unifying those names myself repeatedly. I'd vote for "*Tests", as we're already using that for most tests anyway. This would simply mean renaming all "*TestSuite" classes to "*Tests". Can we do that efficiently, in a batch maybe? > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf >Of Dmitriy Kopylenko >Sent: Tuesday, September 28, 2004 3:13 PM >To: spr...@li... >Subject: [Springframework-developer] Naming convention for JUnint test >classes > > >Juergen, everybody, > >I've noticed a long time ago that some of our test classes are named as >xxxTestSuite and some are named as xxxTests. I'd like to see a >consistent naming pattern throughout the code base. So, what would be >the consistent naming convention for test classes? > >Thoughts? > >Regards, >Dmitriy. > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Rod J. <ro...@in...> - 2004-09-29 09:57:14
|
I prefer *Tests, because it means less renaming in Spring (=3D=3D less = loss of version history) and because one of these files contains multiple tests, = not just one... I find the *Test convention odd. I know the IDE issue is annoying, but I don't like to let IDE = conventions dictate usage. I would rather we leave this renaming until after the last 1.1.x = release. I agree that the inconsistency is annoying, but is it really that = important? Alternatively we could gradually migrate, taking the time to improve = doco etc on *TestSuite test cases as we rename them... R=20 -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf = Of Dmitriy Kopylenko Sent: 28 September 2004 16:10 To: spr...@li... Subject: Re: [Springframework-developer] Naming convention for JUnint = test classes I lean towards "*Tests" myself (and that's how we name it here at work). = +1 for "*Tests" Dmitriy. j=FCrgen h=F6ller [werk3AT] wrote: >That's true: We have "*Tests" and "*TestSuite", sort of mixed. All-embracing tests are often called "*TestSuite", while specific ones = are usually called "*Tests". That's not really a strict rule, though: The = choice is often arbitrary. > >I've thought about unifying those names myself repeatedly. I'd vote for "*Tests", as we're already using that for most tests anyway. This would simply mean renaming all "*TestSuite" classes to "*Tests". Can we do = that efficiently, in a batch maybe? > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf = >Of Dmitriy Kopylenko >Sent: Tuesday, September 28, 2004 3:13 PM >To: spr...@li... >Subject: [Springframework-developer] Naming convention for JUnint test=20 >classes > > >Juergen, everybody, > >I've noticed a long time ago that some of our test classes are named as = >xxxTestSuite and some are named as xxxTests. I'd like to see a=20 >consistent naming pattern throughout the code base. So, what would be=20 >the consistent naming convention for test classes? > >Thoughts? > >Regards, >Dmitriy. > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170=20 >Project Admins to receive an Apple iPod Mini FREE for your judgement on = >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php=20 >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170=20 >Project Admins to receive an Apple iPod Mini FREE for your judgement on = >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php=20 >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > =20 > ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 = Project Admins to receive an Apple iPod Mini FREE for your judgement on who = ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
