Why Good Developers Write Bad Unit Tests · mtlynch.io
mtlynch.io · 2,386 words · saved by 1 readers
The standard techniques of good development can lead you astray if you don't adjust them for unit tests.
Congratulations! You've finally written so many lines of code that you can afford a beach house. You hire Peter Keating, an architect world-famous for his skyscrapers, who assures you that he has brilliant plans for your beachfront property. Months later, you arrive at the grand unveiling. Your new home is an imposing five-story behemoth of steel, concrete, and reflective glass. As you pass through the revolving doors, you track sand onto the opulent marble floor. Inside, you find a reception desk backed by an elevator bank. Upstairs, your master bedroom and three guest rooms are just four adj
saved by
related reading
- GitHub - mawrkus/js-unit-testing-guide: 📙 A guide to unit testing in Javascriptgithub.com
- Crafting High Quality Unit Tests: Tips and Best Practicesmarclittlemore.com
- The Grug Brained Developergrugbrain.dev
- Software Engineering at Googleabseil.io
- CSC 151 - Unit Testingeikmeier.sites.grinnell.edu
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Fighting Distraction With Unit Tests | Matthew C Devmatthewc.dev
- What if writing tests was a joyful experience?blog.janestreet.com
- Reading 3: Testingweb.mit.edu
- Google Testing Blogtesting.googleblog.com
- Reading 2: Testingweb.mit.edu