OliverO2 / kotlin-js-wasm-testing

Experimental Kotlin/JS and Kotlin/Wasm/JS test infrastructure

Experimental Kotlin/JS and Kotlin/Wasm/JS test infrastructure

This project aims to experiment with test runners on the JS platform, in particular regarding

• supporting asynchronous tests,
• supporting nested tests.

Flat Test Framework

The project features alternative flat test frameworks, selectable by setting flatTestFramework in src/jsHostedMain/kotlin/Main.kt:

• kotlinJsTestFramework: A bare-bones implementation of the Kotlin-provided test framework used with kotlin-test.
• standaloneJsFlatTestFramework: A standalone flat test runner. It does not work with browser-based tests due to missing Karma integration.

Synchronous and asynchronous test invocations are supported.

Nested Tests Framework

Running runNestableTests() in src/jsHostedMain/kotlin/Main.kt invokes a suite with nested tests using a separate framework on top of the selected flat test framework. This produces reasonable output when run as a normal application (gradlew jsNodeDevelopmentRun).

When run via test tasks with standaloneJsFlatTestFramework, IntelliJ IDEA does not show the correct nesting.

With kotlinJsTestFramework, the Kotlin test infra (if used) complains:

• previous test `jsNodeTest/nestable async (via JS/Mocha/transformed)/nestable async (via JS/Mocha/transformed)` not finished
• Bad TCSM: unexpected node to close `should pass`, expected `nestable async (via JS/Mocha/transformed)

Test Tasks

• gradlew --continue cleanAllTests jsBrowserTest jsNodeTest wasmJsBrowserTest wasmJsNodeTest

• gradlew cleanJsBrowserTest jsBrowserTest

• gradlew cleanWasmJsBrowserTest wasmJsBrowserTest

• gradlew cleanJsNodeTest jsNodeTest

• gradlew cleanWasmJsNodeTest wasmJsNodeTest

Checking unmodified test reports

Available with the standaloneJsTestFramework only.

• gradlew jsNodeDevelopmentRun

Background

• TeamCity Messages: Service Messages | TeamCity On-Premises Documentation