Antithesis engagement with correctness testing

[serathius]

What would you like to be added?

For some time etcd maintainers have been in contact with https://antithesis.com/ a company offering a deterministic execution environment perfect for testing distributed systems like etcd. This could work as a complementary to existing robustness test that validate etcd correctness under stress and failure, but struggle with reproducibility. Why not combine both approaches and have 100% reproducible correctness tests?

Linux Foundation has offered to sponsor a 3 month engagement to see how much we can achieve by combining efforts community and awesome software build by Antithesis. We are on finals steps of legal contract signing, with planned start on February 14.

I'm looking for people interested in helping integrate robustness tests with Antithesis. The first goal would be to setup etcd

Materials:

• https://www.antithesis.com/docs/test_templates/test_composer_reference/
• https://www.antithesis.com/docs/test_templates/first_test/
• https://github.com/guergabo/quickstarts
• https://github.com/antithesishq/etcd-test-composer

/cc @MadhavJivrajani @fuweid @siyuanfoundation @henrybear327 @AwesomePatrol @jmhbnz @wenjiaswe

Why is this needed?

Provide 100% reproducible robustness tests

[aladesawe]

I'm interested

[fuweid]

+1 to help!

[siyuanfoundation]

+1 to help!

[serathius]

Thanks for interest, please read the linked Antithesis documentation and see https://github.com/antithesishq/etcd-test-composer/tree/main/test-template/main as example of integrating linearization. Hopefully we will get confirmation that we can start by the end of the week.

[serathius]

Got an update from Antithesis team, agreement is on final stage and we expect the engagement to start next week.

First thing that we need to do on etcd side is to agree on location where the work should be done.
I would like to propose to keep the code within the main etcd repository to allow us to iterate fast on integrating it with robustness libraries. The antithesis specific code should be separated in it's own directory tests/anthithesis.

cc @ahrtr @jmhbnz @fuweid @ivanvc for opinion.