The release notes did say that `runComposeUiTest` can be written in commonMain, but when I ran those...

# compose

[andylamax]

The release notes did say that runComposeUiTest can be written in commonMain, but when I ran those tests in android (./gradlew :testDebugUnitTest or ./gradlew testReleaseUnitTest), I am getting

Unresolved reference 'runComposeUiTest'

The same tests run fine on jvm target with (./gradlew :jvmTest)

I did setup my dependencies in commonTest as show below,

val commonTest by getting {
    dependencies {
        implementation(compose.uiTest)
    }
}

What am I doing wrong? using compose version 1.6.0

[Ivan Matkov]

сс @Alexander Maryanovsky

[Alexander Maryanovsky]

Are you trying to run them on Android?

[andylamax]

No, I thought
./gradlew testDebugUnitTest

only run on the machine (not the android phone or emulator), and I think it does, just can't seem to find those dependencies

[Alexander Maryanovsky]

You can only run desktop tests locally.

[Alexander Maryanovsky]

well, and wasm tests

[Alexander Maryanovsky]

For android it needs the Android emulator, for iOS it needs the iOS simulator

[Alexander Maryanovsky]

See https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-test.html

[andylamax]

wait, even the unit tests have to be ran on the device???

[Alexander Maryanovsky]

The compose UI tests can’t run as unit tests, they can only run as instrumented tests.

[Alexander Maryanovsky]

They can’t (currently) run with robolectric.

[andylamax]

Thank you for that clarification then, I was pulling out my hair on this one

[Alexander Maryanovsky]

np

[michaelv]

hi @Alexander Maryanovsky. what is the recommended way to add compose UI tests as described in that document without breaking the unit tests? i.e. if I run ./gradlew :composeApp:connectedAndroidTest it runs the compose UI tests and that’s all good. But if I then run ./gradlew testDebugUnitTest then it will try to run the compose UI tests also since they are in the same source set - but they will fail since it doesn’t have the dependencies for the UI test.

am I missing something or misunderstanding something or how to go about solving this?

one workaround I found is to exclude the test class but this is not ideal if I have to do that for every class.

allprojects {
    tasks.withType<Test> {
        if (name == "testDebugUnitTest") {
            exclude("**/ExampleCommonComposeTest*")
        }
    }
}

I could create a subfolder inside commonTest for unit and ui and exclude the ui folder instead of each class but then it’s using a different package to the main source set. What is the best way? Maybe just need to have separate source sets in common.

[michaelv]

anyone else know? what is the best way to do it? thanks. :)

[michaelv]

seems to be a ghost town. 👻

[Alexander Maryanovsky]

I don’t know the answer, and the question isn’t really about Compose. You have two sets of tests in the same module and source-set, and you want to run them separately. It’s a question about gradle, or maybe the unit-testing framework.

[michaelv]

hmm ok. thanks for responding! I guess for now there’s no recommendation for compose multi-platform projects.

[Julian Pellico]

Sorry to revive such an old thread, but not only is there still no simple solution, this also happens if you add platform specific unit tests in androidUnitTest source set. Now it's a separate source set, but still has the same problem. of course, the reason the same problem happens is it runs the same task testDebugUnitTest , so couldn't KMM project create a separate task to isolate the compose UI tests...?