Jennifer Mann
6.2 KiB
title, comments, description
| title | comments | description |
|---|---|---|
| clock | true |
cy.clock overrides native global functions related to time, so you can test code using those functions in an easier, synchronous way. This includes the setTimeout, clearTimeout, setInterval, and clearInterval functions as well as controlling Date objects. Note that this only applies to the top window on a web page. It will not override the time functions on any iframes embedded on the web page.
cy.clock automatically restores the native functions in between tests without you having to explicitly restore them. You can still manually restore the functions within a test by calling .restore() on the clock object that cy.clock yields.
cy.clock pairs with cy.tick, which moves the clock along a certain number of milliseconds.
Subsequent calls to cy.clock will yield the clock object without re-overriding the native time functions.
If you call cy.clock before visiting a page with cy.visit, the page's native global functions will be overridden on window load, before any of your app code runs, so even if setTimeout, for example, is called on page load, it can still be controlled via cy.tick. This also applies if, during the course of a test, the page under test is reloaded or changed.
| Returns | a clock object. See clock API |
cy.clock()
Replaces setTimeout, clearTimeout, setInterval, clearInterval and Date and allows them to be controlled synchronously via cy.tick or the yielded clock object (see clock API).
The clock starts at the unix epoch (timestamp of 0). This means that when you instantiate new Date in your application, it will have a time of January 1st, 1970.
cy.clock( now )
Same as above, but starts the clock at the specified timestamp.
cy.clock( now, functionNames )
Same as above, but only overrides the functions in the array functionNames.
clock API
cy.clock yields a clock object with the following methods. You can also access the clock object via this.clock in a cy.then callback.
clock.tick(milliseconds)
Move the clock the specified number of milliseconds. Any timers within the affected range of time will be called.
clock.restore()
Restore all overridden native functions. This is automatically called between tests, so should not generally be needed.
Options
Pass in an options object to change the default behavior of cy.clock.
cy.clock( options )
cy.clock( now, options )
cy.clock( now, functionNames, options )
| Option | Default | Notes |
|---|---|---|
log |
true |
whether to display command in command log |
Usage
Create a clock and use it to trigger a setInterval
// your app code
var seconds = 0
setInterval(function(){
$('#seconds-elapsed').text(++seconds + ' seconds')
}, 1000)
// test code
cy
.clock()
.visit("/index.html")
.tick(1000)
.get("#seconds-elapsed")
.should("have.text", "1 seconds")
.tick(1000)
.get("#seconds-elapsed")
.should("have.text", "2 seconds")
Specify the now timestamp
// your app code
$('#date').text(new Date().toJSON())
// test code
const now = new Date(2017, 2, 14).getTime() // March 14, 2017 timestamp
cy
.clock(now)
.visit("/index.html")
.get("#date")
.contains("2017-03-14")
Specify which functions to override
This will only override setTimeout and clearTimeout and leave the other time-related functions as they are.
cy.clock(null, ["setTimeout", "clearTimeout"])
Access the clock object to synchronously move time
In most cases, it's easier to cy.tick to move time, but you can also use clock object yielded by cy.clock.
cy.clock().then(function (clock) {
clock.tick(1000)
})
You can call cy.clock again for this purpose later in a chain if necessary.
cy
.clock()
.get("#foo")
.type("Foo")
.clock().then(function (clock) {
clock.tick(1000)
})
The clock object is also available via this.clock in any .then callback.
cy
.clock()
.get("#foo").then(function ($foo) {
this.clock.tick(1000)
// do something with $foo ...
})
Access the clock object to restore native functions
In general, it should not be necessary to manually restore the native functions that cy.clock overrides, since this is done automatically between tests. But if you need to, the clock object yielded has .restore method.
cy.clock().then(function (clock) {
clock.restore()
})
Or via this.clock:
cy
.clock()
.get("#foo").then(function ($foo) {
this.clock.restore()
// do something with $foo ...
})
Example Recipe
{% note info Using cy.clock and cy.tick %} Check out our example recipe testing spying, stubbing and time {% endnote %}
Command Log
Create a clock and tick it 1 second
cy
.clock()
.tick(1000)
The command above will display in the command log as:
When clicking on the clock command within the command log, the console outputs the following:
