-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
MIgrate tests to Junit5 #1151
Comments
Good idea! Project was started JUnit4 a loonng time ago but can definitely switch to JUnit 5. |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Signed-off-by: Laurent Broudoux <laurent.broudoux@gmail.com>
Signed-off-by: Laurent Broudoux <laurent.broudoux@gmail.com>
Signed-off-by: Laurent Broudoux <laurent.broudoux@gmail.com>
Signed-off-by: Laurent Broudoux <laurent.broudoux@gmail.com>
Now done. Thanks to @gbloquel for awesome contrib! |
Reason/Context
Working on test issue, I noted that the project is using JUnit4 and JUnit5.
Description
The idea is to standardize the JUnit version for all application tests.
Implementation ideas
To use all tests with unique JUnit version
The text was updated successfully, but these errors were encountered: