JavaScript Simplified Course: https://javascriptsimplified.com/?utm_source=youtube&utm_medium=video-description&utm_term=video-id-Zs2IpqHzchw

Many companies use some form of test coverage metric to measure how well tested their code is. Oftentimes these metrics are set as rules that must be maintained at all times. This is a terrible idea, though. Test coverage in general is a poor metric that doesn’t actually tell you anything meaningful about your code or the confidence you should have in it being bug free. In this video I talk about why test coverage is a bad metric and what you should do instead.


📚 Materials/References:

JavaScript Simplified Course: https://javascriptsimplified.com/?utm_source=youtube&utm_medium=video-description&utm_term=video-id-Zs2IpqHzchw
Code Coverage Article: https://www.epicweb.dev/making-use-of-code-coverage


🌎 Find Me Here:

My Blog: https://blog.webdevsimplified.com
My Courses: https://courses.webdevsimplified.com
Patreon: https://www.patreon.com/WebDevSimplified
Twitter: https://twitter.com/DevSimplified
Discord: https://discord.gg/7StTjnR
GitHub: https://github.com/WebDevSimplified
CodePen: https://codepen.io/WebDevSimplified


⏱️ Timestamps:

00:00 - Introduction
01:18 - Problem #1
04:45 - Problem #2
09:30 - Problem #3


#CodeCoverage #WDS #JavaScript

Web Dev Simplified

Testing is crucial for high-quality software, but 100% code coverage is an unreliable metric for code quality. Code coverage measures how many lines of code are executed but doesn't guarantee that all scenarios or intentions behind the code are tested. High code coverage may lead to neglecting important integration and end-to-end tests, which better simulate how users interact with an application. Instead of focusing on code coverage, developers should aim to test the intent and purpose behind their code, especially for user-critical functionalities.

100% Code Coverage Is Useless

most of the tests I’ve seen … well, they suck bad time.

Just because your tests run green doesn’t mean your code is golden. You gotta think about why your code does what it does, not just that it does it.
Great Post!

If you’re noticing that code coverage is hindering your team to deliver, try using it less or (if you have the authority/power) remove it entirely. Interesting concept, curious to see how this gets shaped moving into the future if more teams pick it up

Best way to improve coverage quality - mutation testing