@@ -485,6 +485,8 @@ The structure of this object is as follows:
485485 - [serverHeartbeatSucceededEvent](#expectedEvent_serverHeartbeatSucceededEvent)
486486 - [serverHeartbeatFailedEvent](#expectedEvent_serverHeartbeatFailedEvent)
487487 - [topologyDescriptionChangedEvent](#expectedEvent_topologyDescriptionChangedEvent)
488+ - [topologyOpeningEvent](#expectedEvent_topologyOpeningEvent)
489+ - [topologyClosedEvent](#expectedEvent_topologyClosedEvent)
488490
489491 <span id="entity_client_ignoreCommandMonitoringEvents"></span>
490492
@@ -1231,6 +1233,18 @@ The structure of this object is as follows:
12311233 Test runners SHOULD ignore any other fields present on the `previousDescription` and `newDescription` fields of the
12321234 captured `topologyDescriptionChangedEvent`.
12331235
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+
12341248# #### hasServiceId
12351249
12361250This 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
35553569
35563570# # Changelog
35573571
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+
35583575- 2025-01-21 : **Schema version 1.23.**
35593576
35603577 Support automatic encryption. Add `autoEncryptOpts` to `client` entity.
0 commit comments