[
https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10177:
------------------------------------
Description:
If needed, refer parent task for more details.
1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
there are any (like in {{@RunWith(JUnit4.class)}}) 5) in tests suite classes,
change {{extends TestSuite}} to either {{@RunWith(AllTests.class)}} or
{{@Suite.SuiteClasses}} 6) use
[Ignore|http://junit.sourceforge.net/javadoc/org/junit/Ignore.html] to annotate
empty test classes in examples that were discovered and re-muted per
IGNITE-10174
Side note if for some reason it turns out critically important to keep test
suites names (by default Junit 4 will use suite class names instead), approach
with custom description annotation [described
here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
can be used to address that.
was:
If needed, refer parent task for more details.
1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
there are any (like in {{@RunWith(JUnit4.class)}}) 5) in tests suite classes,
change {{extends TestSuite}} to either {{@RunWith(AllTests.class)}} or
{{@Suite.SuiteClasses}}
Side note if for some reason it turns out critically important to keep test
suites names (by default Junit 4 will use suite class names instead), approach
with custom description annotation [described
here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
can be used to address that.
> cleanup Junit 3 from the project
> --------------------------------
>
> Key: IGNITE-10177
> URL: https://issues.apache.org/jira/browse/IGNITE-10177
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Oleg Ignatenko
> Priority: Major
>
> If needed, refer parent task for more details.
> 1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
> dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
> steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
> there are any (like in {{@RunWith(JUnit4.class)}}) 5) in tests suite classes,
> change {{extends TestSuite}} to either {{@RunWith(AllTests.class)}} or
> {{@Suite.SuiteClasses}} 6) use
> [Ignore|http://junit.sourceforge.net/javadoc/org/junit/Ignore.html] to
> annotate empty test classes in examples that were discovered and re-muted per
> IGNITE-10174
> Side note if for some reason it turns out critically important to keep test
> suites names (by default Junit 4 will use suite class names instead),
> approach with custom description annotation [described
> here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
> can be used to address that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
