SERVER-53786 Test WriteConcernErrors are preserved with the mongos implementation of dropDatabases command

1 files changed, 13 insertions, 0 deletions

diff --git a/jstests/sharding/write_concern_basic.js b/jstests/sharding/write_concern_basic.js
index ae27edad6cd..c24f5a51028 100644
--- a/jstests/sharding/write_concern_basic.js
+++ b/jstests/sharding/write_concern_basic.js
@@ -9,11 +9,24 @@ load("jstests/sharding/libs/failpoint_helpers.js");
 
 let st = new ShardingTest({shards: 1, config: 1});
 
+// Test drop collection
 {
     let db = st.s.getDB("test");
+    // _shardsvrDropCollectionParticipant required for PM-1965
     failCommandsWithWriteConcernError(st.rs0, ["drop", "_shardsvrDropCollectionParticipant"]);
     assert.commandWorked(db.collection.insert({"a": 1}));
     assert.commandFailedWithCode(db.runCommand({drop: "collection"}), 12345);
+    turnOffFailCommand(st.rs0);
+}
+
+// Test drop database
+{
+    let db = st.s.getDB("test");
+    // _shardsvrDropDatabaseParticipant required for PM-1965
+    failCommandsWithWriteConcernError(st.rs0, ["dropDatabase", "_shardsvrDropDatabaseParticipant"]);
+    assert.commandWorked(db.collection.insert({"a": 1}));
+    assert.commandFailedWithCode(db.runCommand({"dropDatabase": 1}), 12345);
+    turnOffFailCommand(st.rs0);
 }
 
 st.stop();