MockObjectNamingConventions

Variables

ExpectationCounter? _methodName_Calls; ReturnValues? _methodName_ActualReturnValues; ExpectationList? _methodName_Parameter0Values (etc);

Methods

public void setExpectedCalls_methodName(...); public void addExpectedValues_methodName(...); public void setupReturn_methodName(...);

I prefer '_' to 'my', but this is not the issue. I think '_' separators is clearer: this is special code after all: test code, not production. MilesD

I disagree (on both counts), but it's more important to be consistent within your project than with the rest of the world. --SteveF

It's nice though if your consistent with the rest of the world, especially if you travel around a lot. -- JeffMartin

What is your preferred naming convention Steve? - MpC

Just to throw my tuppence-worth in: I'd prefer it if the classes generated by MockMaker had the word 'Mock' at the end of the class name and not the start. This fits in (I think) with the usual JUnit convention of putting 'Test' at the end of test classes, and also makes it easier to find Mock, Real and Test class implementations, as they all end up next to each other in directory and code control lists. --DarrenH