ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Ignatenko (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-10739) get rid of using JUnit 3 API in IgniteConfigVariationsAbstractTest
Date Thu, 20 Dec 2018 05:25:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Ignatenko reassigned IGNITE-10739:
---------------------------------------

    Assignee: Oleg Ignatenko

> 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
>            Assignee: Oleg Ignatenko
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, technical_debt
>
> {{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)

Mime
View raw message