Patch AVRO-26.patch.6 and updated AVRO-26.sh are attached to the JIRA.
Patch was applied to the fresh copy of the trunk and then all tests were
passed.

Please review and commit at will.
Thanks,
  Cos

On Wed, May 13, 2009 at 10:57AM, Konstantin Boudnik (JIRA) wrote:
> 
>     [ 
> https://issues.apache.org/jira/browse/AVRO-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709028#action_12709028
>  ] 
> 
> Konstantin Boudnik commented on AVRO-26:
> ----------------------------------------
> 
> Will merge these in a second: I felt like sending them separately in order to
> present them separately. And renaming them totally makes sense.
> 
> Wrt placement of the classes: shall we pull them off avro at all, so other
> projects which will be coming toward testng harness will be able to reuse
> them? Say, org.apache.hadoop.common.test ?
> 
> I'd vote for System.out - these are normal reporting output. System.err is
> left there as a result of some previous experimenting. Will be gone in the
> coming patch.
> 
> Thanks,
>   Cos
> 
> 
> 
> > 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, 
> > AVRO-26.patch.4, AVRO-26.patch.5, AVRO-26.sh, testng-5.9-jdk15.jar
> >
> >
> > 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.
> 

Reply via email to