[IGNITE-10739] get rid of using JUnit 3 API in IgniteConfigVariationsAbstractTest

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8
• Fix Version/s: 2.8
• Labels: MakeTeamcityGreenAgain technical_debt
• Assignee: Oleg Ignatenko
• Reporter: Oleg Ignatenko
• Created: 19/Dec/18 11:04
• Updated: 25/Dec/18 09:14
• Resolved: 25/Dec/18 09:12

Description

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

Issue Links

• depends upon: IGNITE-10177 cleanup Junit 3 from the project
• is depended upon by: IGNITE-10758 remove from tests scaffolding annotations "@RunWith(JUnit4.class)" and their respective imports
• is related to: IGNITE-2521 Need to increase test coverage (support all configurations combinations)
• relates to: IGNITE-10776 Migrate from JUnit 3 to 4 config variations test suites
• links to: GitHub Pull Request #5715