Mock timestamp

[mattphillips]

Summary

This PR adds the internal behaviour to the mock state to record a timestamp on every invocation to allow community matchers to solve #4402.

I'm happy to add the matcher wanted in #4402 to jest-extended

Test plan

• Unit tests for new timestamp

[codecov-io]

Codecov Report

Merging #4866 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4866      +/-   ##
==========================================
+ Coverage   59.24%   59.25%   +<.01%     
==========================================
  Files         200      200              
  Lines        6647     6648       +1     
  Branches        3        4       +1     
==========================================
+ Hits         3938     3939       +1     
  Misses       2709     2709

Impacted Files	Coverage Δ
packages/jest-mock/src/index.js	84.47% <100%> (+0.05%)	⬆️

---

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 2a2429e...53b25f1. Read the comment docs.

[SimenB]

Date.now()

[SimenB]

Thanks for tackling this!

[mattphillips]

@SimenB I've updated this to use Date.now() good suggestion 😄

[ChrisCinelli]

Unfortunately this will not solve #4402 if the calls happen at the same time (see jest-community/jest-extended#98 (comment)).
For this use case, in order to implement .toHaveBeenCalledBefore, we need a global counter incremented at every call. The current value can be saved in .mock.invocationOrder (this is what jasmine uses).
Pretty simple implementation but it will require a new PR.

[AlanFoster]

@ChrisCinelli Confirming that I've run into the same problem too -

  Expected first mock to have been called before, timestamps:
    [1517598132978]
  Received second mock with timestamps:
    [1517598132978]

Is this a PR you're currently working on? :]

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.