|
|
|
Thu, 10 Feb 2005
Test interactions, Not state
Dave Astels has a new blog.
He has this to say about
unit tests that test the private internals of an object:
"This is evidence of a serious misunderstanding of how you should be writing tests: they should be based on behaviour and function.. not state. An object’s state is simply an implementation detail, and should not be exposed to, or relied upon by, other objects. Guess what.. that means no getters & setters, either. But that’s a discussion for another time."
[/links]
permanent link
How to Stifle Creativity
From Bill:
"If you want to stifle participation and creativity focus on threats obligations and punishments in your communications with others. Make sure they are much more afraid of doing the wrong thing than they are of eager to do the right thing."
[/links]
permanent link
|