You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "nkeywal (JIRA)" <ji...@apache.org> on 2013/03/12 10:13:13 UTC

[jira] [Commented] (HBASE-4955) Use the official versions of surefire & junit

    [ https://issues.apache.org/jira/browse/HBASE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599849#comment-13599849 ] 

nkeywal commented on HBASE-4955:
--------------------------------

The regression in SUREFIRE-970 makes the move to 2.14 problematic. It would be nice to have SUREFIRE-969 as well bu it's more mandatory. A bigger issue is that in my tests it seems that having multiple execution with different parameters does not work anymore. I will need to have a look at that to get it fixed in a release...
                
> Use the official versions of surefire & junit
> ---------------------------------------------
>
>                 Key: HBASE-4955
>                 URL: https://issues.apache.org/jira/browse/HBASE-4955
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.94.0
>         Environment: all
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>             Fix For: 0.95.0
>
>         Attachments: 4955.v1.patch, 4955.v2.patch, 4955.v2.patch
>
>
> We currently use private versions for Surefire & JUnit since HBASE-4763.
> This JIRA traks what we need to move to official versions.
> Surefire 2.11 is just out, but, after some tests, it does not contain all what we need.
> JUnit. Could be for JUnit 4.11. Issue to monitor:
> https://github.com/KentBeck/junit/issues/359: fixed in our version, no feedback for an integration on trunk
> Surefire: Could be for Surefire 2.12. Issues to monitor are:
> 329 (category support): fixed, we use the official implementation from the trunk
> 786 (@Category with forkMode=always): fixed, we use the official implementation from the trunk
> 791 (incorrect elapsed time on test failure): fixed, we use the official implementation from the trunk
> 793 (incorrect time in the XML report): Not fixed (reopen) on trunk, fixed on our version.
> 760 (does not take into account the test method): fixed in trunk, not fixed in our version
> 798 (print immediately the test class name): not fixed in trunk, not fixed in our version
> 799 (Allow test parallelization when forkMode=always): not fixed in trunk, not fixed in our version
> 800 (redirectTestOutputToFile not taken into account): not yet fix on trunk, fixed on our version
> 800 & 793 are the more important to monitor, it's the only ones that are fixed in our version but not on trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira