Audit usages of generate_test_classes in the async test suites

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: greenerbuild, Tests
    • None
    • None
    • Python Drivers
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      I noticed that in test_change_stream we are not using {_IS_SYNC} to choose the correct path, meaning that that unified tests are not being run for change streams.

      Definition of done

      Audit the other async test files and fix all usages of generate_test_classes that do not point to the right folder.

      Pitfalls

      None

            Assignee:
            Steve Silvester
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: