CSHARP-4448: Implement OIDC SASL mechanism

Author: Oleksandr Poliakov

specifications/auth/tests/README.rst

@@ -1,18 +1,26 @@
-==========
+==========
 Auth Tests
 ==========
 
-The YAML and JSON files in this directory tree are platform-independent tests
-that drivers can use to prove their conformance to the Auth Spec at least with
-respect to connection string URI input.
+Introduction
+============
+
+This document describes the format of the driver spec tests included in the
+JSON and YAML files included in the ``legacy`` sub-directory. Tests in the
+``unified`` directory are written using the `Unified Test Format
+<../../unified-test-format/unified-test-format.rst>`_.
+
+The YAML and JSON files in the ``legacy`` directory tree are
+platform-independent tests that drivers can use to prove their conformance to
+the Auth Spec at least with respect to connection string URI input.
 
 Drivers should do additional unit testing if there are alternate ways of
 configuring credentials on a client.
 
 Driver must also conduct the prose tests in the Auth Spec test plan section.
 
 Format
-------
+======
 
 Each YAML file contains an object with a single ``tests`` key. This key is an
 array of test case objects, each of which have the following keys:
@@ -50,4 +58,4 @@ Testing whether a URI is valid or not should simply be a matter of checking
 whether URI parsing (or MongoClient construction) raises an error or exception.
 
 If a credential is configured, its properties must be compared to the
-``credential`` field.
+``credential`` field.