Can it be that Amper has problems discovering Kote...

# kotlin-toolchain

[Sebastian Schuberth]

Can it be that Amper has problems discovering Kotest StringSpec tests? Because I'm getting:

❯ ./amper test
00:03.152 INFO  :lib:testJvm              Testing module 'lib' for platform 'jvm'...

Test run finished after 125 ms
[         4 containers found      ]
[         0 containers skipped    ]
[         4 containers started    ]
[         0 containers aborted    ]
[         4 containers successful ]
[         0 containers failed     ]
[         0 tests found           ]
[         0 tests skipped         ]
[         0 tests started         ]
[         0 tests aborted         ]
[         0 tests successful      ]
[         0 tests failed          ]

ERROR: JVM tests failed for module 'lib' with exit code 2 (no tests were discovered) (see errors above)

[Sebastian Schuberth]

This is with https://github.com/sschuberth/stan/tree/amper.

[Sebastian Schuberth]

I guess instead of the junit-platform-console-standalone-6.0.1.jar artifact, the io.kotest.engine.launcher.MainKt entrypoint should be used?

[Anton Prokhorov]

> Can it be
it can be of course, I'll create an issue

[joffrey]

I guess instead of the junit-platform-console-standalone-6.0.1.jar artifact, the io.kotest.engine.launcher.MainKt entrypoint should be used?

I don't think so. Kotest works a JUnit platform engine too, so it should be discovered by JUnit. One thing to check, though: do your test classes end with the Test or Tests suffix? This is the default expected by the JUnit platform.

[joffrey]

If this is the source of your issue, I will reconsider this default. We should override it because you're at least the 3rd or 4th person to report a problem because of this.

[Sebastian Schuberth]

Should be ok, see: https://github.com/sschuberth/stan/blob/amper/lib/test/BookingItemTest.kt

[joffrey]

Oh I had forgotten you had shared your project's link, sorry to bother you with the question, then!