avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-26) Converting JUnit tests into TestNG controlled environment
Date Wed, 06 May 2009 18:52:30 GMT

    [ https://issues.apache.org/jira/browse/AVRO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706554#action_12706554
] 

Doug Cutting commented on AVRO-26:
----------------------------------

A few comments on the latest patch:
  - we should remove lib/junit*.jar
  - TestValueReader has not yet been converted to testng
  - please attach a shell script, AVRO-26.sh, that can be run before the patch is applied
to perform any 'svn mv' and 'svn rm' operations required
  - please attach the testng jar too.
  - in build.xml, the  taskdef can be moved outside the target to top-level and then need
not be repeated.  (we should eventually similarly fix the py-* taskdefs.)

> Converting JUnit tests into TestNG controlled environment
> ---------------------------------------------------------
>
>                 Key: AVRO-26
>                 URL: https://issues.apache.org/jira/browse/AVRO-26
>             Project: Avro
>          Issue Type: Test
>          Components: java, python
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>         Attachments: AVRO-26.patch.1, AVRO-26.patch.2, AVRO-26.patch.3
>
>
> TestNG is a powerful test harness, which provides a lot of useful features like parallel
test execution, test parametrization, and such.
> Avro uses JUnit environment instead which is more rigid and less efficient.
> I'd suggest to convert Avro's Junit based test infrastructure into TestNG controller
environment, which will allow to achieve higher level of test execution control in the long
run

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message