See e.g. http://martinfowler.com/articles/mocksArentStubs.html. A "stub" is
normally a pre-programmed implementation that contains no logic or expectations
(q.v. EasyMock's asStubReturn()), while a "fake" is a better name for something
that uses a non-production implementation for tests.
As it stands, I suppose that you could argue that StubClock is a stub, in that
we currently only program it with the current time, but if we were to add any
additional logic (e.g. as in issue 72), it's no longer an appropriate name.
Original issue reported on code.google.com by
malcolm.roweon 21 Apr 2012 at 9:36