Earlier quoted context omitted.
Would you be able to share any links that expand upon your recommended approach? It makes complete sense to me as a self-taught dev, and is what I've always done (most recently, an e2e test of a realtime cdc etl pipeline, checking for/logging and fixing various things along the way until I was getting the right final output). I rarely write unit tests. It would be good to read something more formal in support of what…
no, but i have a feeling i should write one because i keep running into this misunderstanding. it makes it really hard to recommend TDD when people believe they already know what it is but are doing it ass backwards.
I just remembered this essay from the creator of HTMX. My approach is very similar.