Hi all 👋 — I've been writing a lot of Kafka/JDBC/HTTP connector tests for Flink jobs and kept rewriting the same Testcontainers wiring + polling-for-results boilerplate, so I put together a small JUnit 5 harness for it: flink-testkit (github.com/bharathgunapati/flink-testkit). Rough idea:

@KafkaTopic

/

@JdbcTable

/

@HttpEndpoint

on a typed static field gives you a handle for seeding data, awaiting outcomes (by count or predicate, no fixed sleeps), and getting the connection info to configure your job — one declaration instead of separate container/topic/consumer-group setup per test. It's early (v0.0.1, tested against Flink 1.19/1.20, HTTP examples on 2.2) and I'd genuinely like feedback before going further: - Is this solving a real pain point for people here, or do most of you already have this solved in-house? - Anything obviously missing for it to be useful (other connectors, other patterns)? - Any concerns with the approach itself? Not trying to replace Testcontainers or anyone's existing setup — just curious if this is useful to anyone outside my own projects. Any feedback would be appreciated.