[DRIVERS-604] Re-sync APM tests for removed upsert/multi fields with default values in update commands Created: 05/Feb/19  Updated: 07/Apr/22

Status: Implementing
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Jeremy Mikola Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CXX-1736 Re-sync APM tests for removed upsert/... Backlog
depends on CDRIVER-2965 Re-sync APM tests for removed upsert/... Closed
depends on CSHARP-2517 Re-sync APM tests for removed upsert/... Closed
depends on GODRIVER-827 Re-sync APM tests for removed upsert/... Closed
depends on MOTOR-313 Re-sync APM tests for removed upsert/... Closed
depends on RUBY-1711 Re-sync APM tests for removed upsert/... Closed
depends on PYTHON-1744 Re-sync APM tests for removed upsert/... Closed
depends on NODE-1871 Re-sync APM tests for removed upsert/... Backlog
depends on JAVA-3202 Re-sync APM tests for removed upsert/... Closed
Related
related to DRIVERS-2270 Use $$unsetOrMatches for upsert and m... Implementing
Driver Compliance:
Key Status/Resolution FixVersion
NODE-1871 Backlog
JAVA-3202 Fixed 3.12.0
SCALA-500 Done
PYTHON-1744 Done
CXX-1736 Backlog
MOTOR-313 Won't Fix
CSHARP-2517 Fixed 2.10.0
GODRIVER-827 Done
PERL-1072 Won't Fix
RUBY-1711 Fixed 2.10.0.rc0
CDRIVER-2965 Fixed 1.16.0

 Description   

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. 


Generated at Thu Feb 08 08:21:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.