Geoffrey, This looks great!
A few questions. 1. Will ducktape be maintained separately as a github repo? 2. How easy is viewing the test results and logs. The link in KIP, http://testing.confluent.io/confluent_platform/latest/, lists a bunch of files and dirs. Could you add to KIP how the result and logs for the tests will be organized. 3. Does it support code coverage? If not, how easy/ difficult would it be? On Thu, May 21, 2015 at 2:03 PM, Geoffrey Anderson <ge...@confluent.io> wrote: > Great, I'll work on putting together a more detailed map of this > replacement process. > > On Thu, May 21, 2015 at 11:13 AM, Gwen Shapira <gshap...@cloudera.com> > wrote: > > > Love this idea :) > > > > I took a look at Ducktape API and it looks like a good fit - clean API, > > extensible, easy to use and powerful enough for our use-case. > > > > Something I'd like to see as part of the KIP is a map of what system-test > > currently tests, which ones we want to replace and a JIRA for replacing > > (possibly one for each group of tests). > > Basically, I know we all want to use the new system for new test cases > > (upgrades, etc), but I really want to make sure we don't get stuck with > > both systems forever. > > > > Gwen > > > > On Thu, May 21, 2015 at 9:01 PM, Geoffrey Anderson <ge...@confluent.io> > > wrote: > > > > > Hi, > > > > > > Just kicking off the discussion thread on KIP-25 > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP+-+25+System+test+improvements > > > > > > Thanks, > > > Geoff > > > > > > -- Regards, Ashish
