incubator-kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Ormsbee (Commented) (JIRA)" <>
Subject [jira] [Commented] (KAFKA-217) Client test suite
Date Thu, 01 Dec 2011 23:20:40 GMT


David Ormsbee commented on KAFKA-217:

I like the packet dumps idea from a simplicity point of view. We could have a set of YAML
files that represent types of compliance (e.g. simpleconsumer_0.7.yaml), maybe even put the
message data in fields as base64 encoded strings. We don't have to worry about invoking clients
on the command line -- each client would just know to read the file and the file would specify
what the raw data is and the intended results. It also saves us from having to bring up older
versions of Kafka to live test against.

That being said, is there any simple way to test a ZooKeeper Consumer/Producer? The only thing
I can think of is to specify a standard command-line interface that clients need to implement,
and then have a test script that spins up ZooKeeper and a few Kafka brokers, calls these client
commands, and then inspects the output and the ZK state.
> Client test suite
> -----------------
>                 Key: KAFKA-217
>                 URL:
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jay Kreps
> It would be great to get a comprehensive test suite that we could run against clients
to certify them.
> The first step here would be work out a design approach that makes it easy to certify
the correctness of a client.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message