Summary

Quoting this comment from DRIVERS-1711:

Note: the retryable reads tests make use of command monitoring to ensure operations correctly fail and succeed upon retry. This adds some extra resilience to catch the case in which a test runner does not properly set a fail point and therefore doesn't trigger the retry logic prior to an operation succeeding. We should consider adding command monitoring to the retryable writes tests when converting them to the unified format to gain this additional layer of testing.

Adding command monitoring assertions was out of scope for porting the legacy retryable writes spec tests to the unified format (DRIVERS-1711); however, it can be considered as a future improvement.

What is the problem or use case, what are we trying to achieve?

Motivation

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.