Although today it is possible for a JS Core test suite to instantiate a ShardedClusterFixture with multiple mongos, it is not possible for a test file to interact with the cluster through more than a single connection.

This potentially limits the test coverage guaranteed today and it represents a blocker for writing explicit test cases about the behavior of mongos nodes with stale routing information.

Such gaps could be addressed by:

• (in general) allow test cases to round-robin through the existing mongos processes
• (exclusively to support the validation of stale routing information) allow to programmatically connect to multiple specific mongos instances