ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@apache.org>
Subject Re: Is it time to move forward to JUnit4 (5)?
Date Wed, 18 Apr 2018 14:20:02 GMT
+100500 for upgrading of JUnit

https://developer.ibm.com/dwblog/2017/top-five-reasons-to-use-junit-5-java/
https://stackify.com/junit-5/

On Wed, Apr 18, 2018 at 8:59 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
wrote:

> 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
>



-- 
Alexey Kuznetsov

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message