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

[<jue...@we...>]

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