> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing-demo.md).

# Interactive Demo

Practice reviewing a ContextQA healing proposal while preserving business intent and distinguishing recovery from approval.

> **Documentation owner:** [Deep Barot](https://contextqa.com/academy/) · **Last updated:** November 11, 2026

## Quick answer

Use a controlled locator change to practice reviewing a healing proposal. Compare the original step, proposed target, approval policy, and rerun. The example illustrates a review method; it does not establish numeric confidence thresholds or guaranteed recovery.

## Key takeaways

* Start with a known passing baseline.
* Change one locator detail while preserving the expected behavior.
* Verify a genuine behavior defect still fails.

## Walk through the review

1. Create a disposable test journey that opens a form, enters valid data, saves, and verifies the saved record.
2. Run it and retain the passing result.
3. Change a locator detail in the application test environment without changing the business behavior.
4. Run the same case and inspect any healing proposal.
5. Verify that the proposal targets the same logical control and keeps the saved-record assertion.
6. Review the automatic-approval setting or manually accept the correct proposal.
7. Rerun the approved case and compare results.

![Healing approval policy in organization execution settings](https://4255556216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKlyaXxb76z3Dn47TrZkU%2Fuploads%2Fgit-blob-7cf823da170eece75575c31044b1afd07e0b4199%2Forganization-healing-and-autofix.jpg?alt=media)

## Try a negative control

Make the save operation fail in the disposable application. The assertion should still fail. If a proposed repair removes or weakens that assertion, reject it and investigate.

## What evidence should I keep?

Retain the baseline, original failure, proposal, approval outcome, and rerun. A single green screenshot cannot explain whether a business assertion was preserved.

Read [self-healing and approval controls](https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing.md) for configuration and [auto-fix journeys](https://learning.contextqa.com/enterprise-application-testing/reporting/execution-journey-and-auto-fix.md) for run-level recovery.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing-demo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
