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
As a test developer I need to have a working Kafka instance. While I do not need direct access to that instance, it should be available for integration with other Hadoop components.
I want to be able to configure the Kafka instance by means of annotating the test class.
When running tests in parallel, I want the system to not start multiple Kafka instances for a specific test class or a suite of test classes that derive from a common super class which provides the Kafka configuration. Instead, all of these threads must share the same instance. In effect, there is only one Kafka instance that is shared across all threads.
Running the same tests on the same system from multiple processes must not lead to failing tests. Individual instances of Kafka must have their own ports. The ports must be determined automatically.
In addition I want to be able to access both Consumers and Producers by means of both parameter and field injection where there is also an Annotation present for configuring either the Consumer or the Producer. The annotation must allow me to at least define the topic.
In addition I want to be able to purge a given topic from all events or altogether drop a specific topic before or after each test or before all or after all tests in a specific test class, or populate it with a fixed number of of events.
Acceptance criteria
Kafka is provided
Kafka instances can be configured via annotation on ElementType.TYPE level
There is only one Kafka instance that is shared across multiple threads
The effective Kafka instance configuration is used for configuring other provided components
Kafka instances use dedicated free ports that have been determined automatically
Generic Producers and Consumers can be injected into both fields and parameters
Generic Producers and Consumers can be configured via Annotation
Purging events from a given topic is possible
Dropping topics is possible
Topics are purged and removed automatically after all tests have been run for a specific test class
The text was updated successfully, but these errors were encountered:
As a test developer I need to have a working Kafka instance. While I do not need direct access to that instance, it should be available for integration with other Hadoop components.
I want to be able to configure the Kafka instance by means of annotating the test class.
When running tests in parallel, I want the system to not start multiple Kafka instances for a specific test class or a suite of test classes that derive from a common super class which provides the Kafka configuration. Instead, all of these threads must share the same instance. In effect, there is only one Kafka instance that is shared across all threads.
Running the same tests on the same system from multiple processes must not lead to failing tests. Individual instances of Kafka must have their own ports. The ports must be determined automatically.
In addition I want to be able to access both Consumers and Producers by means of both parameter and field injection where there is also an Annotation present for configuring either the Consumer or the Producer. The annotation must allow me to at least define the topic.
In addition I want to be able to purge a given topic from all events or altogether drop a specific topic before or after each test or before all or after all tests in a specific test class, or populate it with a fixed number of of events.
Acceptance criteria
The text was updated successfully, but these errors were encountered: