You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Oleg Ignatenko (JIRA)" <ji...@apache.org> on 2018/12/19 11:05:00 UTC

[jira] [Created] (IGNITE-10739) get rid of using JUnit 3 API in IgniteConfigVariationsAbstractTest

Oleg Ignatenko created IGNITE-10739:
---------------------------------------

             Summary: get rid of using JUnit 3 API in IgniteConfigVariationsAbstractTest
                 Key: IGNITE-10739
                 URL: https://issues.apache.org/jira/browse/IGNITE-10739
             Project: Ignite
          Issue Type: Task
    Affects Versions: 2.8
            Reporter: Oleg Ignatenko


{{IgniteConfigVariationsAbstractTest}} and part of test framework that uses this class very heavily rely on JUnit 3 specific features.

The task is to get rid of these and use newer versions instead - preferably JUnit 4, although JUnit 5 is also an option

This will allow consistent JUnit framework version across Ignite tests which in turn is expected to simplify maintenance and development of the tests (including ignoring tests, workiing on Teamcity related things etc).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)