Dealing with production code in tests
Sasikanth Miriyampalli, Obvious
You may be wondering, “why not use production code in tests?” Sometimes it might not be possible — like calling an Android framework class in unit tests — or sometimes we don’t want to. In those cases we replace the production code with alternative implementations for testing purposes and these are called ‘Test Doubles.’
Rails Conf 2013 The magic tricks of testing
Finding the right testing balance isn't magic, it's a magic trick. This talk strips away the veil and offers simple, practical guidelines for choosing what to test and how to test it while explaining the secret of writing stable tests that protect your application at the lowest possible cost.
Engineering culture at Obvious
Over the last ten years of writing code, we've become rather opinionated about how we work. All of our work is “country-scale”, which means it goes out to millions of people every day. Here's how we code, the Obvious way.
READ IT HERE →
Managing technical quality in a codebase
Crisis of technical quality, doing the quick stuff first and improving further on the second iteration, confronting the quality problems and best engineering practices.