Adam S
03/12/2024, 7:34 PMgradle :kotest-tests:kotest-tests-js:jsTest
, and see screenshot).
How can I test if my changes have affected Wasm? When I run gradle wasmJsTest
it doesn't trigger anything...Adam S
03/12/2024, 7:34 PMOliver.O
03/13/2024, 12:34 AMwasmJsTest
task is not even available in your case.
The version of kotest-tests/kotest-tests-js/build.gradle.kts that is part of your PR says:
plugins {
id("kotest-js-conventions")
// must be a published version and not one in the current build
id("io.kotest.multiplatform") version "5.8.0"
The unpublished Kotest 5.9.0 will be the first release containing the}
wasmJs
target. So in the meantime you could adjust the version in the above build script, publish the respective Kotest version locally (e.g. publishToMavenLocal
) and pick it up from there.
Note that kotest-tests-js
was still disabled in the main branch when merging the WasmJS changes. So it may work with WasmJS or it may not. General WasmJS testing is done in kotest-framework/kotest-framework-multiplatform-plugin-gradle
, using a separate build of test-project
(but this is slooooow).