scala-cli test --native fails with "No framework found by Scala.js test bridge"

[mattlianje]

Version(s)
1.10.1

Describe the bug
Hello - and many thanks for your work!

Running scala-cli test --native with any test lib compiles and links successfully ... but fails with some misleading error about Scala.js test bridge, even though no JS platform is involved.

To Reproduce

//> using scala 3.5
//> using platform jvm native
//> using dep "org.scalameta::munit::1.2.1"

class SimpleTest extends munit.FunSuite {
    test("foo") {
        assertEquals(1 + 1, 2)
    }
}

scala-cli test . --platform native

Expected behaviour
Tests run on Native

Actual

 [error]  No framework found by Scala.js test bridge

Environment

  - Scala Native: 0.5.9
  - OS: Linux

[Gedochao]

This is very weird, as the test seems rather basic and this really should work. It also does work, as I tested it on my machine just now (MacOS aarch64).

Some things to try:

• double check if your source file is a test input (does the file name end with *.test.scala?)
• bump Scala to the latest stable (3.7.4 at the time of me writing this)
• make sure you're on the latest Scala CLI (I don't think much has changed in this area in 1.11.0, though)
• pass --native rather than --platform native, they should be synonyms
• double check if the framework gets detected on other platforms for you (JVM & JS)

I also realised that the associated integration tests were disabled for Scala 3, so I just re-enabled them. They do pass on my machine, but our CI will double check on Linux (which I'd also be surprised if it doesn't, as otherwise we'd have a bug report already...)
Anyway, let's use the following PR as a sanity check:

• Enable Scala Native tests with the test command on Scala 3 #4018

If you still end up having this problem, you can also pass the framework explicitly as a workaround, as evidently what is breaking for you is the framework detection.
Just add the following directive:

//> using test.framework munit.Framework

Finally, if nothing works, please check what else could be special to your setup, so that we can debug this further.