[SERVER-71166] Ensure we don't drop interesting data at the end of tests Created: 08/Nov/22  Updated: 30/Aug/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-71139 Ensure indexes with simple collation ... Closed
Assigned Teams:
Replication
Participants:

 Description   

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.


Generated at Thu Feb 08 06:18:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.