[
https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716139#action_12716139
]
Konstantin Boudnik commented on HADOOP-4901:
--------------------------------------------
Adding on the same topic. I've investigated JUnit4 more closely and while this
new version is getting much more advanced compare to the old one, it is still
lacking a number of features provided by TestNG. It seems that even grouping is
somehow supported now, alas TestNG feature is a way more complex and flexible.
Here I've found pretty good comparison between the latest versions of the
harnesses:
http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/
Obviously, the decision about such switching from one harness to another has to
be made based on an actual set of feature the project uses or will be using in
the feature.
>From a personal experience, I could say that such a conversion might take
>quite an effort if a project's tests have a heavy JUnit legacy such careless
>resources allocation/release and similar things.
> 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.
