There are a number of tests (47 at the time this ticket is being created) that fail when run against a cluster with a single mongos.

To reproduce start a cluster with mlaunch like this:

mlaunch init --sharded 1 --replicaset --nodes 1 --mongos 1 --binarypath C:\mongodb\v5.0.3\bin --setParameter enableTestCommands=true

which results in the following cluster configuration:

PS C:\mlaunch\v5.0.3\sharded> mlaunch list

PROCESS          PORT     STATUS     PID

mongos           27017    running    27192

config server    27019    running    29380

shard01
    mongod       27018    running    10192


PS C:\mlaunch\v5.0.3\sharded>

 Then run the tests using:

.\build.ps1 --target=testnet472 // or test 

The tests should be run using the default connection strings built into the test suite. In other words, the `MONGODB_URI` and `MONGODB_URI_WITH_MULTIPLE_MONGOSES` environment variables should not be set.