Ignoring the debug/release distinction

[io7m]

Hello!

In our apps, we don't use a debug/release distinction (we're open source software, everyone runs identical code, there are no "debug" or "release" builds). Unfortunately, the Android ecosystem imposes the distinction upon us, and so a command like this:

$ ./gradlew clean assemble test

... Will actually run the test suite twice; once in "debug" and once in "release". For some of our long running test suites, this is annoying and redundant.

Is there a simple way to only run the test suite once? My thinking is that some combination of release and debug test filters should be able to do it, but I can't seem to come up with the right combination.

Edit:

To clarify, we like having a single well-known command such as:

$ ./gradlew clean assemble test

Because this has the same interface regardless of whether the project is an Android project or a plain Java or Kotlin project. We don't want to have to use something like:

$ ./gradlew clean assembleDebug testDebug

... Because those tasks are Android-specific. I'd like to make the test task do the right thing all the time.

[io7m]

The most obvious solution (which I thought I tried first!) actually seems to handle this properly after all:

testOptions {
  junitPlatform {
    releaseFilters {
      excludePattern "**/**"
    }
  }
}

The build results in a testDebugUnitTest directory showing test executions, and no testReleaseUnitTest. 🎉