Uploaded July 2024 | Updated September 2026, 1 week ago

---

JavaScript Simplified Course: 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: 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: blog.webdevsimplified.com
My Courses: courses.webdevsimplified.com
Patreon: patreon.com/WebDevSimplified
Twitter: twitter.com/DevSimplified
Discord: discord.gg/7StTjnR
GitHub: github.com/WebDevSimplified
CodePen: codepen.io/WebDevSimplified


⏱️ Timestamps:

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


#CodeCoverage #WDS #JavaScript