[MONGOCRYPT-465] Investigate running driver integration tests with libmongocrypt changes Created: 03/Aug/22 Updated: 08/Aug/22 |
|
| Status: | Backlog |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Unknown |
| Reporter: | Kevin Albertson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Binding Changes: | Not Needed | ||||||||
| Description |
|
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:
|