Attentive readers may have noticed the naming convention of integration tests ending with IT for integration test. This naming emerged from a Maven naming convention, excluding test classes, that don't match the Test naming pattern, in the test phase. Classes ending with IT will be run by a different life cycle plugin.

This approach supports developers in crafting effective development pipelines, since code level integration tests shouldn't necessarily run in the first build step depending on the time they take. With the example of Maven, the Failsafe Plugin runs integration tests, using the command mvn failsafe:integration-test failsafe:verify, after the project has been built.

The IDE, of course, supports both running Test named tests as well as other naming conventions.

Gradle doesn't take this naming structure into account. In order to achieve the same goal, Gradle projects would use multiple sets of test sources that are executed separately.