-
Notifications
You must be signed in to change notification settings - Fork 19
chore: migrate junit 3 test to junit4 #523
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
base: master
Are you sure you want to change the base?
Conversation
why not JUnit 5? |
The rest of the code base is junit 4 and want to have a minimal change. But of course Junit 5 would be better. Let me take a look on it tomorrow. Thanks for your feedback. |
Signed-off-by: Sandra Parsick <[email protected]>
897dfc6
to
694dd2f
Compare
Many tests are based on Do you have a hint how to handle |
We can try with plexus-testing - example: |
@slawekjaranowski Thx for the link, I will take a look on it. |
also new version released with simple documentation |
Signed-off-by: Sandra Parsick <[email protected]>
migrate one test based on your hint. Unfortunately, I have to use PlexusExtension directly, because of some container configuration customize. Do you think this is the way to go? Or did I oversee anything? |
Signed-off-by: Sandra Parsick <[email protected]>
No description provided.