[SERVER-84316] Query test suite(s) with shared sharding fixture Created: 19/Dec/23 Updated: 26/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qi-testing, quick-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Participants: | |||||||||
| Description |
|
We have many query tests which need to do something special with a ShardingTest - often just sharding a collection and ensuring it's on two different shards or something like that. I think we should invest in a way to have these tests share a single sharded cluster, to dramatically speed up the tests and also de-clutter the logs. Each test could have a unique collection name or db name, similar to jscore. Unlike the sharded jscore passthrough, it would be expected/encouraged for tests to modify the sharding distribution of their datasets. |