You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the unit test is based on Kafka's test-utils package, but kafka-junit provides deeper support as it allows us to set up a mock broker with input/output topics that we can use. Update the existing unit test to use kafka-junit.
The text was updated successfully, but these errors were encountered:
williewheeler
changed the title
Create kafka-junit test for KafkaAnomalyDetectorMapper
Create kafka-junit test for KafkaAnomalyDetectorManager
Feb 19, 2019
Not so sure we want to do this after all. On a couple occasions I've run into seeming interactions between tests where disabling one kafka-junit test causes another one to fail:
Connection to node 1 could not be established. Broker may not be available.
This could easily be a matter of my inexperience with kafka-junit.
Might make more sense to use the Kafka Streams test framework, which doesn't spin up a broker, and save the broker stuff for integration tests.
Currently the unit test is based on Kafka's
test-utils
package, butkafka-junit
provides deeper support as it allows us to set up a mock broker with input/output topics that we can use. Update the existing unit test to usekafka-junit
.The text was updated successfully, but these errors were encountered: