Add unified spec tests for commitTransaction and abortTransaction command logging

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Component/s: Logging
    • None
    • Needed - No Spec Changes
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-6200 Blocked
      CXX-3401 Blocked
      CSHARP-5837 Blocked
      GODRIVER-3760 Blocked
      JAVA-6061 Blocked
      NODE-7393 Blocked
      PYTHON-5698 Blocked
      PHPLIB-1769 Blocked
      RUBY-3758 Blocked
      RUST-2339 Blocked
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } #scriptField td.willNotDo { background-color: #FF0000; /* Red color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-6200 Blocked CXX-3401 Blocked CSHARP-5837 Blocked GODRIVER-3760 Blocked JAVA-6061 Blocked NODE-7393 Blocked PYTHON-5698 Blocked PHPLIB-1769 Blocked RUBY-3758 Blocked RUST-2339 Blocked

      Summary

      Add unified spec tests to verify that commitTransaction and abortTransaction commands are logged when command logging is enabled at the debug level.

      Motivation

      When command logging is enabled at the debug level, all commands sent to the server should generate "Command started" and "Command succeeded" (or "Command failed") log messages. Currently, the command-logging-and-monitoring spec tests do not include coverage for transaction commands (commitTransaction and abortTransaction), which may allow driver implementations to inadvertently omit logging for these commands.

      Is this ticket only for tests?

      Yes

      Acceptance Criteria

      Add the following test cases to command-logging-and-monitoring/tests/logging/command.yml (or equivalent):

      • "A successful commitTransaction command"
      • "A successful abortTransaction command"

            Assignee:
            Preston Vasquez
            Reporter:
            Preston Vasquez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: