Skip CSOT unified tests when running with coverage

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Python Drivers
    • 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

      Context

      Describe the background behind the problem.
      Coverage-enabled test suite runs are significantly slower due to the additional overhead in both total runtime and in inter-test timings. This causes frequent failures for timing-sensitive tests such as CSOT.

      Definition of done

      What must be done to consider the task complete?
      Skip CSOT tests when coverage is enabled.

      Pitfalls

      What should the implementer watch out for? What are the risks?

            Assignee:
            Noah Stapp
            Reporter:
            Noah Stapp
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: