Prove wait for works using useFakeTimers

[chris110408]

What:

Fixes #631

Why:
Create the unit test to prove the wait for function works using jest.useFakeTimers

How:

Created a unit test use jest.useFakeTimers and jest.advanceTimersByTime()
Checklist:

• Documentation updated
• Tests
• Ready to be merged
  
• Added myself to contributors table
  

[codecov]

Codecov Report

Merging #637 (f9ed124) into main (ee0b83f) will not change coverage.
The diff coverage is n/a.

❗ Current head f9ed124 differs from pull request most recent head 0aaf07a. Consider uploading reports for the commit 0aaf07a to get more accurate results

@@            Coverage Diff            @@
##              main      #637   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           15        15           
  Lines          235       235           
  Branches        33        29    -4     
=========================================
  Hits           235       235           

---

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 ee0b83f...0aaf07a. Read the comment docs.

[mpeyper]

thanks again @chris110408!

I'll wait for a resolution to the conversation in #631 before doing anything with this.

[mpeyper]

This should be in a catch block. If the test fails, we don't want to the fake timers to break other tests in the file.

[chris110408]

Copy that makes sense. I will wrap the jest.useRealTimers() in finally

[mpeyper]

lol, yes, I meant finally, not catch... putting it in catch would not be useful at all 🤦

[mpeyper]

@chris110408 I'm thinking of merging these tests but keeping #631 open until we get some clarification on what the actual issue is there, as I feel these represent valid ways of using fake timers and they will help ensure we don't accidentally break anything for the current functionality.

I know it's annoying (read my thoughts on it here, but would you mind making variations for native and server renderers? It'll mostly be copying the file into their test directory and you may need to add a hydrate call for the server renderer (see other server tests for examples).