Update of unit tests to use KRaft - part 6 #10436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
Part 6 of the unit test refactoring to use KRaft:
KafkaAssemblyOperatorCustomCertMockTest
is not dependent on ZooKeeper in any way and was just updated to use KRaftKafkaAssemblyOperatorNodePoolWatcherTest
is not dependent on ZooKeeper in any way and was just updated to use KRaftKafkaAssemblyOperatorManualRollingUpdatesTest
used ZooKeeper. The original class was kept in a copy asKafkaAssemblyOperatorManualRollingUpdatesZooBasedTest
and theKafkaAssemblyOperatorManualRollingUpdatesTest
class itself was updated to use KRaftKafkaAssemblyOperatorNonParametrizedTest
used ZooKeeper in some tests. The original classKafkaAssemblyOperatorNonParametrizedTest
has been used to keep the tests that did not need ZooKeeper based clusters. A new classKafkaAssemblyOperatorNonParametrizedZooBasedTest
was created to hols the ZooKeeper related tests (this class will be removed when ZooKeeper support is removed).Checklist