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

JUnit Engine should be managed #831

Closed
melix opened this issue Aug 2, 2023 · 0 comments · Fixed by #936
Closed

JUnit Engine should be managed #831

melix opened this issue Aug 2, 2023 · 0 comments · Fixed by #936
Assignees

Comments

@melix
Copy link
Contributor

melix commented Aug 2, 2023

Feature description

There's an inconsistency in how we handle the test frameworks. With kotest, we can use:

    testImplementation(mnTest.micronaut.test.kotest5)
    testRuntimeOnly(mnTest.kotest.runner.junit5.jvm)

To get the JUnit5 runtime dependency. But we have no such thing for JUnit, which forces to declare a dependency:

    testImplementation(mnTest.micronaut.test.junit5)
    testImplementation("org.junit.jupiter:junit-jupiter-engine:5.9.2")

Note that this is in a test-suite project, not a user project which would apply the Micronaut Gradle plugin, but still, for consistency and users wanting to avoid our plugins, there should be a managed version of JUnit.

altro3 added a commit to altro3/micronaut-test that referenced this issue Jan 27, 2024
altro3 added a commit to altro3/micronaut-test that referenced this issue Jan 27, 2024
altro3 added a commit to altro3/micronaut-test that referenced this issue Feb 14, 2024
sdelamo added a commit that referenced this issue Feb 20, 2024
Fixed #831


---------

Co-authored-by: Sergio del Amo <sergio.delamo@softamo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants