News for hackers. Stuff that matters.
Re:Test Isolation Is About Avoiding Mocks by adamors on Thursday May 15, 2014 @04:07PM (#7751897)
Well, one thing I learned from all this recent TDD related discussion is that almost nobody is aware of this book [1] and the entire school of TDD it spawned.

[1] http://www.amazon.com/Growing-Object-Oriented-Software-Guide...

Re:Test Isolation Is About Avoiding Mocks by platz on Thursday May 15, 2014 @04:17PM (#7751964)
This is a great book. Although I must admit it kind of "washed over me" a bit too much. Perhaps it was just the java.. I think I need to re-read it to be able to synthesize the ideas in it, and connect the high-level ideas to the examples later in the book enough to be able to get the same results in my own work.
Re:Test Isolation Is About Avoiding Mocks by henrik_w on Thursday May 15, 2014 @04:12PM (#7751928)
An alternative way of using unit tests is this: Selective Unit Testing – Costs and Benefits http://blog.stevensanderson.com/2009/11/04/selective-unit-te...

The main idea there is to unit test logic, but not unit test "coordination-code".

Re:Test Isolation Is About Avoiding Mocks by gary_bernhardt on Thursday May 15, 2014 @04:16PM (#7751963)
That sounds vaguely similar to "Functional Core, Imperative Shell". I merge state management and coordination (together, the shell) so that the logic (the core) can be composed of pure functions without coordination overhead. So far I've done very little testing of the imperative shell.