[DRIVERS-2414] CSFLE spec tests should not specify options under an "opts" operation argument Created: 15/Aug/22 Updated: 18/Aug/22 Resolved: 18/Aug/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Client Side Encryption |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Unknown |
| Reporter: | Jeremy Mikola | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
SummaryQuoting Expressing Required and Optional Parameters in the unified test format spec:
The CSFLE spec tests do not follow this. For example, createDataKey.yml includes an opts key within the operation's arguments object. This was likely an oversight in MotivationIs this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Kevin Albertson [ 18/Aug/22 ] |
|
Good point. I missed that during review too. Closing as "Won't Fix" since it does not interfere with driver testing, and would require some effort to update the tests and test runners. |
| Comment by Jeremy Mikola [ 15/Aug/22 ] |
|
Feel free to resolve/close if there is no intention to address this, but I felt compelled to point it out when I encountered this. It was definitely missed during the original review for |