@@ -485,6 +485,8 @@ The structure of this object is as follows:
485
485
- [serverHeartbeatSucceededEvent](#expectedEvent_serverHeartbeatSucceededEvent)
486
486
- [serverHeartbeatFailedEvent](#expectedEvent_serverHeartbeatFailedEvent)
487
487
- [topologyDescriptionChangedEvent](#expectedEvent_topologyDescriptionChangedEvent)
488
+ - [topologyOpeningEvent](#expectedEvent_topologyOpeningEvent)
489
+ - [topologyClosedEvent](#expectedEvent_topologyClosedEvent)
488
490
489
491
<span id="entity_client_ignoreCommandMonitoringEvents"></span>
490
492
@@ -1231,6 +1233,18 @@ The structure of this object is as follows:
1231
1233
Test runners SHOULD ignore any other fields present on the `previousDescription` and `newDescription` fields of the
1232
1234
captured `topologyDescriptionChangedEvent`.
1233
1235
1236
+ <span id="expectedEvent_topologyOpeningEvent"></span>
1237
+
1238
+ - `topologyOpeningEvent` : Optional object. Assertions for one
1239
+ [topologyOpeningEvent](../server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.md#events-api)
1240
+ object.
1241
+
1242
+ <span id="expectedEvent_topologyClosedEvent"></span>
1243
+
1244
+ - `topologyClosedEvent` : Optional object. Assertions for one
1245
+ [topologyClosedEvent](../server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.md#events-api)
1246
+ object.
1247
+
1234
1248
# #### hasServiceId
1235
1249
1236
1250
This field is an optional boolean that specifies whether or not the `serviceId` field of an event is set. If true, test
@@ -3555,6 +3569,9 @@ other specs *and* collating spec changes developed in parallel or during the sam
3555
3569
3556
3570
# # Changelog
3557
3571
3572
+ - 2025-04-07 : Add `topologyOpeningEvent` and `topologyClosedEvent` to the unified test format and schema 1.20+ as they
3573
+ were omitted in error.
3574
+
3558
3575
- 2025-01-21 : **Schema version 1.23.**
3559
3576
3560
3577
Support automatic encryption. Add `autoEncryptOpts` to `client` entity.
0 commit comments