[KAFKA-17587] Move test infrastructure out of core

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: core
• Assignee: Unassigned
• Reporter: David Arthur
• Created: 20/Sep/24 20:20
• Updated: 26/Sep/24 08:38

Description

Currently, our integration test infrastructure exists in the ":core" module's test sources. This means that any integration test must exist in "core/src/test/java" or "core/src/test/scala". 

This has two negative consequences. First, it means most of our integration tests live in "core" which is why that module's test time is by far the highest. The other related problem is that modules cannot easily define integration tests in their directory due to circularity with the core test dependency. 

For example, ":metadata" could not add ClusterTests because that would require a dependency on "project(':core').sourceSets.test.output" – but this can't happen because ":core" depends on ":metadata".

We should refactor our test infrastructure classes so that we can untangle these dependencies.

Issue Links

• relates to: KAFKA-17619 Remove zk type and instance from ClusterTest

Sub-Tasks

• Remove internal classes from ClusterInstance: Open
• Move JUnit extensions to test-common module: Resolved