-
-
Notifications
You must be signed in to change notification settings - Fork 26.5k
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
Use the same JUnit version everywhere #1500
Comments
I'd like to take this issue. Thank you in advance. |
Yes @ToxicDreamz, go ahead |
Half way through upgrading, one test case seems to be causing an issue, within the Serverless module, in specific the Initially the DynamoDBMapper was being Mocked with Mockito, and was causing issues once the tests were upgraded to JUnit 5 stating that the class could not be mocked, but as stated in the official Mockito guidelines, a type should not be mocked if it doesn't belong to you. See attached link below for details. https://github.com/mockito/mockito/wiki/How-to-write-good-tests#dont-mock-a-type-you-dont-own Suggestion.A new issue should be opened to address that certain test case, as of now the test case is commented out and marked with a TODO Displayed Error
Error after supplying region`
|
Overall the serverless module needs to be looked at, more tests are causing the same issues due to them not being able to be mocked. |
@ToxicDreamz FYI: I created #1505 which removes the dependency of |
@stefanbirkner Okay, thank you for the heads up. I'll wait for @iluwatar to merge that PR, until I continue with that module. |
It's merged now |
Using JUnit 5 in Trampoline module. PR #1529 created. |
I want to work on this issue if its is still unassigned . |
Ok @sgarg5794 |
I'm working on updating all the modules to JUnit5 right now. @ohbus |
Sure @charlesfinley you're good to go! |
Sorry I opened a new PR for this - #1668 |
@charlesfinley no need to be sorry for 😄 It is easier for us to review code in smaller chunks and this helps a lot 💯 Thank you so much for your help! |
This issue should probably be closed since the PR was merged and we have 2 new issues identifying the only modules lacking JUnit5. |
@charlesfinley great work! We will close this issue for sure. |
This issue has been partially addressed using #1542 and #1668 thanks to @charlesfinley Tests from two modules serverless and naked-objects are not being executed. Respective issues have been opened for resolving the tests in favour of these two modules. Resolving these two issues should close this current issue |
@iluwatar let me know how can I help with this, I am confused about the status of the what has been resolved and what is pending. |
Thanks for asking @anuragagarwal561994. I think the only remaining issue is that naked objects pattern still uses JUnit 4. Resolving this is covered by issues #1669 and #1683. I think we should close this task. |
At the moment there are some modules that are still using JUnit 4. Most of the codebase uses JUnit 5, but even with that there are different versions. For example
unit-of-work
andpartial-response
declare their own versions.In this ticket let's try to apply the same version of JUnit 5 everywhere upgrading from JUnit 4 where needed.
This issue has been partially addressed using #1542 and #1668
Tests from two modules serverless and naked-objects are not being executed.
Respective issues have been opened for resolving the tests in favour of these two modules.
Resolving these two issues should close this current issue
The text was updated successfully, but these errors were encountered: