-
Type: Task
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Component/s: None
-
None
Command Monitoring (APM) spec tests should be synced with 8d1187b.
This is not urgent, as we've only removed upsert and multi from update command expectations where the fields were false (default value, which the CRUD spec does not require sending). I don't believe any drivers will need to change their test runner, unless they were explicitly ignoring these fields and want to remove existing work-around code (as Swift was doing).
There is a previous spec test change ticket DRIVERS-480 that should be considered as part of implementation of this ticket.
- depends on
-
CXX-1736 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Backlog
-
CDRIVER-2965 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
CSHARP-2517 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
GODRIVER-827 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
MOTOR-313 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
RUBY-1711 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
PYTHON-1744 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
JAVA-3202 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
-
NODE-1871 Re-sync APM tests for removed upsert/multi fields with default values in update commands
- Closed
- is related to
-
PYTHON-4608 Don't send upsert/multi unless user sets it explicitly
- Backlog
- related to
-
DRIVERS-2270 Use $$unsetOrMatches for upsert and multi in update command expectations
- Implementing