[Bug]: JVM unit tests are not executed on CI

[SimonMarquis]

Is there an existing issue for this?

• I have searched the existing issues

Is there a StackOverflow question about this issue?

• I have searched StackOverflow

What happened?

Since the recent merge of this PR

• Prep work for JVM alternatives to modules/plugins #923

, the :core:common module is now a pure JVM module.

Unfortunately, the CI currently only runs Android tests:

nowinandroid/.github/workflows/Build.yaml

Line 106 in 50b13ec

run: ./gradlew testDemoDebug :lint:test

This also brought up this issue with missing test dependencies that were not visible on CI builds:

• [Bug]: Build Broken #1544

Relevant logcat output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[JoseAlcerreca]

How do you suggest we run all the JVM tests? I wouldn't want to specify every JVM module in the command.

[SimonMarquis]

A solution to this could be to do something similar to slackhq/slack-gradle-plugin's UnitTest.kt that creates a global ciUnitTest task that executed the JVM default test tasks as well as the chosen test${variant}UnitTest Android test task.
This worked for us with an even simpler setup on adevinta/spark-android.

[alexvanyo]

I would prefer switching over to a built-in umbrella task like check if we can, as that would avoid other cases like this in the future where there's a new type of check that we forget to add to CI.

If check runs too much, maybe we can look into something like switching to single-variant Android modules.

[Jaehwa-Noh]

What about add task with dependsOn at JVM module's gradle?
https://docs.gradle.org/current/userguide/controlling_task_execution.html#sec:adding_dependencies_to_tasks

If the CI merely check demoDebugTest, you can make dependency with that.