3 ms·
A decade ago, that TDD would be a de facto standard by now. It's not
- qvzvabgra 7y agoTitle needs fixing, but I think the real issue is that even in the hearts of the most loving TDD users, writing the tests in their entirety first is not how they actually operate, so it's already stuck with that false stigma out the gate. It's too... dogmatic about how you're supposed to approach problems. I don't think in a way that's conducive to "tests first" because I rarely know what the full implementation of a feature or bugfix will look like before I've gotten working code up and running. Once I've done the first "rough draft" pass, only then do I have a firm grasp on what the second pass/refactoring will look like, and at that point I can begin to think in terms of tests "first" (pre-refactoring, at least). But I don't think that way, either. I guess TDD really matters most as a way of forcing a final product that looks like the tests were written first. If we're interested in outcomes over dogma, making sure the code output looks right is the real outcome, and I do think it's a valuable tool for that. All of that is still completely backwards from what's on the tin, however.