GeistHaus
log in · sign up

Why should we aim for 100% code coverage?

engineering-management.space

I never worked on a project with 100% code coverage. I’ve worked on several projects with a high coverage and a test suite that gave confidence to the team. But even on those projects sometimes we’d have a nasty bug in production that could have been easily detected with a simple test. This is a tricky subject and usually developers don’t care much about this or think that it’s not worth the cost, or even that is not that useful. I’ve gathered here several arguments in favor for a full coverage.

0 pages link to this URL

No pages have linked to this URL yet.