Restructure Kotlin/JS and Kotlin/JS/Wasm testing, fix #3329

[OliverO2]

What's inside

• Use the FrameworkAdapter interface provided by the Kotlin/JS test infra, so that failed tests are correctly reported for the JS target on Node.js (does not apply to Wasm/JS, which does not require "adapter transformation").
• Use JS Promise instead of callbacks to interact with the JS test framework.
• Clean up the code to avoid API layers changing from Mocha/Jasmine style ("describe", "it) to Kotlin test style ("suite", "test) and back.

Testing JS

Preparation

• settings.gradle.kts:
  • Add mavenLocal() to repositories.
  • Uncomment ":kotest-tests:kotest-tests-js",
• kotest-tests/kotest-tests-js/build.gradle.kts: use appropriate version numbers for mavenLocal publication:
  • id("io.kotest.multiplatform") version "5.9.0-LOCAL"
  • kotestCompilerPluginVersion.set("5.9.0-LOCAL")

Tasks

• gradlew publishToMavenLocal (once for the Kotest compiler plugin)

• gradlew -p kotest-tests/kotest-tests-js --continue cleanAllTests jsBrowserTest jsNodeTest wasmJsBrowserTest wasmJsNodeTest

• gradlew -p kotest-tests/kotest-tests-js cleanJsBrowserTest jsBrowserTest

• gradlew -p kotest-tests/kotest-tests-js cleanJsNodeTest jsNodeTest

• gradlew -p kotest-tests/kotest-tests-js cleanWasmJsNodeTest wasmJsNodeTest

• gradlew -p kotest-tests/kotest-tests-js cleanWasmJsBrowserTest wasmJsBrowserTest

Check failing tests

Create kotest-tests/kotest-tests-js/src/jsHostedTest/kotlin/io/kotest/engine/js/BasicTests.kt with content:

package io.kotest.engine.js

import io.kotest.core.spec.style.FunSpec
import io.kotest.matchers.shouldBe
import kotlinx.coroutines.delay
import kotlin.time.Duration.Companion.seconds

class BasicTests : FunSpec({
   test("pass") {
      log("test 'pass' running\n")
      true shouldBe true
      log("test 'pass' finished\n")
   }

   test("fail") {
      log("test 'fail' running\n")
      false shouldBe true
      log("test 'fail' finished (why?)\n")
   }

   test("pass delay") {
      log("test 'pass delay' running\n")
      delay(3.seconds)
      log("test 'pass delay' past delay\n")
      true shouldBe true
      log("test 'pass delay' finished\n")
   }

   test("fail delay") {
      log("test 'fail delay' running\n")
      delay(3.seconds)
      log("test 'fail delay' past delay\n")
      false shouldBe true
      log("test 'fail delay' finished (why?)\n")
   }

   test("!disabled") {
      log("test 'disabled' running (why?)\n")
   }
})

fun log(message: String) {
   println("$message\n")
}

Debug browser tests

Problems with Kotest functions running in the browser may not show up in the regular test output, but only in the browser's console. This is invisible with headless browsers. Unless we tweak things a bit:

1. Create kotest-tests/kotest-tests-js/karma.config.d/keep-browser-open.js with content:

   // https://stackoverflow.com/questions/31632191/have-karma-keep-browser-and-test-results-open-longer
   config.set({
      singleRun: false,
      autoWatch: true
   });

2. Add this section to the kotlin block in kotest-tests/kotest-tests-js/build.gradle.kts:

   js {
     browser {
       testTask {
         useKarma {
           useDebuggableChrome()
           // useChromeHeadless()
         }
       }
     }
   }

3. The browser may launch immediately, or you may need to click on the link shown in the test output.
4. When the browser launches, click the DEBUG button.
5. In the new tab, open the browser's dev tools, look for console messages, etc.
6. Refresh as necessary.
7. The node engine may hang at the end. On Linux, you may need to hard kill it (SIGKILL).

[OliverO2]

If there are no objections, I'd like to get this merged within 48 hours in order to test a bit with the snapshot in advance of any potentially upcoming release.