-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Client Side Encryption
-
None
-
Needed
-
Summary
The current tests users expectResult: null however, it should use {"$$unsetOrMatches": null}.
This operator can be used anywhere a matched value is expected (including expectResult), excluding an array element because Arrays Must Contain the Same Number of Elements. The test runner MUST assert that the actual value either does not exist or matches the expected value. Matching the expected value MUST use the standard rules in Evaluating Matches, which means that it may contain special operators.
This is because its testing the absence of a result and comparing against a Bson Null.
Motivation
Keeps the test runner to spec.
Is this ticket only for tests?
Yes
- is duplicated by
-
DRIVERS-2383 Update CSE unified tests expectResult: null
- Closed
- split to
-
PHPLIB-907 Update CSE unified tests expectResult: null
- Closed
-
CXX-2541 Update CSE unified tests expectResult: null
- Backlog
-
CDRIVER-4423 Update CSE unified tests expectResult: null
- Closed
-
CSHARP-4243 Update CSE unified tests expectResult: null
- Closed
-
GODRIVER-2485 Update CSE unified tests expectResult: null
- Closed
-
JAVA-4670 Update CSE unified tests expectResult: null
- Closed
-
MOTOR-990 Update CSE unified tests expectResult: null
- Closed
-
NODE-4390 Update CSE unified tests expectResult: null
- Closed
-
PYTHON-3344 Update CSE unified tests expectResult: null
- Closed
-
RUBY-3045 Update CSE unified tests expectResult: null
- Closed
-
RUST-1397 Update CSE unified tests expectResult: null
- Closed