-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2024-12-23, CAR Team 2025-01-06, CAR Team 2025-01-20
As we aim to progressively transition towards the core testing infrastructure to qualify the behavior of sharded clusters, we should stop creating new test files within jstests/sharding. The objective of this ticket is to create a new task that rejects the submission of an evergreen patch if it includes file creations under such a path.
- depends on
-
SERVER-97544 The coverage guaranteed by JS core test suites is not on par with ShardingTest-based ones
-
- Closed
-
-
SERVER-98315 Ensure that relevant noPassthrough test cases are executed against multiple Sharded Cluster Topologies
-
- Backlog
-
-
SERVER-99356 Improve the coverage and isolation of JS Core test cases for add/removeShard
-
- Backlog
-
- is related to
-
SERVER-98670 Clean up single-variant evergreen task apperaing in multiple variant definitions
-
- Needs Scheduling
-
- related to
-
SERVER-100776 Ensure code coverage for mongod nodes with maxed mirrored read settings within the JS core framework
-
- Backlog
-
-
SERVER-100775 Ensure code coverage for un/sharded, non-timeseries clustered collections within the JS core framework
-
- Needs Scheduling
-