WhatsInAnInterfaceName

Whats in an interface name, and does it help or hinder TestFirstDesign and the use of MockObjects?

Aside from readability, does this cause any real issues for test-first design, or the substituion of a mock object as a parameter to a method?

I think it inhibits refactoring because you have to change the type name when you change its content. Personally, I prefer to put the naming wart on the implementation, not the interface, because the interfaces are the "real" system. My understanding is that the I prefix is a historical leftover from using abstract classes as interfaces in C++ --SteveF