Omg nothing is as frustrating as writing tests for a given file, that is needed to achieve 100% code coverage. Also not following TDD.

  • 7
    100% code coverage is a ridiculous target, and anyone who mandates that has no clue what they're on about.
  • 3
  • 1
    Agree, writing tests after-the-fact is way too late. You're codifying what the code currently does, not what it actually should do.

    I once joined a project to help putting out fires. Of course it had 0% test coverage. The junior dev in charge (whoever was braindead enough to make a junior the lead dev...) was like "good point, why don't you write the tests? That's good training to get to know the project" - No, it's not. No, just no. 🤦🏻‍♂️
Add Comment