Cannot override cy.clock a second time

[Lehren]

Current behavior

If I mock the current date with cy.clock(), and then I call it again later in my test, the current date will not be changed and new invocations of new Date() will return my old mocked date.

Additionally, the second cy.clock call is not even shown in the log

Desired behavior

Something like this should work:

cy.clock(Date.UTC(2021, 2, 31);
cy.visit(....);
....

cy.clock(Date.UTC(2021, 4, 20);
cy.reload();
...

Test code to reproduce

https://github.com/Lehren/cypress-test-tiny

Cypress Version

13.15.0

Node version

v16.20.2

Operating System

macOS 14.3.1

Debug Logs

No response

Other

Cypress test:

Cypress testlog :
Note, no second clock call

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[Lehren]

Still happens on 13.15.0

[cjonesuk]

I've just encountered the same issue. A workaround i found is when changing the clock a second time, call restore first then either use setSystemTime or set the date with cy.clock(new Date(...))

cy.clock().then(clock => {
  clock.restore()
  clock.setSystemTime(new Date('2024-10-27T10:00:00.000Z'))
})

[CalCorbin]

I'm not having any success with the workaround in 13.17.0.

[ruohola]

Calling cy.clock().invoke('restore') before the second cy.clock(Date.UTC(…)) worked for me in cypress@13.8.1.

This is needed as if a mocked clock already exists, calling cy.clock() with any set of arguments just returns the existing clock: https://github.com/cypress-io/cypress/blob/v13.8.1/packages/driver/src/cy/commands/clock.ts#L49-L51

---

I'm also not using the cy.clock().then(clock => { … }) syntax, as those clock.… calls inside the then are run synchronously and don't get executed linearly with any interleaved test code, which gets confusing very easily.