[
https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665238#comment-15665238
]
Ismael Juma commented on KAFKA-4401:
------------------------------------
Kafka Streams also has helpers for tests that are nicer to use from Java
(EmbeddedKafkaCluster, KafkaEmbedded). If we want to encourage people to use
our test harness classes, we should think about compatibility guarantees. And
that implies exposing a simple and supportable interface instead
(IntegrationTestHarness and KafkaServerTestHarness expose too much IMO). Having
said that, I think it's a good idea, if done right.
> Change the KafkaServerTestHarness and IntegrationTestHarness from trait to
> abstract class.
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-4401
> URL: https://issues.apache.org/jira/browse/KAFKA-4401
> Project: Kafka
> Issue Type: Task
> Components: unit tests
> Affects Versions: 0.10.1.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.10.1.1
>
>
> The IntegartionTestHarness and KafkaServerTestHarness are useful not only in
> Kafka unit test, but also useful for the unit tests in other products that
> depend on Kafka.
> Currently there are two issues making those two test harness classes hard to
> use by other Java users.
> 1. The two classes are Scala traits. This makes it difficult for people to
> write Java unit test code.
> 2. Some of the interfaces are Scala only.
> It will be good to expose those two classes for more general usage and make
> them Java friendly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
