Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot be run with JUnit 5 runner. #585

Open
tribbloid opened this issue Oct 4, 2022 · 5 comments
Open

Cannot be run with JUnit 5 runner. #585

tribbloid opened this issue Oct 4, 2022 · 5 comments

Comments

@tribbloid
Copy link

Here is an example:

build.gradle.kts

        test {

            useJUnitPlatform {
                includeEngines("scalatest")
                includeEngines("munit")
                testLogging {
                    events("passed", "skipped", "failed")
                }
            }

            testLogging {
                showExceptions = true
                showCauses = true
                showStackTraces = true
            }
        }

file:

import munit.FunSuite

class SimpleSpec extends FunSuite {

  test("abc") {
    assert(1 == 2)
  }
}

When executing junit for this test:

Execution failed for task ':meta:test'.
> No tests found for given includes: [xxx.SimpleSpec](--tests filter)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

So it appears that @RunWith(classOf[MUnitRunner]) annotation doesn't do anything.

@tribbloid
Copy link
Author

The compilation of https://github.com/eyalroth/java-scala-gradle-project/tree/munit also appears to be broken

@armanbilge
Copy link
Contributor

This is probably blocked by:

@tribbloid
Copy link
Author

2 years passed, and no fix on the horizon

@tgodzik
Copy link
Contributor

tgodzik commented Dec 2, 2024

2 years passed, and no fix on the horizon

I don't think there was anyone available to work on it and it didn't seem to have a high priority, but if you are interested you might have a go.

@SethTisue
Copy link
Contributor

is this ticket somehow distinct from #41 ? or should we just close it as a duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants