hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4901) Upgrade to JUnit 4
Date Thu, 04 Jun 2009 13:51:07 GMT

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

Steve Loughran commented on HADOOP-4901:
----------------------------------------

a lot of the tests are a bit weak on releasing the miniMR clusters on failure. As long as
everything works, nobody notices, but when a test fails, the clusters hang around. 
It's that cluster setup/teardown that causes a lot of the tests to be slow -if teardown could
be asynchronous, maybe even with queued creation of MiniMRClusters, things could be faster.

> 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.


Mime
View raw message