Fix over-strict update assertion and missing initialData in OpenTelemetry spec tests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Observability
    • Hide

      DRIVERS-3597:
      Summary of necessary driver changes

      • Resync the OpenTelemetry spec tests. Both fixes are test-only, so no driver code changes are required.
      • Drop any local patch or skip carried for the over-strict update assertion, and any local cleanup added to make the operation fixtures repeatable within a single process.
      • create_collection gained a second expected span, so a driver that hard-codes span counts for that fixture needs to pick up the new expectation.

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      Context for other referenced/linked tickets
      N/A

      Show
      DRIVERS-3597 : Summary of necessary driver changes Resync the OpenTelemetry spec tests. Both fixes are test-only, so no driver code changes are required. Drop any local patch or skip carried for the over-strict update assertion, and any local cleanup added to make the operation fixtures repeatable within a single process. create_collection gained a second expected span, so a driver that hard-codes span counts for that fixture needs to pick up the new expectation. Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) 0d6fee49 (PR #1971 ) Python POC: https://github.com/mongodb/mongo-python-driver/pull/2964 0529b08a vendors the fixed fixtures and removes both workarounds, taking the otel selection from 178 passed and 5 skipped to 180 passed and 3 skipped. c8ae168a introduced the workarounds, so the two commits bracket the deviation. Context for other referenced/linked tickets N/A
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3597, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: