Uploaded image for project: 'Motor'
  1. Motor
  2. MOTOR-797

Integration tests for observeSensitiveCommands

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Hide

      DRIVERS-1868:
      Sync valid-pass tests for the unified test format to mongodb/specifications@6847048. Also note that some additional clarifications were added to the spec itself concerning implementation of observeSensitiveEvents (originally introduced in DRIVERS-1653); however, the behavior of the syntax has not been changed.

      Show
      DRIVERS-1868 : Sync valid-pass tests for the unified test format to mongodb/specifications@6847048 . Also note that some additional clarifications were added to the spec itself concerning implementation of observeSensitiveEvents (originally introduced in DRIVERS-1653); however, the behavior of the syntax has not been changed.

      Driver Changes: Sync valid-pass tests for the unified test format to mongodb/specifications@6847048. Also note that some additional clarifications were added to the spec itself concerning implementation of observeSensitiveEvents (originally introduced in DRIVERS-1653); however, the behavior of the syntax has not been changed.

      Summary

      DRIVERS-1653 introduced observeSensitiveCommands to the unified test runner (schema version 1.5); however, it did not include integration tests for the new syntax. The test cases pertaining to sensitive command redaction are not sufficient to verify that drivers have implemented the new syntax completely. This issue will add integration tests to do so.

      Motivation

      Who is the affected end user?

      Drivers.

      How does this affect the end user?

      Does not affect the end user.

      How likely is it that this problem or use case will occur?

      It's quite possible that observeSensitiveCommands can be implemented incorrectly if drivers are only using the redaction tests in DRIVERS-1653 to verify their implementations.

      If the problem does occur, what are the consequences and how severe are they?

      The risk is an incorrect test runner implementation.

      Is this issue urgent?

      This should be done alongside DRIVERS-1653, but individual drivers can make that call.

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      Only tests.

            Assignee:
            Unassigned Unassigned
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: