Motivation

...

The community is informed about the migration to 5 and benefits of the newest version.

Additional improvements

...

in JUnit 3->4 migration.

Actualize JUnit3TestLegacyAssertclassJUnit3TestLegacyAssert class: rename classit, update documentation. Replacement inheritance to imports is not appropriate here as it leads to changes of all test classes. Moreover, during migration to the next JUnit versions, problem with changing all test classes wil will arrise again and in new test classes developer should make import manually.

In JUnit3TestLegacySupport:

1. Investigate replacement of beforeTest/afterTest and beforeTestsStarted/afterTestsStopped methods and if needed replace them by annotations - it is noticed in IGNITE-11413.
2. Replace tearDown, setUp by beforeTest, afterTest methods where it is necessary.
3. Actualize JUnit3TestLegacySupport: remove deprecated annotation, rename class and specify documentation.Investigate replacement of beforeTest/afterTest and beforeTestsStarted/afterTestsStopped methods and if needed replace them by annotations - it is noticed in IGNITE-11413.

Futhermore, GridAbstractTest and GridCommonAbstractTest refactoring necessity should be investigated. Check ability to turn some instance methods to static methods. It was mentioned in the conversation on dev-list.

...