re: How do you measure your test coverage? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: However it seems odd to me that you'd have a test for an immutable model that tests all fields. We ignore files that don't necessarily need to be...
 

Yea I’m with Ben on the imperfection of code coverage as a metric. I set up Istanbul/NYC to ignore files that are just wrappers on API calls, files with constants, and any file where the type system is doing all of he heavy lifting. But honestly, I don’t use code coverage as anything more than a fun thing to watch on the build. Instead, I use the number of bugs that pop up in a given sprint as my measure of quality. And if a bug occurs then I know that my code coverage was low and/or that our tests were flaky. So I immediately go beef up the tests. :)

code of conduct - report abuse