We currently don't have a good way of inducing a server error in the Go driver, which makes checking that a change stream doesn't resume on a server error somewhat difficult. One possible solution is to mock test the functionality rather than running it on an actual server. Either way, some time after change streams land, we should decide on a method and use it to implement the test.