We have a few unit tests that mock a shard response when mongos sends a bulkWrite command. This is to test that mongos, when it receives a stale config error response from the shard, refreshes itself, and additionally, when the number of refresh attempts exceeds kMaxRoundsWithoutProgress, we return a NoProgressMade error. See here for more info.

Note that we already have an integration JS test for stale config errors here, so we don't really need to test that. What we need to test is regarding the number of refreshes.

Original generated JIRA text:
There is a TODO in the codebase referencing a resolved ticket which is assigned to you.

Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/mongodb/mongo/search?q=SERVER-72790&type=Code

The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to represent the work you're actually doing.