A transition to junit5 should also be easy - even for the real junit5 (called Jupiter) and not the junit5 compatibility layer (called vintage). For Jupiter the major changes are the order of arguments for assertions (I came over this for 1000 test case with probably 10000 assertions in another project) - you can use regular expression to reorder them in the source code (E.g. using Eclipse replace). Another thing is the verification that an Exception is thrown - this is also more elegantly handled in Junit5 jupiter.
> Am 18.04.2018 um 15:59 schrieb Dmitry Pavlov <dpavlov....@gmail.com>: > > Hi Igniters, > > During MTCGA monitoring I’ve discovered a number of issues related to test > framework itself. > > In addition it is not convinient to mute tests on TC, because in branches > (e.g. 2.5 and in master) we can’t mute it separately. So some tests, which > already fixed are shown as failed in our PRs and release branches. But > current JUnit3 test style does not allow to use @Ignore. > > Is it time to start translating tests to Unit 4 style? > > Are there any of us who would like to assist in the research and create a > new GridCommonAbstractTest and/or IgniteJUnitRunner? > > Sincerely, > Dmitriy Pavlov
