[
https://issues.apache.org/jira/browse/OOZIE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon updated OOZIE-3475:
----------------------------------
Description:
OOZIE-783 upgraded JUnit 3 to JUnit 4 years ago, but most of out unit tests
still use JUnit 3 style.
The following counting is not perfect, but shows the approximate numbers:
{noformat}
$ find . -name "Test*.java" | wc -l
491
$ find . -name "Test*.java" | xargs grep 'extends.*TestCase' -l | wc -l
346
{noformat}
Although there are ways to
[automagically|https://stackoverflow.com/q/264680/21348] convert the tests, I
don't think we can skip the manual work.
I open this umbrella jira (similarly to OOZIE-3111) so at least we are aware of
the problem. We need to solve it in batches.
was:
OOZIE-783 upgraded JUnit 3 to JUnit 4 years ago, but most of out unit tests
still use JUnit 3 style.
The following counting is not perfect, but shows the approximate numbers:
{noformat}
$ find . -name "Test*.java" | wc -l
491
$ find . -name "Test*.java" | xargs grep 'extends.*TestCase' -l | wc -l
346
{noformat}
Although there are ways to
[automagically|https://stackoverflow.com/q/264680/21348] convert the tests, I
don't think we can skip the manual work.
I open this umbrella jira (similarly to OOZIE-3111) so at least we are aware of
the problem.
> [Umbrella] Migrate junit tests from JUnit 3 to JUnit 4
> ------------------------------------------------------
>
> Key: OOZIE-3475
> URL: https://issues.apache.org/jira/browse/OOZIE-3475
> Project: Oozie
> Issue Type: Task
> Reporter: Andras Salamon
> Priority: Major
>
> OOZIE-783 upgraded JUnit 3 to JUnit 4 years ago, but most of out unit tests
> still use JUnit 3 style.
> The following counting is not perfect, but shows the approximate numbers:
> {noformat}
> $ find . -name "Test*.java" | wc -l
> 491
> $ find . -name "Test*.java" | xargs grep 'extends.*TestCase' -l | wc -l
> 346
> {noformat}
> Although there are ways to
> [automagically|https://stackoverflow.com/q/264680/21348] convert the tests, I
> don't think we can skip the manual work.
> I open this umbrella jira (similarly to OOZIE-3111) so at least we are aware
> of the problem. We need to solve it in batches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)