There are a number of suites with a background hook that performs moveCollection operations, namely the config_transition* and add_remove_shard* suites. However, those suites are not able to catch the liveness issue like in SERVER-109322 because:

• The hook moves collections at random so the collection being moved is usually not the collection the test is writing to.
• Even when a write gets blocked as described above, it would get unblocked when the moveCollection completes. This would not cause a test to fail.

We should add liveness testing for CRUD operations in resharding in general to avoid missing this kind of issues in the future.