# Find the slowest tests of a Java project

DevFeed: [Find the slowest tests of a Java project](<https://devfeed.tech/articles/find-the-slowest-tests-of-a-java-project-37842.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/slow-tests/>)

Author: Carlos Alexandro Becker

Published: 2014-04-28T00:00:00Z

Content type: tutorial

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Maven](<https://devfeed.tech/topics/maven.md>)

Tags: [coverage](<https://devfeed.tech/tags/coverage.md>), [java](<https://devfeed.tech/tags/java.md>), [junit](<https://devfeed.tech/tags/junit.md>), [maven](<https://devfeed.tech/tags/maven.md>), [scripts](<https://devfeed.tech/tags/scripts.md>), [tests](<https://devfeed.tech/tags/tests.md>)

## AI overview

The article explains that slow tests can discourage teams from running and writing tests, reducing test coverage. It recommends identifying and fixing the slowest JUnit tests, reducing test dependencies, and using scripts and Maven tools to find slow build components and enforce pull-request coverage thresholds.

## Source excerpt

I found that it's pretty hard to have a project with high test coverage and fast build... if the tests are slow, people will feel the need to skip them to speed up the build, and will probably write fewer tests than they should, afraid that the build will become even slower. You go out for a walk and when you come back no one is running or writing tests anymore...