3 ms·
One thing I have found helpful in this sort of situation is to start by writing the exploratory code as a self-contained test. So a test that has no production
by mpweiher 8y ago
One thing I have found helpful in this sort of situation is to start by writing the exploratory code as a self-contained test.
So a test that has no production code it is testing.
Preferably in a language with really fast turnaround, a "scripting" language.
After a while, I have a self-contained test that does something, and does it reliably.
I can then refactor the test by extracting the production code.
- lancerkind 8y agoI do this too in cases where I’ve got an “extreme” amount of learning to do. (Learning a new language, a library, or something I’m trying to make work just simply won’t do I break it down into a tiny test). This isn’t my usual TDD workflow but I use it when my understanding of the mangauge or language feature are blocking me.