This SDAM prose test implies the following order of events:

1. step 2: ServerHeartbeatSucceededEvent happens before ConnectionPoolReadyEvent caused by it
2. steps 4 and 5: ServerHeartbeatFailedEvent happens before ConnectionPoolReadyEvent caused by a successful check that happened after the check that caused ServerHeartbeatFailedEvent.

However, neither SDAM more CMAP specs require any such ordering. Java driver recently recently started delivering server monitor events asynchronously (in a dedicated thread, together with server and cluster events). This change affected the aforementioned SDAM prose test: it started failing sporadically, and we disabled it. If the order implied by the test is indeed what the specifications require, the order should be explicitly and unambiguously specified either by SDAM or by CMAP specs.