Proposed commit message

Use a shared helper that creates and waits for a test topic to become writable before producing events. Apply it across kafka integration tests, including TestTest, to reduce leader-election race flakes.

GenAI-Assisted: Yes
Human-Reviewed: Yes
Tool: GitHub Copilot CLI, Model: GPT-5.3 Codex

Summary

• add createReadyTestTopic(t) to centralize kafka test-topic setup and readiness waiting
• switch kafka input integration tests to use this helper before producing events
• include TestTest and the other topic-writing tests so they all avoid leader-election write races consistently

Why

TestTest flake reports show transient no leader for this partition write errors. Other tests in the same file had the same write-on-fresh-topic pattern; this change applies the readiness guard uniformly.

Validation

• go test -tags=integration ./filebeat/input/kafka -run '^(TestInput|TestInputWithMultipleEvents|TestInputWithJsonPayload|TestInputWithJsonPayloadAndMultipleEvents|TestSASLAuthentication|TestTest)$' -count=1 -v

  • fails in this runner because Kafka test services are not running (connect: connection refused on localhost:9094), but the modified code path compiles and executes until environment connection.

• Fixes [Flaky Test] Kafka TestTest: kafka server: In the middle of a leadership election, there is currently no leader for this partition and hence it is unavailable for writes #49206

What is this? | From workflow: Mention in Issue

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.