Hello guys,

I have created KIP [1], with all the related details.

Cheers,
Maros

[1] -
https://cwiki.apache.org/confluence/spaces/KAFKA/pages/462816417/KIP-1393+Container-based+system+tests+with+JUnit+and+Testcontainers

pi 17. 4. 2026 o 16:09 Mickael Maison <[email protected]> napísal(a):

> Hi,
>
> I'd really be in favor of replacing our Python system test framework
> with something in Java.
>
> > How would the new framework handle these older compatibility tests?
>
> The tests for releases older than 3.7.0 will have to stay as is.
> We would need to have both frameworks in parallel.
>
> Even if this would not be changing any public APIs, we could do a KIP
> if we want to have a formal vote.
> But I wonder if more inputs from the community would be preferable
> first. Are there any features/behavior of ducktape or the current
> framework in general really important or liked?
>
> Thanks,
> Mickael
>
>
> On Thu, Apr 9, 2026 at 7:08 PM Chia-Ping Tsai <[email protected]> wrote:
> >
> > hi Maros
> >
> > Thanks for the proposal! Would you mind creating a KIP to describe the
> > details?
> >
> > > Version coverage is also narrower since the framework only targets
> KRaft
> > 3.9+
> >
> > I am a bit concerned about this since our testing baseline starts from
> 2.0.
> > For example, we still need to test Kafka 2.0 clients against 4.x servers.
> > How would the new framework handle these older compatibility tests?
> >
> > Best,
> > Chia-Ping
> >
> > Maroš Orsák <[email protected]> 於 2026年4月9日週四 下午5:53寫道:
> >
> > > Hello Kafka Devs,
> > >
> > > After years of working with Kafka system tests, I would like to propose
> > > moving them from Python/Ducktape to Java/Testcontainers, building on
> top of
> > > the @ClusterTest framework that contributors already know.
> > >
> > > The motivation is making system tests more effective and accessible for
> > > everyone. Instead of learning a second language and a niche test
> runner,
> > > contributors would write system tests the same way they write
> integration
> > > tests just with a different execution mode.
> > >
> > > The benefits include a single language and framework with reduced
> > > maintenance. Some tests also run significantly faster (e.g.,
> compression
> > > test dropped ~85s to ~12s), though that will not hold for every
> scenario.
> > >
> > > It is not without downsides. Ducktape can do things containers cannot
> > > (e.g.,
> > > real VM isolation, Kibosh fault injection, multi-host setups). Version
> > > coverage is also narrower since the framework only targets KRaft 3.9+,
> so
> > > ZooKeeper-based versions cannot be tested. This is deliberate (i.e.,
> KRaft
> > > has been production-ready since 3.6.0, and ZooKeeper mode was removed
> in
> > > 4.0, so investing in ZK-based test infrastructure isn't justified).
> Some
> > > tests will likely stay in Ducktape, and that is fine.
> > >
> > > If the community agrees this direction makes sense, I will follow up
> with
> > > the concrete details:
> > >
> > >
> > >    1. *which *tests can be migrated now,
> > >    2. *what *features @ClusterTest still needs,
> > >    3. *how *to wire up CI so both frameworks run from one place.
> > >
> > >  Looking forward to hearing your thoughts.
> > >
> > > Cheers,
> > >
> > > Maros
> > >
>

Reply via email to