RUST-1879 Convert read/write concern operation tests to unified test format (#1168)

Author: isabelatkinson

src/test/spec.rs

@@ -24,7 +24,7 @@ mod sessions;
 #[cfg(feature = "tracing-unstable")]
 mod trace;
 mod transactions;
-pub mod unified_runner;
+pub(crate) mod unified_runner;
 mod v2_runner;
 mod versioned_api;
 mod write_error;

src/test/spec/json/read-write-concern/README.rst

@@ -1,6 +1,6 @@
-=======================
-Connection String Tests
-=======================
+============================
+Read and Write Concern Tests
+============================
 
 The YAML and JSON files in this directory tree are platform-independent tests
 that drivers can use to prove their conformance to the Read and Write Concern 
@@ -57,19 +57,7 @@ Operation
 
 These tests check that the default write concern is omitted in operations.
 
-The spec test format is an extension of `transactions spec tests <https://github.com/mongodb/specifications/blob/master/source/transactions/tests/README.rst>`_ with the following additions:
-
-- ``writeConcern`` in the ``databaseOptions`` or ``collectionOptions`` may be an empty document to indicate a `server default write concern <https://github.com/mongodb/specifications/blob/master/source/read-write-concern/read-write-concern.rst#servers-default-writeconcern>`_. For example, in libmongoc:
-
-    .. code:: c
-
-       /* Create a default write concern, and set on a collection object. */
-       mongoc_write_concern_t *wc = mongoc_write_concern_new ();
-       mongoc_collection_set_write_concern (collection, wc);
-
-    If the driver has no way to explicitly set a default write concern on a database or collection, ignore the empty ``writeConcern`` document and continue with the test.
-- The operations ``createIndex``, ``dropIndex`` are introduced.
-
+The tests utilize the `Unified Test Format <../../unified-test-format/unified-test-format.md>`__.
 
 Use as unit tests
 =================