Validate if spy or mock was passed when expected

[atsikov]

What

Add error to toHaveBeenCalledBefore and toHaveBeenCalledAfter matchers in case passed params are not instances of jest.Mock

Why

Jest has similar errors when non spy or mock is passed to toHaveBeenCalled or other mock-related matchers.

• Unit tests
• No additional lint warnings

[codecov-io]

Codecov Report

Merging #203 (4a3aff6) into main (449905f) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #203   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          125       125           
  Lines          774       792   +18     
  Branches       115       124    +9     
=========================================
+ Hits           774       792   +18     

Impacted Files	Coverage Δ
src/matchers/toHaveBeenCalledAfter/index.js	100.00% <100.00%> (ø)
src/matchers/toHaveBeenCalledBefore/index.js	100.00% <100.00%> (ø)
src/utils/index.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 449905f...4a3aff6. Read the comment docs.

[benjaminkay93]

This is a really great PR, and going to be really useful as more mocking matchers are added 🎉.

Ive stuck a comment on one little bit where I couldn't read the logic easily which could lead to it being hard to maintain in the future.

Also just worrying abit about how clear we are being to our users on the error message outputted :)

Hope to hear from you soon about how you feel about these comments 😺

[SimenB]

thanks!