-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
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.
- depends on
-
CDRIVER-3186 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
CSHARP-2633 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
CXX-1784 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
GODRIVER-1125 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
JAVA-3318 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
MOTOR-349 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
NODE-2002 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
PHPLIB-437 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
PYTHON-1865 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed
-
RUBY-1835 Use $project to ensure only relevant fields in Database-level aggregation spec tests
- Closed