This gradle tasks works correctly, I can see the f...

# gradle

[jean]

This gradle tasks works correctly, I can see the file at the into location

tasks.register<Copy>("copyIosTestResources") {
    from("src/commonTest/resources")
    into("build/bin/iosX64/debugTest/resources")
}

tasks.findByName("iosX64Test")!!.dependsOn("copyIosTestResources")

But if I try to do the same for my js target with this

tasks.register<Copy>("copyJsTestResources") {
    from("src/commonTest/resources")
    into("build/js/test/resources")
}

tasks.findByName("jsTest")!!.dependsOn("copyJsTestResources")

I tried a bunch of different values for into but it doesn’t seem to work at all. Any idea why?

[Javier]

jsTest exists?

[jean]

I have no idea hehe, first time targeting it. If I try “js2Test” I get an error saying java.lang.NullPointerException so I supposed “jsTest” was the correct name

[jean]

I can run ./gradlew jsTest so I suppose it does exists yes

[Vampire]

If I interpret your code correctly, your tasks copy files into the output directory is another task. This is a big no-go anyway. Tasks should never have overlapping outputs.

[jean]

I did this for android and ios target, it works well. I’m just trying to find a way to support js target too https://developer.squareup.com/blog/kotlin-multiplatform-shared-test-resources/

[Vampire]

It might seem to work well, but it doesn't. Especially regarding up-to-date checks and if you use build output cache. You will end up with strange build behavior and hard to debug issues if tasks have overlapping outputs, as well as some more sophisticated Gradle features being disabled if Gradle detects it.

[jean]

So what solution do you advocate to share test resources? Have them hardcoded in commonTest directly?

[Vampire]

I'm not familiar with KMP builds, sorry.

[Vampire]

But hardcoded sounds not good either, no

[jean]

@vgonda you wrote the article I linked, do you have any recommendations?

[vgonda]

Sorry, I don't 😞