Update OpenTelemetry tests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Component/s: New Spec
    • None

      Summary

      Some OpenTelemetry tests do not conform to the Spec, some require specific run requirements:

       

      • https://github.com/mongodb/specifications/blame/master/source/open-telemetry/tests/operation/aggregate.yml#L46 asserts that db.mongodb.cursor_id is unpopulated, but some drivers fill it in because aggregate returns a cursor (it should have been left out anyway since that’s not the focus of this test)
      • txNumber is not reported when running against standalone, so it has to be behind txnNumber: { $$unsetOrMatches: 1 }) or the test requirement should be replicaSet/sharded
      • The list_collections test expects an empty cursor document, which some drivers don’t populate
      • server.type is not part of the spec, but present in some tests
      • the usage of comment requires a minServerVersion (same for dropCollection )

       __ 

      Motivation

      Who is the affected end user?

      N/A, spec implementation in progress.

      How does this affect the end user?

      N/A

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

      N/A

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

      N/A

      Is this issue urgent?

      N/A

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      Only for tests updates

      Acceptance Criteria

      What specific requirements must be met to consider the design phase complete?

            Assignee:
            Unassigned
            Reporter:
            Nabil Hachicha
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: