Open shanejansen opened 2 years ago
I believe this is more of a bug than an enhancement: yet another case where 0
times vs. None
times aren't being correctly distinguished, this case in the assertion failure reporting.
It probably happons for more than just the MySQL mock. Could happen for the reporting of 0
times assertions with any mock.
MySql mock method
does_not_exist
has a misleading error message: "was found 1 time(s) but expected any time(s)"