# The hidden cost of code coverage

DevFeed: [The hidden cost of code coverage](<https://devfeed.tech/articles/the-hidden-cost-of-code-coverage-28650.md>)

Original publisher: [Read original article](<https://jeroenmols.com/blog/2016/09/01/coveragecost/>)

Author: info@jeroenmols.com (Jeroen Mols)

Published: 2016-09-01T00:00:00Z

Content type: tutorial

Language: en

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

Topics: [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Testing](<https://devfeed.tech/topics/testing.md>)

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

## AI overview

This tutorial explains that enabling code coverage with JaCoCo can significantly slow Gradle builds, even when tests are not being run. It recommends using a build flag so coverage runs only when needed, such as after unit tests or during CI builds.

## Source excerpt

Code coverage is an awesome way to motivate you and your team to write more tests. But did you know that simply enabling it slows down your build significantly?