This message was deleted.

We always call them

testIntegration

to ensure that it both sorts together with

test

(and other things like

testFixtures

) everywhere and reads as command on the command line:

gradle testIntegration

I usually call it

integTest

which is also the most widespread it have seen. The Gradle docs on the other hand call them

intTest

here: https://docs.gradle.org/current/userguide/userguide_single.html#sec:configuring_java_integration_tests. While that chapter should probably be changed to either use the JVM test suites plugin, or to use a different example.

@Fleshgrinder but your naming convention collides with Android and Kotlin multiplatform tests for example. I think integrationTest (or whatever in…Test) fits better because testFixtures are not tests themself

Probably, there's no standard so everyone does whatever. Not using Android nor multi platform so I don't know what they do. There's no

testFixtures

task so that's fine. Stuff like

int

,

intg

, ... is just cryptic. Not sure what's wrong with

integration

,

functional

, ... at least everyone understands what it is. Whether the test portion is the prefix or suffix shouldn't matter too much (except fs sorting) but it should be consistent. Having task names that resemble commands is imho always a nice too have.

at least everyone understands what it is

well, if only everyone had the same idea of what an “integration” test is : )

That’s a lost cause. 😄 We always only have

test

and

testIntegration

and that’s it.