That makes a lot of sense. I'll get the book and look out for the post. But I was wondering: does it make sense to have classes implement interfaces specifying public exposure of methods, but contain public methods that are there only to be accessed by the tests?
That is, the interface specifies a public method getIdentity() that returns an _identity_ object, but the class has getName(), getIDNumber(), that are public (so we can test them) but not declared in the interface? Do people do things like that?
That is, the interface specifies a public method getIdentity() that returns an _identity_ object, but the class has getName(), getIDNumber(), that are public (so we can test them) but not declared in the interface? Do people do things like that?