4 ms·

What's wrong with TDD? This is a serious question, not starting an argument.

• BobbyTables2 11mo ago
  Try it and you’ll quickly see…
  • CPLX 11mo ago
    I have. I don’t hate it, though I don’t think it’s a magic bullet either.
• jmann99999 11mo ago
  My issue with it has always been that I just don't think the way TDD requires. I think in terms of building features. TDD generally requires thinking in terms of proving behavior. I still can't wrap my head around first writing a test that fails and then writing minimal code to make it pass (I know I am simplifying it). Different strokes for different folks. I'm sure it works great for some people but not for me.
  • moi2388 11mo ago
    Well, all it does is basically enforce you code with testing (abstraction) in mind, and only focus on what you need. So you build feature A. Great. Why not write a test to instantiate the feature? It will fail, because you haven’t built it yet. Now go build it. I assume you build the interface first already, before every little detail of the methods? Also, you really don’t have to stick to the TDD principles that much. It’s basically to ensure: 1. You have a test which can fail (it actually tests something) 2. You actually have a test for your unit 3. You actually only code what you’re supposed to This is great for juniors, but as you have more experience, these individual steps lose value, but the principles remain I think. Also, I would never write tests for every method (as TDD might have you believe), because that’s not my “unit” in unit testing.