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.

Sign up for GitHub

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

Jump to bottom

Support JUnit 5 and allow legacy JUnit 4 #553

Closed
emmanuelbernard opened this issue Jan 17, 2019 · 1 comment
Closed

Support JUnit 5 and allow legacy JUnit 4 #553

emmanuelbernard opened this issue Jan 17, 2019 · 1 comment
Assignees
@stuartwdouglas
Labels
help wanted Extra attention is needed release/noteworthy-feature
Milestone
0.7.0

Comments

@emmanuelbernard
Copy link
Member

JUnit 4 is a bit easier to setup in Maven.
But we want to me forward looking so let's make JUnit 5 our recommended approach.
@emmanuelbernard emmanuelbernard mentioned this issue Jan 17, 2019
Closed
8 tasks
@geoand geoand mentioned this issue Jan 18, 2019
Closed
@geoand
Copy link
Contributor

geoand commented Jan 18, 2019

@iocanel Count me in on this one if you want assistance

stuartwdouglas referenced this issue in stuartwdouglas/quarkus-old Jan 20, 2019
@stuartwdouglas
Fixes #553 Create a JUnit 5 test runner
9d258c3 
There are now three different runners:

- junit5: our preferred runner for end users
- junit4: legacy runner for JUnit 4
- junit5-internal: unit test runner for testing Shamrock itself
stuartwdouglas referenced this issue in stuartwdouglas/quarkus-old Jan 20, 2019
@stuartwdouglas
Fixes #553 Create a JUnit 5 test runner
1c560d3 
There are now three different runners:

- junit5: our preferred runner for end users
- junit4: legacy runner for JUnit 4
- junit5-internal: unit test runner for testing Shamrock itself
stuartwdouglas referenced this issue in stuartwdouglas/quarkus-old Jan 21, 2019
@stuartwdouglas
Fixes #553 Create a JUnit 5 test runner
42e68d5 
There are now three different runners:

- junit5: our preferred runner for end users
- junit4: legacy runner for JUnit 4
- junit5-internal: unit test runner for testing Shamrock itself
@stuartwdouglas stuartwdouglas self-assigned this Jan 21, 2019
@cescoffier cescoffier added this to the 0.7.0 milestone Jan 23, 2019
maxandersen pushed a commit to maxandersen/quarkus that referenced this issue Nov 5, 2022
@quintesse
fix: running tests won't affect user's environment anymore (quarkusio…
fdcd0ff 
…#553)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stuartwdouglas stuartwdouglas

Labels
help wanted Extra attention is needed release/noteworthy-feature
Projects
None yet
Milestone
0.7.0
Development

No branches or pull requests
5 participants
@emmanuelbernard @stuartwdouglas @iocanel @cescoffier @geoand