Files
cypress/docs/source/api/commands/debug.md
T
Brian Mann 6acb418230 docs: WIP, normalizing all of the yields for every command
- all of the straightforward ones are done
- still working on the custom / complex ones
2017-06-25 16:22:39 -04:00

1.6 KiB

title, comments
title comments
debug false

Set a debugger and log what the previous command yields.

{% note warning %} You need to have your Developer Tools open for .debug() to hit the breakpoint. {% endnote %}

Syntax

.debug()
.debug(options)

Usage

.debug() can be chained off of cy or any cy command.

{% fa fa-check-circle green %} Valid Usage

cy.debug().getCookie('app') // Pause to debug at beginning of commands
cy.get('nav').debug()       // Debug the `get` command's yield

Arguments

{% fa fa-angle-right %} options (Object)

Pass in an options object to change the default behavior of .debug().

Option Default Description
log true {% usage_options log %}

Yields {% helper_icon yields %}

{% yields same_subject .debug %}

Timeouts {% helper_icon timeout %}

.debug() cannot timeout.

Examples

Debug

Pause with debugger after .get()

cy.get('a').debug().should('have.attr', 'href')

Command Log

Log out the current subject for debugging

cy.get(".ls-btn").click({ force: true }).debug()

The commands above will display in the command log as:

Command Log debug

When clicking on the debug command within the command log, the console outputs the following:

console.log debug

See also