-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: CRUD
-
None
-
Needed - No Spec Changes
-
Summary
The updateWithPipelines.yml test file includes a mix of operations, which is inconsistent with the naming convention of other CRUD spec tests. This dates back to SPEC-1267 and was not addressed when the v2 specs were ported to the unified format in DRIVERS-1130.
I previously split this test file up when starting DRIVERS-2638, but decided not to move forward with the main change in that ticket; however, the split tests seem worth preserving for consistency.
Motivation
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- is related to
-
DRIVERS-2638 Add spec tests for passing empty pipeline arrays to update and findAndModify operations
- Closed
- split to
-
RUBY-3593 Split updateWithPipelines.yml by operation
- Backlog
-
CDRIVER-5806 Split updateWithPipelines.yml by operation
- Backlog
-
CSHARP-5408 Split updateWithPipelines.yml by operation
- Backlog
-
CXX-3178 Split updateWithPipelines.yml by operation
- Backlog
-
GODRIVER-3424 Split updateWithPipelines.yml by operation
- Backlog
-
JAVA-5698 Split updateWithPipelines.yml by operation
- Backlog
-
NODE-6530 Split updateWithPipelines.yml by operation
- Backlog
-
PYTHON-4961 Split updateWithPipelines.yml by operation
- Backlog
-
RUST-2096 Split updateWithPipelines.yml by operation
- Backlog
-
MOTOR-1412 Split updateWithPipelines.yml by operation
- Closed
-
PHPLIB-1591 Split updateWithPipelines.yml by operation
- Closed