Expose setSystemTime from lolex

[emilgoldsmith]

What would you like?

I would like to be able to do:

cy.clock().then(clock => clock.setSystemTime(12345));

Why is this needed?

I am testing a timer, and I realized that when I wanted to test it also displays hours correctly, I did cy.tick(46060*1000) and Cypress froze because it was running thousands of setInterval callbacks in a row. setSystemTime allows me to skip forward in time, and I can still use tick for small increment testing.

I'm happy to do the implementing

[emilgoldsmith]

P.S: I have a working test right now as I just used the workaround of installing the underlying package myself and manually faking timers, and then using setSystemTime, but would of course be neat to not have to do that

[emilgoldsmith]

Hi @jennifer-shehane so I see it was tagged as a proposal, thank you for that! I was just wondering what this means logistically. Is it welcome for me to contribute this change or does it need to go through some kind of discussion first?

[jennifer-shehane]

@emilgoldsmith I think this would be an accepted change. There seems to be a use case for it. Maybe @chrisbreiding has some thoughts.

[chrisbreiding]

That sounds good to me 👍

[emilgoldsmith]

Great :), I’ll try to set aside time for it one weekend then, but anyone else following is definitely welcome to do it too :)

[cypress-bot]

The code for this is done in cypress-io/cypress#23329, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 10.7.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v10.7.0, please open a new issue.