[ https://issues.apache.org/jira/browse/HADOOP-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788297#action_12788297 ]
Stephen Watt commented on HADOOP-6332: -------------------------------------- Great discussion. Kos, et al.. do you think we are at point where we can consider starting to write some code ? Another thing we need to do is identify which of the functional tests we are going to port. 12/11 is my last day but I will be back on 1/4. Not sure how much run way we have before 0.21 is due but I'd like to see if we can at least have the framework plus a couple of tests available in time for the release. > Large-scale Automated Test Framework > ------------------------------------ > > Key: HADOOP-6332 > URL: https://issues.apache.org/jira/browse/HADOOP-6332 > Project: Hadoop Common > Issue Type: New Feature > Components: test > Reporter: Arun C Murthy > Assignee: Arun C Murthy > Fix For: 0.21.0 > > Attachments: 6332_v1.patch > > > Hadoop would benefit from having a large-scale, automated, test-framework. > This jira is meant to be a master-jira to track relevant work. > ---- > The proposal is a junit-based, large-scale test framework which would run > against _real_ clusters. > There are several pieces we need to achieve this goal: > # A set of utilities we can use in junit-based tests to work with real, > large-scale hadoop clusters. E.g. utilities to bring up to deploy, start & > stop clusters, bring down tasktrackers, datanodes, entire racks of both etc. > # Enhanced control-ability and inspect-ability of the various components in > the system e.g. daemons such as namenode, jobtracker should expose their > data-structures for query/manipulation etc. Tests would be much more relevant > if we could for e.g. query for specific states of the jobtracker, scheduler > etc. Clearly these apis should _not_ be part of the production clusters - > hence the proposal is to use aspectj to weave these new apis to > debug-deployments. > ---- > Related note: we should break up our tests into at least 3 categories: > # src/test/unit -> Real unit tests using mock objects (e.g. HDFS-669 & > MAPREDUCE-1050). > # src/test/integration -> Current junit tests with Mini* clusters etc. > # src/test/system -> HADOOP-6332 and it's children -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.