For the last 3 odd years, I’ve been exploring the use of behavior (verbs, instead of Nouns, Test) as my test class names. The verb describes what behavior you expect from your system (program).
For example for a Veterinarian Information System (system responsible for billing and patient history), I would have tests called:
ChargeAccountForServices with the following test methods:
Another test class: GenerateBillsForClientAccount with
And another test class: ManageClientVisits with
These tests helped us flush out Objects like Account, Procedure, Visit and so on…. When we started we had no idea we’ll need these objects.
For more about this approach…read my last post…There is No Spoon (Objects)