-
Type: Task
-
Resolution: Done
-
Priority: Unknown
-
None
-
Component/s: Unified Test Runner
-
Needed
-
Summary
DRIVERS-1653 introduced observeSensitiveCommands to the unified test runner (schema version 1.5); however, it did not include integration tests for the new syntax. The test cases pertaining to sensitive command redaction are not sufficient to verify that drivers have implemented the new syntax completely. This issue will add integration tests to do so.
Motivation
Who is the affected end user?
Drivers.
How does this affect the end user?
Does not affect the end user.
How likely is it that this problem or use case will occur?
It's quite possible that observeSensitiveCommands can be implemented incorrectly if drivers are only using the redaction tests in DRIVERS-1653 to verify their implementations.
If the problem does occur, what are the consequences and how severe are they?
The risk is an incorrect test runner implementation.
Is this issue urgent?
This should be done alongside DRIVERS-1653, but individual drivers can make that call.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Only tests.
- split to
-
CDRIVER-4104 Integration tests for observeSensitiveCommands
- Closed
-
CSHARP-3769 Integration tests for observeSensitiveCommands
- Closed
-
CXX-2325 Integration tests for observeSensitiveCommands
- Closed
-
GODRIVER-2107 Integration tests for observeSensitiveCommands
- Closed
-
MOTOR-797 Integration tests for observeSensitiveCommands
- Closed
-
NODE-3494 Implement support and integrate tests for observeSensitiveCommands
- Closed
-
PHPLIB-703 Integration tests for observeSensitiveCommands
- Closed
-
PYTHON-2842 Integration tests for observeSensitiveCommands
- Closed
-
RUBY-2752 Integration tests for observeSensitiveCommands
- Closed
-
RUST-944 Integration tests for observeSensitiveCommands
- Closed
-
JAVA-4264 Integration tests for observeSensitiveCommands
- Closed