Breaking up (with) your test suite (Justin Searls) @TestDouble
Breaking up (with) your test suite (Justin Searls)  @TestDouble
Uploaded March 2020 | Updated November 2026, 5 days ago
In this day and age, we have a thousand ways and reasons to test our code. On it’s face, this is great! But the sword is double-edged: when I open a test that I’m not familiar with, I have to determine why it exists from any of a thousand possible reasons. If I want to add my own tests, I must decide how to implement it from any of a thousand possible methods.

The most immediate abstraction we have for wrangling the motivations and implementations of our tests is the “test suite”. By cordoning off each group of tests based on the value we hope to get out of them, we can develop unprecedented clarity in our working relationship with tests.

This talk is an example of how to do that. Hopefully, it’s at just the level of detail you’ll need to ponder how to apply a similar approach to your teams and applications.

More here: blog.testdouble.com/talks/2014-05-25-breaking-up-with-your-test-suite
Breaking up (with) your test suite (Justin Searls)Judgment to build the right thing in the first placeWhat is a Meta Programmer?Technical fixes are not magic cures if your org is failingDevelopers do not want to write documentation (AI helps)A Better Technical Interview (Sam Jones)3 Stages to evaluate codeSometimes a Controller is just a Controller (Justin Searls)How to tell if AI threatens your jobThe Social Coding Contract (Justin Searls)Diagnosing vibe coding with code smells: superpower or illusion?Unpopular opinions on vibe coding from senior developers
Test Double |

Breaking up (with) your test suite (Justin Searls)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER