In order to have data not conflict with other tests, tests need to drop all used collections at some point. This drop should happen at the beginning of the test and not the end of the test (unless specifically testing drop) to ensure that we can check the tested data for consistency. SERVER-71139 is an example where the test coverage was largely lost in our passthroughs due to dropping the interesting data after the fact. We should see if we can ensure the preferred pattern is enforced and convert tests that use the wrong pattern as applicable. Alternatively we should explore overrides that automatically ensure the correct pattern.

A counterpoint to investing time here is that our mutational fuzzers over time run all of the jscore commands in different orders and don't drop the data after the fact.