[DRIVERS-668] Use $project to ensure only relevant fields in Database-level aggregation spec tests Created: 10/Jun/19  Updated: 22/Feb/23  Resolved: 22/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-3186 Use $project to ensure only relevant ... Closed
depends on CSHARP-2633 Use $project to ensure only relevant ... Closed
depends on CXX-1784 Use $project to ensure only relevant ... Closed
depends on GODRIVER-1125 Use $project to ensure only relevant ... Closed
depends on JAVA-3318 Use $project to ensure only relevant ... Closed
depends on MOTOR-349 Use $project to ensure only relevant ... Closed
depends on NODE-2002 Use $project to ensure only relevant ... Closed
depends on PHPLIB-437 Use $project to ensure only relevant ... Closed
depends on PYTHON-1865 Use $project to ensure only relevant ... Closed
depends on RUBY-1835 Use $project to ensure only relevant ... Closed
Driver Compliance:
Key Status/Resolution FixVersion
SCALA-534 Done
MOTOR-349 Won't Fix
NODE-2002 Done
CDRIVER-3186 Fixed 1.15.0
PYTHON-1865 Duplicate
CSHARP-2633 Won't Do
GODRIVER-1125 Done
PHPLIB-437 Done
PERL-1104 Won't Fix
CXX-1784 Fixed 3.5.0
JAVA-3318 Done
RUBY-1835 Fixed 2.11.0.rc0

 Description   

The existing database-level aggregation spec tests are written such that the command response from the server includes fields that are not included in results such as $readPreference and $clusterTime. Consequently, test-runners in drivers must do extra work to ensure the spec tests don't fail by comparing only those fields that are included in results.command. This can increase the complexity of the test runners significantly. This can be avoided by tweaking the tests to project out only those fields that we are interested in comparing.


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