You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2009/05/04 19:24:30 UTC

[jira] Issue Comment Edited: (AVRO-26) Converting JUnit tests into TestNG controlled environment

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

Konstantin Boudnik edited comment on AVRO-26 at 5/4/09 10:24 AM:
-----------------------------------------------------------------

This patch includes the following modifications:
  - JUnit tests conversion to be naively executed by TestNG. This involves new annotations and inter tests dependencies introduction
  - some of test files for schemata were renamed and affected Java and Python code has been refactored accordingly 
  - build.xml file is modified to accommodate TestNG switch
    - an extra target 'reports' has been added to facilitate conversion of the reports produced by testng into junit format
  - import lists are optimized for all test classes for they included too much of unused imports which made tests refactoring difficult
  - new library is added  to lib/testng-5.9-jdk15.jar

Tests invocation remain the same: it could be executed either through 'test' for all languages or through 'test-java' for java. Interop test interfaces are remained as before too.

      was (Author: cos):
    This patch includes the following modifications:
  - JUnit tests conversion to be naively executed by TestNG. This involves new annotations and inter tests dependencies introduction
  - some of test files for schemata were renamed and affected Java and Python code has been refactored accordingly 
  - build.xml file is modified to accommodate TestNG switch
  - import lists are optimized for all test classes for they included too much of unused imports which made tests refactoring difficult
  - new library is added  to lib/testng-5.9-jdk15.jar

Tests invocation remain the same: it could be executed either through 'test' for all languages or through 'test-java' for java. Interop test interfaces are remained as before too.
  
> 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
>
>
> 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.