[
https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657699#action_12657699
]
Hemanth Yamijala commented on HADOOP-4901:
------------------------------------------
bq. It would be nice to be able to categorize tests into 1 or more categories
(smoke, nightly, dfs, mapred, etc).
+1. We have been seeing bug reports of tests taking a long time to run. These
have all been correct reports so far because the tests were inefficient and
hence could be fixed. But I suspect there might be legitimate cases in future
where some tests will actually require a longer time to run and we want them as
part of the automated test suite. For eg we are trying to enhance capacity
scheduler test cases to start using the MiniMRCluster. The objective of these
tests is to test the capacity scheduler along with the JobTracker, above and
beyond unit tests for the scheduler itself. Clearly these need not be run for
every patch submitted to Hudson, but maybe once every day or so. That way, you
could add long running tests without incurring overhead per patch.
Any new test framework that would allow this flexibility would be great to have
!
> 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: Tom White
>
> 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.
