• Double_A@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Code changes that could affect tests happen all the time. It doesn’t need to be a specific refactoring of that unit.

    • Alexstarfire@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I don’t think you understood my point. That’s exactly why I think unit tests aren’t all that useful. Most code changes require updating the unit tests so unless you change the unit tests first all that’s being done is saying, yep this works how I programmed it to work.

      • Double_A@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        But if unit tests that other people wrote unexpectedly break, you know that you changed things that you maybe didn’t mean to change.

        • Alexstarfire@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Ideally. It’s just that more often than not it means you need to update the unit tests. I can still use my fingers to count how many times a unit test has caught a mistake I made, and I’ve been at my job for 10 years.

          I’m curious if others have a different experience.