Summary

What is the problem or use case, what are we trying to achieve?
The SDAM spec says:

"If the driver encounters errors when establishing application connections (this includes the initial handshake and authentication), the driver MUST mark the server Unknown and clear the server's connection pool if the TopologyType is not LoadBalanced."

We have two tests that check for errors encountered during authentication but no tests currently for errors encountered on the hello message.

"reset server and pool after AuthenticationFailure error" and
"Reset server and pool after misc command error" are the two existing tests.

Motivation

We are not testing drivers for full spec compliance, leading to non-deterministic behavior.

Who is the affected end user?

Who are the stakeholders?
Users of the drivers.

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?
Unlikely in practice

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Users could see an increase in error rates if the pool is not cleared when it should.

Is this issue urgent?

Does this ticket have a required timeline? What is it?
No

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?
No

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?
Yes

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?
Implement one or more tests similar to the two existing tests for authentication failures.