Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "SystemTestingConfCallSynopsis" page has been changed by SteveWatt. http://wiki.apache.org/hadoop/SystemTestingConfCallSynopsis?action=diff&rev1=1&rev2=2 -------------------------------------------------- * Deployment is a separate concern from Testing. Deployment is outside of the scope of this JIRA. Users will be responsible for setting up their cluster. * Deployment information is provided as a set of parameters (possibly environment variables) to the testing framework. * Create a 'Cluster QA' set of JUNIT based tests. Start by selecting several of the existing functional tests and port them to run over the cluster. - * Contain the tests inside a hadoop-version-test.jar (or alternatively separate jobs for each project split, i.e. mapred-test, hdfs-test etc.) + * Contain the tests inside a hadoop-version-test.jar (or alternatively separate jars for each project split, i.e. mapred-test, hdfs-test etc.) * Design the framework such that is able to take the parameters specified and run the tests in the test jar specified against the cluster identified. - * Once the cluster is running the tests could be run against the default cluster with something like : "bin/hadooop -verify" + * Once the cluster is running the tests could be run against the default cluster with something like : "bin/hadoop -verify" * Start collecting data on how long system tests (such as TeraSort) take to run on certain cluster configurations so we can provide users a benchmark they can use to validate the health of their cluster.
