cy commands from running and allow interaction with the application under
test. You can then "resume" running all commands or choose to step through the
"next" commands from the Command Log.
It is unsafe to
chain further commands that rely on a DOM element as the subject after
This does not set a
debugger in your code, unlike
cy.pause().getCookie('app') // Pause at the beginning of commands
cy.get('nav').pause() // Pause after the 'get' commands yield
Pass in an options object to change the default behavior of
|Displays the command in the Command log|
.pause()yields the same subject it was given.
- It is unsafe
to chain further commands that rely on a DOM element as the subject after
Pause after assertion
.pause()can be chained off of
cyor off another command.
.pause()is a utility command.
.pause()will not run assertions. Assertions will pass through as if this command did not exist.
.pause()cannot time out.
Pause and step through each
The commands above will display in the Command Log as:
When clicking on "Next: 'click'" at the top of the Command Log, the Command Log will run only the next command and pause again.