Improve encryption / CSFLE code coverage from ~25% to ~80%

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Cannot Reproduce
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: Client Side Encryption
    • 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

      CSFLE modules represent ~2.7% of the total codebase (856 / 32,085 statements) but are sitting at only ~25% coverage — well below the project average of 44%. The async/encryption.py and sync/encryption.py files are the worst at 25%, with encryption_options.py close behind at 26%.

      CSFLE module coverage can be improved by targeting critical code paths:

      • encryption.py (sync + async), encryption_options.py
      • ~70% uncovered; KMS provider paths, key rotation, error handling

      Definition of done

      Improve CSFLE coverage to ~80-100% which will increase total coverage by up to 2%.

      Pitfalls

      Possible practical challenges testing CSFLE code in real world scenarios and/or mocking the results.

            Assignee:
            Unassigned
            Reporter:
            Alex Clark
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: