+1 (non-binding. Actually, since this is non-binding anyway, lets make it +100. I'm so so excited about having a usable testing framework)
On Wed, Jun 10, 2015 at 6:10 PM, Geoffrey Anderson <ge...@confluent.io> wrote: > Hi Kafka, > > After a few rounds of discussion on KIP-25, there doesn't seem to be > opposition, so I'd like to propose a vote. > > Thanks, > Geoff > > On Mon, Jun 8, 2015 at 10:56 PM, Geoffrey Anderson <ge...@confluent.io> > wrote: > >> Hi KIP-25 thread, >> >> I consolidated some of the questions from this thread and elsewhere. >> >> Q: Can we see a map of what system-test currently tests, which ones we >> want to replace and JIRAs for replacing? >> A: Initial draft here: >> https://cwiki.apache.org/confluence/display/KAFKA/Roadmap+-+port+existing+system+tests >> >> Q: Will ducktape be maintained separately as a github repo? >> A: Yes https://github.com/confluentinc/ducktape >> >> Q: How easy is viewing the test results and logs, how will test output be >> structured? >> A: Hierarchical structure as outlined here: >> https://github.com/confluentinc/ducktape/wiki/Design-overview#output >> >> Q: Does it support code coverage? If not, how easy/ difficult would it be >> to support? >> A: It does not, and we have no immediate plans to support this. Difficulty >> unclear. >> >> Q: It would be nice if each Kafka version that we release will also >> have a separate "tests" artifact that users can download, untar and easily >> run against a Kafka cluster of the same version. >> A: This seems reasonable and not too much extra work. Definitely open to >> discussion on this. >> >> Q: Why not share running services across multiple tests? >> A: Prefer to optimize for simplicity and correctness over what might be a >> questionable improvement in run-time. >> >> Q: Are regressions - in the road map? >> A: yes >> >> Q: Are Jepsen style tests involving network failures in the road map? >> A: yes >> >> Thanks much, >> Geoff >> >> >>
