> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/test-steps/utility/debug-element.md).

# Debug Element

Debug Element writes details about an [Element](/elements/creating-elements.md) into the Test Case result. Use it while building or fixing a Flow to see what the runner resolved on the page.

![Debug element Test Step](https://app.does.qa/screenshots/node/utility_debug_element.png)

## When to use it

* Confirm an Element selector still matches after a UI change.
* Inspect Element output when a Check or Touch step fails unexpectedly.
* Pair with [Debug Value](/test-steps/utility/debug-value.md) when both page output and stored Values matter.

## Configure

### Basics

| Field       | What to set                                                           |
| ----------- | --------------------------------------------------------------------- |
| **Element** | The [Element](/elements/creating-elements.md) to record in the result |

### Advanced

| Field              | What to set                                          |
| ------------------ | ---------------------------------------------------- |
| **Status on fail** | [Failed Status](/test-step-options/failed-status.md) |

{% hint style="info" %}
**Pro tip:** Debug Element adds no user-facing action. Place it before the failing step, run the Test Case once, then remove it when the Flow is stable.
{% endhint %}

## Related

* [Debug Value](/test-steps/utility/debug-value.md)
* [Creating Elements](/elements/creating-elements.md)
* [Utilities](/test-steps/utility.md)

**Tags:** `utility`, `debug`, `element`, `log`, `console`, `print`