-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 majority of tests to junit5 #3711
Conversation
please check if I didn't forgot one Test annotation
@@ -31,15 +31,14 @@ public void testExistenceOfIconImagesReferencedFromIconsProperties() throws IOEx | |||
try (Reader reader = Files.newBufferedReader(Paths.get(iconsPropertiesPath))) { | |||
properties.load(reader); | |||
} | |||
assertFalse("There must be loaded properties after loading " + iconsPropertiesPath, | |||
properties.entrySet().isEmpty()); | |||
assertFalse(properties.entrySet().isEmpty(), () -> "There must be loaded properties after loading " + iconsPropertiesPath); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, not sure if I like these Supplier Lambdas...Are they really needed? Makes the methods look more complex and I doubt that the evaluation of the message really takes a long time. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the beginning I did not see that I can pass the message as parameter without a supplier . The later tests are without. The supplier is only needed in the assertThroes
remove unnecessary supplier convert some more tests to junit5 fix imports
Mock externalFileTypes in importer test
Convert FormatterTest to junit5
convert architecture test to junit5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I scrolled over the code and it looks good to me (there are of course too much changes to verify everything in detail). Since the tests passes and the code coverage stays almost the same, everything should work as expected.
I am still struggling with Install4J. Not sure, when I'll have one that fight. |
please check if I didn't forget one Test annotation