- how they don't just test implementation
- how you expect developers to hunt for something they really don't want to find (i.e. problems with their implementation... I mean if they could think of it, they would have solved it in the code, right?)
- how they work in a world dependent on side effects: if it's a function, inputs in, output out, that's pretty straightforward. But so much of UI, say, is the evil of "side effects", changing something else in the environment that the user will see...
2 unit tests. 0 integration tests pic.twitter.com/V2Z9F4G1sJ— Practical Developer (@ThePracticalDev) January 14, 2016