We have two composer tests tasks to run with antithesis:

• antithesis_replica_sets_basic_js_commands
• antithesis_sharding_basic_js_commands

Currently, these tasks are not being run in our daily antithesis runs as they were an experiment with minimal command coverage. The goal for the Replication team is to expend these tests to include more commands (see SERVER-123055, SERVER-122168 and SERVER-122173). But first we need to make these tests pass successfully with the existing commands.

Currently there are test failures related to how the test is written and how it handles errors. We should fix the test to handle those scenarios gracefully and run successfully.

Examples of current execution of these tests:

• antithesis_replica_sets_basic_js_commands
• antithesis_sharding_basic_js_commands

Setup failures are sometimes expected and will be ignored by the Build Baron team. But Antithesis Test Composer failures should indicate real issues. Currently they're failing due to mishandled connection strings and retryable errors not being caught properly. The sharding suite can't execute any command at the moment, since the client doesn't recognize the URI we're passing in to connect to the mongos instances.

Once these fixes are done, we should probably enable these two tasks in our daily "MongoDB Core Server" runs. If we do that we need to remove these TODOs: here and here.

Doc on composer tests in antithesis. To ask questions: #ext-antithesis-mongodb