DRIVERS-2951 Test serverMonitoringMode=poll waits after a successful …

…heartbeat (#1626)
mongodb · Aug 5, 2024 · 121be10 · 121be10
1 parent 34b9d46
commit 121be10
Show file tree

Hide file tree

Showing 2 changed files with 103 additions and 0 deletions.
diff --git a/source/server-discovery-and-monitoring/tests/unified/serverMonitoringMode.json b/source/server-discovery-and-monitoring/tests/unified/serverMonitoringMode.json
diff --git a/source/server-discovery-and-monitoring/tests/unified/serverMonitoringMode.yml b/source/server-discovery-and-monitoring/tests/unified/serverMonitoringMode.yml
@@ -171,3 +171,43 @@ tests:
  # Wait for the second serverHeartbeatStartedEvent to ensure we do not stream.
  - *waitForSecondHeartbeatStarted
  expectEvents: *pollingStartedEvents
+
+ - description: "poll waits after successful heartbeat"
+ operations:
+ - name: createEntities
+ object: testRunner
+ arguments:
+ entities:
+ - client:
+ id: client
+ uriOptions:
+ serverMonitoringMode: "poll"
+ heartbeatFrequencyMS: 1000000
+ useMultipleMongoses: false
+ observeEvents:
+ - serverHeartbeatStartedEvent
+ - serverHeartbeatSucceededEvent
+ - database:
+ id: db
+ client: client
+ databaseName: sdam-tests
+ # Wait for the first serverHeartbeatSucceededEvent to ensure we start polling.
+ - name: waitForEvent
+ object: testRunner
+ arguments:
+ client: client
+ event:
+ serverHeartbeatSucceededEvent: {}
+ count: 1
+ # Wait for a bit longer to ensure we wait heartbeatFrequencyMS before starting the next check.
+ - name: wait
+ object: testRunner
+ arguments:
+ ms: 500
+ - name: assertEventCount
+ object: testRunner
+ arguments:
+ client: client
+ event:
+ serverHeartbeatStartedEvent: {}
+ count: 1