It covers each and every line of the source code, each and every conditional statement in the program and every loop otherwise known as iteration in the program.
I think it is important to note 100% code coverage (“covers each and every line”) does not mean the tests are good tests.
Worst, 100% coverage leaves you without a tool that is helpful for finding places where your tests might be lacking. Code coverage reports can be used to improve tests, but are not an indication of good tests in of itself.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
I think it is important to note 100% code coverage (“covers each and every line”) does not mean the tests are good tests.
The myth of 100% code coverage
Most of the time 100% code coverage is just a waste of time.
Worst, 100% coverage leaves you without a tool that is helpful for finding places where your tests might be lacking. Code coverage reports can be used to improve tests, but are not an indication of good tests in of itself.
Yep… I can get you 100% code coverage of a bug-laden, exploit-ridden piece of software effortless. It’s a useless measure.