DRIVERS-2619 Remove null values from command_started_event in fle2v2-CreateCollection.yml (#1429)

* remove null values from `command_started_event`

* link to legacy command monitoring spec tests runner

* note `null` is only expected in top level fields of command

Author: kevinAlbs

source/client-side-encryption/tests/legacy/fle2v2-CreateCollection.json

@@ -158,9 +158,6 @@
             "command": {
               "create": "encryptedCollection",
               "encryptedFields": {
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                   {
                     "path": "firstName",
@@ -343,9 +340,6 @@
             "command": {
               "create": "encryptedCollection",
               "encryptedFields": {
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                   {
                     "path": "firstName",
@@ -851,9 +845,6 @@
             "command": {
               "create": "encryptedCollection",
               "encryptedFields": {
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                   {
                     "path": "firstName",
@@ -1048,9 +1039,6 @@
             "command": {
               "create": "encryptedCollection",
               "encryptedFields": {
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                   {
                     "path": "firstName",
@@ -1367,9 +1355,6 @@
             "command": {
               "create": "encryptedCollection",
               "encryptedFields": {
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                   {
                     "path": "firstName",
@@ -1635,9 +1620,6 @@
             "command": {
               "create": "encryptedCollection",
               "encryptedFields": {
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                   {
                     "path": "firstName",

source/client-side-encryption/tests/legacy/fle2v2-CreateCollection.yml

@@ -101,10 +101,6 @@ tests:
             command:
               create: *encrypted_collection_name
               encryptedFields: &encrypted_fields_expectation {
-                # Expect state collections are not included in the encryptedFields sent to the server.
-                "escCollection": null,
-                "ecocCollection": null,
-                "eccCollection": null,
                 "fields": [
                     {
                         "path": "firstName",
@@ -939,4 +935,4 @@ tests:
           collection: *encrypted_collection_name
         result:
           # Expect error due to server constraints added in SERVER-74069
-          errorContains: "Encrypted State Collection name should follow"
+          errorContains: "Encrypted State Collection name should follow"

source/transactions/tests/README.rst

@@ -322,7 +322,7 @@ Then for each element in ``tests``:
 #. Call ``session0.endSession()`` and ``session1.endSession``.
 #. If the test includes a list of command-started events in ``expectations``,
    compare them to the actual command-started events using the
-   same logic as the Command Monitoring Spec Tests runner, plus the rules in
+   same logic as the `legacy Command Monitoring Spec Tests runner <https://github.com/mongodb/specifications/blob/09ee1ebc481f1502e3246971a9419e484d736207/source/command-monitoring/tests/README.rst#expectations>`_, plus the rules in
    the Command-Started Events instructions below.
 #. If ``failPoint`` is specified, disable the fail point to avoid spurious
    failures in subsequent tests. The fail point may be disabled like so::
@@ -507,10 +507,10 @@ value "session0" or "session1". Tests MUST assert that the command's actual
 Null Values
 ~~~~~~~~~~~
 
-Some command-started events in ``expectations`` include ``null`` values for
-fields such as ``txnNumber``, ``autocommit``, and ``writeConcern``.
-Tests MUST assert that the actual command **omits** any field that has a
-``null`` value in the expected command.
+Some command-started events in ``expectations`` include ``null`` values for top
+level ```command``` fields such as ``txnNumber``, ``autocommit``, and
+``writeConcern``. Tests MUST assert that the actual command **omits** any field
+that has a ``null`` value in the expected command.
 
 Cursor Id
 ~~~~~~~~~