Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Unknown
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Binding Changes:
Not Needed
Confidence Status:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Link:
None
Goal Name(s):
None

Scope

Investigate solutions and consider adding driver integration tests in libmongocrypt to catch regressions on master.

Background & Motivation

Some libmongocrypt changes inadvertently break driver tests, and are only caught by drivers that test with the master branch. This causes churn on those changes.

Examples:

~~MONGOCRYPT-306~~ changed an error message. This failed driver tests and required a follow-up change https://github.com/mongodb/libmongocrypt/pull/437
~~MONGOCRYPT-457~~ exposed a bug in drivers-evergreen-tools scripts. This failed driver tests and required a follow-up change: https://github.com/mongodb-labs/drivers-evergreen-tools/pull/220

is related to

MONGOCRYPT-350 Add integration tests with CSFLE CLI to Evergreen

Backlog

Assignee:: Unassigned
Reporter:: Kevin Albertson
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Aug 03 2022 05:20:28 PM UTC
Updated:: Aug 08 2022 07:19:07 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates