- 
    Type:Improvement 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: None
- 
    Component/s: Internal Code, Testing Infrastructure
- 
    None
- 
        Fully Compatible
- 
        Query 2018-08-13
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Tests which forget to schedule responses to remote commands triggered by the test can be hard to diagnose. For example, setting up the in-memory state representing a sharded collection requires mocking several responses to finds on the config servers. If you forget to schedule a response to one of them, it's hard to tell why the test is hung.