RUST-949 Use SDAM monitoring in auth_error test

Author: isabelatkinson

src/sdam/test.rs

@@ -9,6 +9,7 @@ use tokio::sync::RwLockWriteGuard;
 
 use crate::{
     error::ErrorKind,
+    sdam::ServerType,
     test::{
         CmapEvent,
         Event,
@@ -318,6 +319,7 @@ async fn auth_error() {
     options.retry_writes = Some(false);
     options.cmap_event_handler = Some(handler.clone());
     options.command_event_handler = Some(handler.clone());
+    options.sdam_event_handler = Some(handler.clone());
     let client = Client::with_options(options).expect("client creation should succeed");
 
     let coll = client.database("auth_error").collection("auth_error");
@@ -327,18 +329,25 @@ async fn auth_error() {
         .expect_err("insert should fail");
     assert!(matches!(*auth_err.kind, ErrorKind::Authentication { .. }));
 
+    if !setup_client.is_load_balanced() {
+        subscriber
+            .wait_for_event(Duration::from_millis(2000), |event| match event {
+                Event::Sdam(SdamEvent::ServerDescriptionChanged(event)) => {
+                    event.new_description.description.server_type == ServerType::Unknown
+                }
+                _ => false,
+            })
+            .await
+            .expect("should see server marked unknown");
+    }
+
     subscriber
         .wait_for_event(Duration::from_millis(2000), |event| {
             matches!(event, Event::Cmap(CmapEvent::PoolCleared(_)))
         })
         .await
         .expect("should see pool cleared event");
 
-    // Wait a little while for the server to be marked as Unknown.
-    // Once we have SDAM monitoring, this wait can be removed and be replaced
-    // with another event waiting.
-    RUNTIME.delay_for(Duration::from_millis(750)).await;
-
     coll.insert_many(vec![doc! { "_id": 5 }, doc! { "_id": 6 }], None)
         .await
         .expect("insert should succeed");