My organization has a mishmash of apex classes, both regular classes that execute specific business logic and test classes that execute unit tests on those regular classes. When we started developing on the platform we really didn't know what we were doing, so we didn't enforce any kind of naming convention on class names. For example, one developer might have created a class called
ShowDay and an accompanying test class called
ShowDayTest. Another developer might have a class called
Host_Validate with test class called
Host_Validate_Test. There are two problems with this for me:
(1) When looking at a list of all of the classes in the Force.com IDE or in the Salesforce UI, all the classes are there in a big jumble, whether they are test or not. I'd love to be able to see my test classes separate from all others. I can't quite articulate why except for the fact that I just feel like it would help me organize things better.
(2) The inconsistent naming convention leads to all kinds of weird class names. It would be nice to have one convention that's clean, consistent, and makes sense. However, I don't want to implement such a convention if it's outside of what's considered "normal."
Are there any best practices here?