4 ms·

Why? It's not hard to do if you start a fresh project.

• baconomatic 9y ago
  Just because you have coverage doesn't necessarily mean that you have written good tests. That being said, we do something similar where we require 80% coverage.
  • tehlike 9y ago
    The difference between 80% coverage and 100% coverage is overrated. 80% is more than sufficient, i'd even go ahead and say 70% is better. 100% goes into "change detecting test" territory. There's also the time aspect: going from 0-70 is not hard, 70-100 is extremely time consuming, and often not worth the effort. Monitoring is a way more efficient tool at catching issues.
    • baconomatic 9y ago
      While I agree with 70% is about the sweet spot, it really depends on the tools you're using. We've found that with using Jest and just doing snapshots you can get to 70% without actually testing any of your others methods, hence the 80% coverage requirement.