-
Type: Improvement
-
Resolution: Fixed
-
Priority: Unknown
-
Component/s: CSOT
-
None
-
Not Needed
-
Summary
Recent discussion and observations have confirmed that only one listCollections operation is required in the context of the client-side encryption test scenario, contrary to the current test definition in timeoutMS.yml. This adjustment is based on the understanding of libmongocrypt's caching behavior, which negates the need for a second listCollections operation. Additionally, the internal MongoClient is not configured with auto encryption, and therefore would not produce the listCollections event.
Motivation
Who is the affected end user?
Engineers who implement and test client-side encryption functionality.
How does this affect the end user?
Improper testing could result in unnoticed bugs.
Is this issue urgent?
No
Is this ticket only for tests?
Yes
Acceptance Criteria
- Update Test Definition: Revise timeoutMS.yml to specify that only one listCollections operation is expected during the test scenario, removing any requirement for a second operation.
- split to
-
CDRIVER-5490 Update test definition in Client-Side encryption tests
- Backlog
-
CSHARP-4983 Update test definition in Client-Side encryption tests
- Backlog
-
CXX-2968 Update test definition in Client-Side encryption tests
- Backlog
-
GODRIVER-3140 Update test definition in Client-Side encryption tests
- In Progress
-
JAVA-5340 Update test definition in Client-Side encryption tests
- Closed
-
MOTOR-1263 Update test definition in Client-Side encryption tests
- Closed
-
NODE-5974 Update test definition in Client-Side encryption tests
- Closed
-
PHPLIB-1401 Update test definition in Client-Side encryption tests
- Closed
-
PYTHON-4240 Update test definition in Client-Side encryption tests
- Closed
-
RUBY-3407 Update test definition in Client-Side encryption tests
- Closed
-
RUST-1862 Update test definition in Client-Side encryption tests
- Closed