            
              (3) Get annoyed by constantly increasing Code Coverage Requirements on untestable (often legacy) code.  Even afding comments requires code coverage go up!  Line must always go up!
Change step 2 to "Commit and push ONLY when absolutely necessary.  Because adding comments often requires a rewrite of untestable code."
Go back to Step 2 and wait for a major bug.

[–] fibojoly@sh.itjust.works 1 points 13 minutes ago* (last edited 12 minutes ago)

Our company "architects" decided we needed 80% coverage minimum. On a mostly .Net 4.8 codebase. Hundreds of programs used in prod, with barely any tests in sight.
It's a fucking nightmare.

[–] ExperiencedWinter@lemmy.world 2 points 2 hours ago* (last edited 1 hour ago)

Why would you care about code coverage requirements on a branch that is currently in development? My work in progress commits might not build because they don't even compile, let alone have passing tests. The only time I care about the build passing and meeting requirements is when I'm ready to create the pull request.

Also code coverage is a useless metric, but that's a different story.