Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <635332570.1243616925777.JavaMail.jira@brutus>
Date: Fri, 29 May 2009 10:08:45 -0700 (PDT)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4901) Upgrade to JUnit 4
In-Reply-To: <1370926570.1229519504690.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714514#action_12714514 ] 

Konstantin Boudnik commented on HADOOP-4901:
--------------------------------------------

Or we can start using testng to run JUnit tests natively and migrate them to 
'native' TestNG format eventually. There's a couple of benefits which JUnit 
doesn't have. E.g.
   - parallel tests execution
   - sameVM execution (without forking)
   - absence of mandatory TestCase's inheritance which limits the options of 
test developers.

With regards,
   Cos


> Upgrade to JUnit 4
> ------------------
>
>                 Key: HADOOP-4901
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4901
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: test
>            Reporter: Tom White
>            Assignee: Alex Loddengaard
>
> Amongst other things, JUnit 4 has better support for class-wide set up and tear down (via @BeforeClass and @AfterClass annotations), and more flexible assertions (http://junit.sourceforge.net/doc/ReleaseNotes4.4.html). It would be nice to be able to take advantage of these features in tests we write.
> JUnit 4 can run tests written for JUnit 3.8.1 without any changes.

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