• leisesprecher@feddit.org
    link
    fedilink
    arrow-up
    3
    ·
    3 days ago

    Tests first is only good in theory.

    Unit tests typically test rather fine grained, but coming up with the structure of the grain is 80% of the work. Often enough you end up with code that’s structured differently than initially thought, because it turns out that this one class needs to be wrapped, and this annotation doesn’t play nice with the other one when used on the same class, etc etc.

          • leisesprecher@feddit.org
            link
            fedilink
            arrow-up
            1
            ·
            3 days ago

            Because you don’t know what you’ll need that wrapper beforehand, that’s my entire point.

            Unless you’re only doing trivial changes, the chances are very high that you won’t be able to design the class structure. Or, you end up essentially writing the code to be able to write the tests, which kind of defeats the purpose.

            • CanadaPlus@lemmy.sdf.org
              link
              fedilink
              arrow-up
              1
              ·
              3 days ago

              That’s kind of the whole philosophy, though. The tests are the main way you understand what you’re doing, the working code is just an addition on top of that. Presumably, there’s a way to do that without repeating yourself - although I’m not turning up much on a quick look.