# The 100% code coverage problem

DevFeed: [The 100% code coverage problem](<https://devfeed.tech/articles/the-100-code-coverage-problem-28662.md>)

Original publisher: [Read original article](<https://jeroenmols.com/blog/2017/11/28/coveragproblem/>)

Author: info@jeroenmols.com (Jeroen Mols)

Published: 2017-11-28T00:00:00Z

Content type: opinion

Language: en

Sources: [Jeroen Mols](<https://devfeed.tech/sources/jeroen-mols.md>)

Topics: [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Code](<https://devfeed.tech/topics/code.md>), [test](<https://devfeed.tech/topics/test.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [blogs](<https://devfeed.tech/tags/blogs.md>), [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [quality](<https://devfeed.tech/tags/quality.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>)

## AI overview

The article explains why 100% code coverage is not a reliable quality measure or goal. Coverage records executed lines, but does not show whether tests contain meaningful assertions, cover all functionality, or verify correct interactions between components.

## Source excerpt

While you may be tempted to strive for 100% code coverage, that would be a horrible idea. Besides some code being hard to test, the concept of coverage is actually fundamentally limited.