• SeductiveTortoise@piefed.social
    link
    fedilink
    English
    arrow-up
    7
    ·
    7 hours ago

    Me, trying to fix failing tests my colleagues keep ignoring.

    “48 of 1307 fail, but for these seven it’s this’d the assertion expecting a new enum value, easy!”

    “106 of 1307 fail. What the fuck?”

      • SeductiveTortoise@piefed.social
        link
        fedilink
        English
        arrow-up
        5
        ·
        7 hours ago

        Their solution was to remove them from the pipeline. And I wondered why test coverage went down in SonarQube.

        0.9% is not a lot of coverage, let me tell you that.

        • ulterno@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 hours ago

          So I was given a project after a major part of it was made by an AI fanatic coworker and right before delivery, we were asked to make some specific types of documentation to submit.
          One of which included code coverage reports.

          The party receiving the documentation then said that they need 100% test coverage…
          Of a GUI application that interfaces with multiple proprietary devices over serial port, network, USB etc and is dependent upon the physical environment to get all code paths.

          I just gave that all to the AI fanatic coworker and am not even planning on reading the test code.
          If the program itself satisfies my logical requirements, I’ll ask him to change the test code to match the changed application code.

          • SeductiveTortoise@piefed.social
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 hours ago

            One hundred percent coverage is obviously not realistic. But I would wish there were more tests at least checking core components.