• Hexorg@beehaw.org
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 year ago

    The Test part of TDD isn’t meant to encompass your whole need before developing the application. It’s function-by function based. It also forces you to not have giant functions. Let’s say you’re making a compiler. First you need to parse text. Idk what language structure we are doing yet but first we need to tokenize our steam. You write a test that inputs hello world into your tokenizer then expects two tokens back. You start implementing your tokenizer. Repeat for parser. Then you realize you need to tokenize numbers too. So you go back and make a token test for numbers.

    So you don’t need to make all the tests ahead of time. You just expand at the smallest test possible.

    • argv_minus_one@beehaw.org
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      It also forces you to not have giant functions.

      No, being unable to read giant functions is what forces me not to have giant functions.

      • Hexorg@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        My friend, let me tell you a story during my studies when I had to help someone find a bug in their 1383-line long main() in C… on the other hand I think Ill spare you from the gruesome details, but it took me 30 hours.

        • argv_minus_one@beehaw.org
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Case in point, actually. Whenever I’m forced to write a giant function, I always get nervous because it could be crawling with bugs that I have little hope of spotting.