De-flake Tests

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: Tests
    • De-flake tests
    • Python Drivers
    • 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?
    • Done
    • 0
    • 0
    • 0
    • 100
    • None
    • None
    • Hide

      Engineer(s): Steven Silvester

      2025-07-10:

      •    All previously identified flaky tests have been addressed, and we now have a process to handle flaky tests, documented in our contributing guide.

       

      2025-07-03:

      • What was accomplished since the last update?
        •  Created a flaky decorator and flaky test process. Substantially improved the waterfall.
      • What's the focus over the next two weeks?
        •  Identify remaining flaky tests and open tickets / add flaky decorator as appropriate
      Show
      Engineer(s): Steven Silvester 2025-07-10:    All previously identified flaky tests have been addressed, and we now have a process to handle flaky tests, documented in our contributing guide.   2025-07-03: What was accomplished since the last update?  Created a flaky decorator and flaky test process. Substantially improved the waterfall. What's the focus over the next two weeks?  Identify remaining flaky tests and open tickets / add flaky decorator as appropriate
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      We have recurring flaky tests, both sync and async, that pop up just often enough to annoy but not enough to consistently get flagged. Going through and fixing or removing these tests would make it significantly easier to isolate future code changes when builds fail.

      Definition of done

      Skipping or fixing each test until there are no more flaky tests running in our CI.

      Pitfalls

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

              Assignee:
              Steve Silvester
              Reporter:
              Jib Adegunloye
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:
                None
                None
                None
                None