Open zvolin opened 4 months ago
Wanted to work on this issue and it turned out that this bug is actually an undocumented feature. I found this comment too
/// `wiremock`'s pooling is designed to be an invisible optimisation: users of the crate, if
/// we are successful, should never have to reason about it.
Would you consider a PR which mentions about the difference in behavior on MockServer::start
and MockServer::builder
? Builder avoids pooling and was what I was actually looking for in this particular test, but I had to find it out by reading code
Hey, as in issue title. I wanted to test that a service gracefully handles networking issues like server being temporarily unreachable and wanted to do that by dropping the
MockServer
, however this loop actually never finishes: