Summary

Currently, the initial DNS seedlist discovery spec test runner description requires creating a MongoClient initialized with the URI specified in the test and asserting that either the host lists match the expected values or that an error was thrown/returned. However, it does not specify to run an operation or create a connection, which can lead to incorrectly configured tests passing. Some drivers (e.g. the Go driver) do create connections, which exposes test misconfigurations.

Update the initial DNS seedlist discovery spec test runner description to require running a Ping operation with the created MongoClient in the no-error test cases.

Motivation

Who is the affected end user?

Driver devs.

How does this affect the end user?

Driver devs can be blocked and/or confused about the test failures.

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

The problem typically only occurs when the spec test or test environment changes.

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

Some drivers initial DNS seedlist discovery spec tests may pass while others fail using the same spec tests and configuration. Updates that introduce inconsistencies in the initial DNS seedlist discovery spec tests may go unrecognized in some drivers projects, but may impact . The result is that some drivers teams

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.