- "Write tests. Not too many. Mostly integration."
- Integration tests strike a great balance on the trade-offs between confidence and speed/expense. This is why it's advisable to spend most (not all, mind you) of your effort there.
- biggest thing you can do to write more integration tests is to stop mocking so much stuff
- When you mock something you're removing all confidence in the integration between what you're testing and what's being mocked.
I have spent much of the last fifteen years trying to build bridges between the two solitudes of computing: academic researchers on the one side, and working developers on the other. These efforts have largely failed, but have done so in interesting ways. This talk will explore why the wide gulf between research and practice persists, and outline a new plan for trying to narrow it based on scurvy, smoking, and statistic