[
https://issues.apache.org/jira/browse/AVRO-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated AVRO-81:
-----------------------------------
Attachment: AVRO-81.patch
This patch takes care about reverse conversion of the tests to JUnit framework.
However, the following problem has been found and I haven't find the
explanation yet:
- in TestValidatingIO 81 out of 960 are failing with messages like this
{noformat}
Testcase: testMain[8] took 0.004 sec
FAILED
expected:<[...@17cd7867> but was:<[...@329bbe66>
junit.framework.AssertionFailedError: expected:<[...@17cd7867> but
was:<[...@329bbe66>
at org.apache.avro.io.TestValidatingIO.check(TestValidatingIO.java:377)
at org.apache.avro.io.TestValidatingIO.check(TestValidatingIO.java:308)
at
org.apache.avro.io.TestValidatingIO.testOnce(TestValidatingIO.java:71)
at
org.apache.avro.io.TestValidatingIO.testMain(TestValidatingIO.java:61)
{noformat}
Also, an extra test class TestResolvingIO_resolving has been created to
workaround the limitations of JUnit @Parameters solution, i.e. you can't have
more than one data provider per test class.
> Switch Avro's tests back to JUnit from current TestNG framework
> ---------------------------------------------------------------
>
> Key: AVRO-81
> URL: https://issues.apache.org/jira/browse/AVRO-81
> Project: Avro
> Issue Type: Test
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Attachments: AVRO-81.patch
>
>
> This issue has been opened in order to track possible future switch of
> testing framework for Avro. Currently it is based on TestNG, however because
> of a number of limitations this test framework is not likely to be used by
> any of Hadoop's subproject. Thus, Avro will have to be start using JUnit
> again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
