Improved mock expectations not satisfied message

[kellpossible]

I get the following panic message when my mock expectation is not met.

thread 'my_test' panicked at 'Verification failed: mock expectations have not been satisfied.

It would be good for the error message to be more explicit with how it has failed to meet this expectation. In my situation showing the expected number of calls, and the actual number of calls.

[LukeMathWalker]

Hey @kellpossible!

This has already been addressed in the master branch by @marcoieni a few weeks ago - see

wiremock-rs/src/verification.rs

Line 16 in 92c7bc9

"{}. Expected range of matching incoming requests: {:?}, actual: {}",

It just needs to be released - there is a breaking change, so I was hoping to bundle together a few more improvements but it'd probably makes sense to just release what we have at the moment.
I'll try to cut a release later today/tomorrow.

[kellpossible]

@LukeMathWalker awesome!