> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getdecipher.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test Failures

> Understanding when tests fail and what data you receive

When a test runs, Decipher executes each step and tracks whether it succeeds or fails. This page explains when a test is marked as failed and what information you get to help diagnose the issue.

## When a Test Fails

A test is marked as **failed** when any step does not complete successfully. This includes:

* **Element not found** - The target element (button, input, link) couldn't be located on the page
* **Action failed** - A click, type, or other interaction didn't produce the expected result
* **Assertion failed** - A validation check didn't pass (e.g., expected text wasn't present)

## Failure Data

Each test run captures detailed information to help you understand what went wrong:

### Screenshots

* Screenshot taken at each step
* Final screenshot showing the state when failure occurred
* Visual comparison to identify UI changes

### Logs

* Console logs from the browser
* Network request logs

### Step Details

* Which step failed and why
* Time taken for each step

### Session Recording

* Full video replay of the test execution
* See exactly what happened leading up to the failure

## Viewing Failure Information

1. Go to your [Tests dashboard](https://app.getdecipher.com/tests)
2. Click on a failed test run
3. Review the step-by-step breakdown
4. Click on the failed step to see detailed logs and screenshots

<Tip>
  Use the session recording to watch the test execution in real-time. This often reveals issues that aren't obvious from logs alone.
</Tip>

## Suggested Fixes

When a test fails because your product has changed — for example, a UI was refreshed, page elements were moved or renamed, or underlying data became stale — Decipher automatically self-heals simple step failures without any action needed from you. For more involved changes, Decipher suggests specific fixes to bring the test back in sync with the current state of your application.

To view suggested fixes, expand the **Suggested Fixes** section on a failed test run.

<Frame>
  <img src="https://mintcdn.com/decipherai/7DfBb9M7wvlFmFV1/images/suggested-fixes.png?fit=max&auto=format&n=7DfBb9M7wvlFmFV1&q=85&s=2dfa8305bba4c80429e723fc72472ae6" alt="Suggested fixes for a failed test run" width="3984" height="1738" data-path="images/suggested-fixes.png" />
</Frame>

To apply a fix, click **Apply** on the suggestion. You can also select multiple fixes and click **Apply Selected** to queue them all at once. Applied fixes automatically update your test steps.

***

*Need help? [Contact our support team](mailto:team@getdecipher.com).*