Summary
The unified spec test "upload when contentType is provided" tests a field that is deprecated and that need to be removed (see DRIVERS-2656). This test need to be removed or replaced by a test adding the content type as a "metadata".
Additionally, all the fixtures data contain the fields "md5", "contentType" and "aliases". This fields are removed from the implementation, they need to be removed from the data.
Motivation
Who is the affected end user?
Developers of GridFS implementations
How does this affect the end user?
We don't test the download and delete features on files identical to those we create.
How likely is it that this problem or use case will occur?
Blocking DRIVERS-2656, unless the test is skipped.
If the problem does occur, what are the consequences and how severe are they?
-
Is this issue urgent?
no
Is this ticket required by a downstream team?
Yes
Is this ticket only for tests?
Unified tests only
Acceptance Criteria
The unified tests must be compatible with a GridFS implementation without the fields md5, contentType and aliases.
- related to
-
DRIVERS-2656 Remove Deprecated GridFS Fields
- Implementing
- split to
-
CDRIVER-5818 Remove deprecated field from GridFS unified tests
- Backlog
-
CXX-3191 Remove deprecated field from GridFS unified tests
- Backlog
-
GODRIVER-3441 Remove deprecated field from GridFS unified tests
- Backlog
-
NODE-6581 Remove deprecated field from GridFS unified tests
- Backlog
-
PYTHON-4990 Remove deprecated field from GridFS unified tests
- Backlog
-
RUBY-3597 Remove deprecated field from GridFS unified tests
- Backlog
-
RUST-2107 Remove deprecated field from GridFS unified tests
- Backlog
-
CSHARP-5423 Remove deprecated field from GridFS unified tests
- In Code Review
-
JAVA-5709 Remove deprecated field from GridFS unified tests
- Closed
-
MOTOR-1416 Remove deprecated field from GridFS unified tests
- Closed
-
PHPLIB-1595 Remove deprecated field from GridFS unified tests
- Closed
-
PHPLIB-1218 Remove Deprecated GridFS Fields
- Closed