Hello folks, how are you separating unit tests from integration test in a multiplatform setting??

# multiplatform

[andylamax]

Hello folks, how are you separating unit tests from integration test in a multiplatform setting??

[Anmol Verma]

I never inject multiplatform settings directly to my consumers.. instead i pass a interface. And for unit tests they depend on a fake in memory data impl, for android and other platform tests the impl with settings instance is used

[andylamax]

I am sorry, I failed to make myself clear. When I said "In a multiplatform setting", I meant "In a multiplatform project", Not Russel Wolf's library "Multiplatform Settings"

[Anmol Verma]

so all unit tests go in commonTest dir and all platform tests go to theirs, a small example from my repo here CommonTest: https://github.com/oianmol/SlackComposeMultiplatform/blob/main/capillary-kmp/src/commonTest/kotlin/TestCapillaryInitialization.kt

AndroidTest: https://github.com/oianmol/SlackComposeMultiplatform/blob/main/capillary-kmp/src/androidInstrumentedTest/kotlin/TestCapillaryInitialization.kt

[Anmol Verma]

Screenshot 2023-10-01 at 1.08.53 PM.png

[andylamax]

and where do integration tests (not unit tests) for browser go?
where do intergration tests for desktop go??


In short i am almost asking for the equivalent of "androidInstrumentedTest" (androidIntergrationTest to be precise) but for non android targets such as, browser, nodejs, desktop, all other nativeTargets.

[andylamax]

on top of that, I am asking how do I place them in a single source set? (say commonIntegration test)???

[andylamax]

the same way android test have been split for unit and instrumentation tests, I need to be able to split unit tests and integration tests for all targets

[Anmol Verma]

You can create your own source sets right and name them ?

[Anmol Verma]

val jvmIntegrationTest by creating {}
        val jvmTest by getting {
            dependsOn(jvmIntegrationTest)
        }
        val nativeIntegrationTest by creating {}
        val nativeTest by getting {
            dependsOn(nativeIntegrationTest)
        }

[andylamax]

and what gradle task will I execute so that I may only run those tests in those sourceSets??

[Anmol Verma]

how about filtering by package ?

gradle test --tests 'com.example.native.integrationTests*'

[Anmol Verma]

something like this https://jskim1991.medium.com/gradle-creating-a-new-source-set-for-integration-test-using-kotlin-dsl-f5b67da2aea3