[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10177:
Fix Version/s: 2.8
> 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
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps for various reasons:
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> ## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
> starts failing after move to JUnit 4
> ## IgniteCachePartitionedQuerySelfTest,
> IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
> CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
> GridPartitionedCacheJtaLookupClassNameSelfTest,
> GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
> these at IGNITE-10176)
> ## find out why tests in logging suite failed on teamcity (not locally) when
> setup method was annotated {{@Before}}
> ## (!) note part of this work related to
> {{IgniteConfigVariationsAbstractTest}} is expected to be done separately per
> IGNITE-10739
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> (i) per discussion with [~EdShangGG] plan to to do this in a separate
> ticket for smoother merges - IGNITE-10758
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
## find out why tests in logging suite failed on teamcity (not locally) when
setup method was annotated {{@Before}}
## (!) note part of this work related to
{{IgniteConfigVariationsAbstractTest}} is expected to be done separately per
IGNITE-10739
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(i) per discussion with [~EdShangGG] plan to to do this in a separate ticket
for smoother merges - IGNITE-10758
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
## find out why tests in logging suite failed on teamcity (not locally) when
setup method was annotated {{@Before}}
## (!) note part of this work related to
{{IgniteConfigVariationsAbstractTest}} is expected to be done separately per
IGNITE-10739
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
## find out why tests in logging suite failed on teamcity (not locally) when
setup method was annotated {{@Before}}
## (!) note part of this work related to
{{IgniteConfigVariationsAbstractTest}} is expected to be done separately per
IGNITE-10739
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
## find out why tests in logging suite failed on teamcity (not locally) when
setup method was annotated {{@Before}}
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
## find out why tests in logging suite failed on teamcity (not locally) when
setup method was annotated {{@Before}}
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps for various reasons:
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps for various reasons:
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
## IgniteCachePartitionedQuerySelfTest,
IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
GridPartitionedCacheJtaLookupClassNameSelfTest,
GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
these at IGNITE-10176)
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps for various reasons:
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> ## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
> starts failing after move to JUnit 4
> ##
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
starts failing after move to JUnit 4
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps, if there are any
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> ## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
> starts failing after move to JUnit 4
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> (per discussion with [~EdShangGG] it looks more convenient to do
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps, if there are any
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> (per discussion with [~EdShangGG] it looks more convenient to do this in a
> separate ticket for smoother merges)
> 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
>
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# execute junit related inspections of IDE and analyse results
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps, if there are any
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# execute junit related inspections of IDE and analyse results
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# review and if possible upgrade all occurrences of {{import org.junit}} in the
project
# execute junit related inspections of IDE and analyse results
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
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> # find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> # execute junit related inspections of IDE and analyse results
> 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
>
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# review and if possible upgrade all occurrences of {{import org.junit}} in the
project
# execute junit related inspections of IDE and analyse results
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# review and if possible upgrade all occurrences of {{import org.junit}} in the
project
# execute junit related inspections of IDE and analyse results
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.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> # find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> # review and if possible upgrade all occurrences of {{import org.junit}} in
> the project
> # execute junit related inspections of IDE and analyse results
> 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
>
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# review and if possible upgrade all occurrences of {{import org.junit}} in the
project
# execute junit related inspections of IDE and analyse results
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# review and if possible upgade all occurrences of {{import org.junit}} in the
project
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.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> # review and if possible upgrade all occurrences of {{import org.junit}} in
> the project
> # execute junit related inspections of IDE and analyse results
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
# review and if possible upgade all occurrences of {{import org.junit}} in the
project
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
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.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> # review and if possible upgade all occurrences of {{import org.junit}} in
> the project
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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.
# remove deprecated API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven
# migrate tests that were missed at prior steps, if there are any
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}} to
add the class via Junit4 adapter
# find and update all Junit3-specific code that {{extends TestCase}}
# untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass which
currently conflict with Junit4 execution because of using constructors and make
them properly use {{@Test}} annotation
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}} 6) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
and update all Junit3-specific code that {{extends TestCase}}
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.
> # remove deprecated API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven
> # migrate tests that were missed at prior steps, if there are any
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # check and adjust if needed methods like {{GridTestUtils.addTestIfNeeded}}
> to add the class via Junit4 adapter
> # find and update all Junit3-specific code that {{extends TestCase}}
> # untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
and update all Junit3-specific code that {{extends TestCase}}
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}} 6) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
and get rid of all code that {{extends TestClass}}
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) check and adjust if needed methods like
> {{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
> and update all Junit3-specific code that {{extends TestCase}}
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
and get rid of all code that {{extends TestClass}}
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}} 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 7) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 8) find
and get rid of all code that {{extends TestClass}}
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) check and adjust if needed methods like
> {{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 7) find
> and get rid of all code that {{extends TestClass}}
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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 7) check and adjust if needed methods like
{{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 8) find
and get rid of all code that {{extends TestClass}}
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}} 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.
> 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 7) check and adjust if needed methods like
> {{GridTestUtils.addTestIfNeeded}} to add the class via Junit4 adapter 8) find
> and get rid of all code that {{extends TestClass}}
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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}}
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 {{@RunWith(AllTests.class)}}
> 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}}
> 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)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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 {{@RunWith(AllTests.class)}}
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)}})
> 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 {{@RunWith(AllTests.class)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
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)}})
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
> 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)}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[ https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko updated IGNITE-10177: Ignite Flags: (was: Docs Required) > 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
