-
Type: Task
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Component/s: Unified Test Runner
-
Needed
-
Summary
Drivers should be able to correctly fail or skip a test when an operation within the test is unsupported. We should add a test similar to operation-failure that tests that an unsupported driver operation (like unsupportedOperation) correctly fails.
Motivation
Who is the affected end user?
Driver devs.
How does this affect the end user?
Does not.
How likely is it that this problem or use case will occur?
This issue came up in a recent PR that tests the modifyCollection operation present in only some drivers.
If the problem does occur, what are the consequences and how severe are they?
Drivers may not be able to even sync tests with unsupported operations because they are not able to decode the file.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- split to
-
CDRIVER-4381 Add unified test format valid-fail test for unsupported operation
- Backlog
-
CSHARP-4166 Add unified test format valid-fail test for unsupported operation
- Backlog
-
CXX-2507 Add unified test format valid-fail test for unsupported operation
- Backlog
-
RUST-1312 Add unified test format valid-fail test for unsupported operation
- Backlog
-
NODE-4233 Add unified test format valid-fail test for unsupported operation
- Blocked
-
GODRIVER-2409 Add unified test format valid-fail test for unsupported operation
- Closed
-
MOTOR-958 Add unified test format valid-fail test for unsupported operation
- Closed
-
PHPLIB-865 Add unified test format valid-fail test for unsupported operation
- Closed
-
PYTHON-3255 Add unified test format valid-fail test for unsupported operation
- Closed
-
RUBY-2988 Add unified test format valid-fail test for unsupported operation
- Closed
-
JAVA-4603 Add unified test format valid-fail test for unsupported operation
- Closed