ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vyacheslav Daradur <daradu...@gmail.com>
Subject Re: Is it time to move forward to JUnit4 (5)?
Date Thu, 08 Nov 2018 15:04:45 GMT
Hi, thanks for pushing this activity.

You have mentioned only GridAbstractTest to be changed at the first
step, but how about GridCommonAbstractTest?

Tests in examples depend on GridCommonAbstractTest, should we clone
this class too or merge with GridAbstractTest?
On Wed, Nov 7, 2018 at 7:57 PM oignatenko <oignatenko@gridgain.com> wrote:
>
> Hello,
>
> I created JIRA task for this move, with detailed explanation and
> step-by-step subtasks, your comments are welcome:
>
> - https://issues.apache.org/jira/browse/IGNITE-10173
>
> In brief, the plan is to gradually migrate the part of tests that still uses
> Junit 3 (hundreds if not thousands of those that depend on GridAbstractTest
> and its subclasses) to newer version. The trick proposed to avoid doing all
> this in one (big and risky) step is to introduce a Junit4-based "twin" of
> GridAbstractTest (and respective twins of its subclasses) and use it to
> gradually change tests to use that newer API instead.
>
> After above is over, Junit 3 and all its related stuff (including
> GridAbstractTest) could be safely removed from project.
>
> regards, Oleg
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/



-- 
Best Regards, Vyacheslav D.

Mime
View raw message