+1 Sounds very nice. You going to script the running of the wiki content DD?
You see any overlap with the effort at getting hbase-it tests run on a continual basis, the stuff discussed here [1] and here [2] (currently a little stalled till we figure the failed hbase-it test), or as you see it, the two efforts compliment each other (which seems to be the case)? Good stuff, St.Ack 1. http://search-hadoop.com/m/6bg8O1ZB7nr&subj=Re+Move+TestReplication+out+of+LargeTests+into+hbase+it+instead+(see about 2/3rds down the thread) 2. http://mail-archives.apache.org/mod_mbox/hbase-dev/201212.mbox/%3ccadcmmgg0b-oyi10xruut87uxhard7od9wu5cykxih4samp4...@mail.gmail.com%3E On Wed, Jan 30, 2013 at 10:07 PM, Devaraj Das <d...@hortonworks.com> wrote: > Hi folks, > > Have been toying with the idea of automating the process of running > the tests that constitute the release test plan (the initial tests > would be from > https://docs.google.com/spreadsheet/ccc?key=0AvLqcVIqNtlTdE9iemw2STVmWHFVMVVNY2JvZ0NwZGc#gid=0 > , > and they would be run with/without security turned on in the cluster). > As we continue to develop more system/largescale tests, we would keep > adding them to the harness. > > I have set the ball rolling on this within the company and I hope the > community will be interested in seeing such a thing happen. > > The idea is to be able to easily run a release artifact through a > series of tests (on our internal cluster or on AWS), and the result > would be published in a machine on AWS (visible to all). In the > future, this could be extended to run the tests on trunk artifacts as > well (catch regressions early). > > Thoughts? > > Thanks, > Devaraj. >
