[SERVER-45052] Separate out RWCDefault jstests into appropriate suites Created: 11/Dec/19  Updated: 05/Dec/22  Resolved: 14/Nov/22

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

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: sharding-common-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-43125 Write RWCDefaults propagation tests Closed
related to SERVER-43720 mongos and configsvr get/setDefaultRW... Closed
related to SERVER-71342 Complete TODO listed in SERVER-45052 Closed
Assigned Teams:
Replication
Participants:

 Description   

This relates to

  • jstests/sharding/read_write_concern_defaults_commands_api.js
  • jstests/sharding/read_write_concern_defaults_application.js
  • jstests/noPassthrough/read_write_concern_defaults_metrics.js

Currently these run standalone and/or replset tests from inside the sharding suite. These other environments should run the tests from within the more appropriate suites. Consider a framework like on SERVER-43125.


Generated at Thu Feb 08 05:07:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.