The Ruby driver offers two standalone connection options:

• Direct - topology is forced;
• (none given) - topology is discovered.

The URI in standalone sdam monitoring spec test is interpreted by the Ruby driver as a discoverable topology, which is unlike most (all?) other drivers where it means a forced standalone topology. As a result, Ruby driver behavior is not correct.

This ticket proposes to add both tests and adjust the behavior to be correct for each. The difference is the order in which topology and description change events happen:

• For a forced topology, transitions are: unknown/unknown -> single topology/unknown server -> single topology/standalone server
• For a discovered topology, transitions are: unknown/unknown -> unknown topology/standalone server -> single topology/standalone server