Re: [Springframework-developer] Naming convention for JUnint test classes

[Colin S. <col...@ex...>]

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.
>  
>