Verification-First Development • Buttondown
https://buttondown.com/hillelwayne/archive/verification-first-development/
before writing code, put in place some means of verifying that the code is correct, or at least have an idea of what you'll do.
Write Code That Works by Reid Burke
http://reidburke.com/2012/09/27/write-code-that-works/?awesm=reid.in_l6
If you’re writing tests for code that’s rapidly changing, you’re going to spend more of your time writing tests instead of shipping features. For code that’s brand new, I typically only test-first a small amount of code and wait a while before hitting that green bar on a code coverage report.
Write Code That Works by Reid Burke
http://reidburke.com/2012/09/27/write-code-that-works?awesm=reid.in_l6
If you’re writing tests for code that’s rapidly changing, you’re going to spend more of your time writing tests instead of shipping features. For code that’s brand new, I typically only test-first a small amount of code and wait a while before hitting that green bar on a code coverage report.
Personal unit tests
http://hober.backpackit.com/pub/1233865
"Basically, I’ve made a list of personal unit tests: assertions about myself that I’d like to be true."