Skip to content

dev >> main #1089

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bharathk-testsigma merged 1 commit into from
Sep 2, 2026
Merged

dev >> main #1089

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 39 additions & 39 deletions src/pages/docs/ai-agents/analyzer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Analyzer Agent in Testsigma"
page_title: "Analyzer Agent in Testsigma"
metadesc: "The Analyzer Agent in Testsigma is your intelligent assistant that autonomously reviews test executions | This article discusses the Analyzer Agent in Testsigma"
metadesc: "The Analyzer Agent in Testsigma analyzes a failed test step and returns the error type, root cause, visual evidence, and suggestions | This article discusses the Analyzer Agent in Testsigma"
noindex: false
order: 4.815
page_id: "analyzer-agent-in-testsigma"
Expand All @@ -25,79 +25,79 @@ contextual_links:

---

The Analyzer Agent in Testsigma analyzes failed test steps and provides actionable insights. It identifies the error type, determines the root cause, provides visual evidence captured during execution, and suggests possible fixes. This article discusses how to analyze step failures and take action using the Analyzer Agent.
The Analyzer Agent analyzes a failed test step and returns the error type, the root cause, the visual evidence captured during execution, and a set of suggestions. Apply a suggestion to update the step, or report the failure to your bug tracking tool, without leaving the results page.

---

> <p id="prerequisites">Prerequisites</p>
>
>
> Before you begin, ensure that:
> 1. At least one test plan has been executed.
> 2. The test plan contains failed test cases.

> 1. At least one test plan or dry run has been executed.
> 2. The run contains a failed test step.

---

## **Steps to Analyze Step Failures**

1. From the left navigation bar, click **Run Results**.
![Run Results](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Nav_Run_Results_from_Dashboard.png)

2. Select the test plan that contains failed test steps.
2. Select the run that contains failed test steps.

3. Open the test case with failures and select the failed test step.

4. In the **Step Details** panel, click **Analyze with Agent**. This will open the **Analyzer Agent** overlay.
![Analyze with Agent](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Analyze_with_Agent_from_Results.png)
The step header shows the error message. Click **Read more** to see the full message. The **Analysis** tab shows the error code, such as **#NO_SUCH_ELEMENT**, along with the **Visual Evidence** section.

4. Click **Analyze with Agent** in the action bar at the bottom of the page.
![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Analyze_with_Agent_Results.png)

5. Wait for the **Analyzer Agent** to complete the analysis.
5. Review the analysis, which displays:
<!-- Image Placeholder: Analysis -->
- **Error Type**: The category of failure identified during execution, such as ELEMENT_NOT_FOUND.
- **Root Cause**: An explanation of why the step failed, based on the error message and the captured evidence.
- **Visual Evidence**: The screenshot captured at the time of execution. Click **Expand Images** to view it at full size, or the download icon to save it.
- **Suggestions**: A numbered list of ways to resolve the failure.

6. Review the analysis in **Analyzer Agent** overlay, which displays:
![Analysis](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Analysis_from_Analyzer_Agent.png)
- **Error Type**: Displays the category of failure identified during test execution.
- **Root Cause**: Describes the underlying reason for the failure based on execution analysis.
- **Visual Evidence**: Displays screenshots captured during recording and execution to support failure analysis.
- **Suggested Fixes**: Displays recommended actions to resolve the failed test step.
[[info | **NOTE**:]]
| To ask a follow-up question about the failure, enter it in **Debug with Atto** and click **Analyze**.

**Additional Information**: Responses are generated by Atto AI. Review the analysis before acting on it. Use the feedback icons or **Give Feedback** to tell us how useful it was.

---

## **Apply Fix Using Analyzer Agent**

1. From the **Analyzer Agent** overlay, select the fix you want to apply.
![Select Fix](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Select_Fix_Option.png)
1. In the **Suggestions** list, select the suggestion you want to apply.

[[info | **NOTE**:]]
| You can select only one suggestion at a time.

2. Click **Apply Fix**.
![Apply Fix](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Apply_fix_from_Agent_Suggestion.png)
![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Analyze_with_Agent_Results.png)

3. Wait for the **Analyzer Agent** to generate the required fix.
Atto generates the fix and returns an **Update Test Step** card explaining what it found, followed by the current version of the step and the proposed version.

4. Click **Add Step**, **Update Step**, or **Update Step Settings**, as suggested by the **Analyzer Agent**.
![Update as per suggestion](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Update_Add_Step_Setting.png)
3. Compare the two versions of the step.

5. Verify that the changes are applied to the test step.
![Verify the changes](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Verify_the_Updated_Test_Step_from_Atto.png)
4. Click **Update Step** to apply the change.

6. Rerun the test plan to validate the fix.
5. Rerun the test to validate the fix.

---

## **Report a Bug Using Analyzer Agent**

1. From the **Analyzer Agent** overlay, click **Report Bug**.
![Report Bug](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Report_Bug_From_Agent.png)
1. In the **Analyzer with Atto** panel, click **Report Bug**. The **QA Agent** panel opens.

2. Select the bug tracking application from **QA Agent** overlay.
![Select Bug Tracking App](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Select_Bug_Tracking_App_from_Overlay.png)
2. Select your bug tracking tool from the dropdown at the top right.
![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Bug_Reporting_Tools.png)

3. Review the prefilled bug details, such as **Team**, **Project**, and **Title**.
![Review Details](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Review_Prefilled_Bug_Details.png)

> The fields displayed vary based on the selected bug tracking tool.

4. Click **Report Bug**.
![Report](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Report_Bug_Button_QA_Agent.png)
3. Do one of the following:
- To raise a new issue, open the **Create New** tab, review the prefilled details, and click **Report Bug**.
- To attach the failure to an issue that already exists, open the **Link To Issue** tab, search for the issue, and click **Link To Ticket**.

[[info | **NOTE**:]]
| To link the failure to an existing issue, click **Link to Issue**, search for the issue in the selected bug tracking application, and then click **Link to Ticket**.
| The fields displayed vary based on the selected bug tracking tool.

---
**Additional Information**: If the tool returns no projects, check that the credentials configured for it have access to the projects you expect. For Jira, the panel reads "For given JIRA Credentials, the projects list is empty. Please make sure it has the right access to required projects on JIRA".

---
109 changes: 93 additions & 16 deletions src/pages/docs/auto-healing/auto-healing-insights.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Auto-Healing Insights"
page_title: "Auto-Healing Insights"
metadesc: "Review Auto-Heal Insights in Testsigma to see which elements were healed, how locators were updated, and decide if the changes should be made permanent."
metadesc: "Review how auto-healing behaved during a run in Testsigma | See which locator failed, what replaced it, and decide whether to keep the change."
noindex: false
order: 4.918
page_id: "auto-healing-insights"
Expand All @@ -10,32 +10,109 @@ contextual_links:
- type: section
name: "Contents"
- type: link
name: "Steps to View Auto-Heal Insights"
url: "#steps-to-view-auto-heal-insights"
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Identify Healed Steps in a Run"
url: "#identify-healed-steps-in-a-run"
- type: link
name: "Review the Heal on the Analysis Tab"
url: "#review-the-heal-on-the-analysis-tab"
- type: link
name: "View Autoheal Details"
url: "#view-autoheal-details"
- type: link
name: "Read the Locator Trace"
url: "#read-the-locator-trace"
- type: link
name: "When a Heal Fails"
url: "#when-a-heal-fails"
- type: link
name: "Fix the Locator Yourself"
url: "#fix-the-locator-yourself"
---

---

Review how auto-healing behaved during a run to see which locator failed, what replaced it, and whether to keep the change. Insights open from the healed step on the results page.

---

> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that:
> 1. Auto-healing is enabled for the project.
> 2. A run has been completed in which at least one step was healed.

---

## **Identify Healed Steps in a Run**

1. Open the test case results for the run.

2. Select the healed step.
![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Auto_Healing_Insights_New.png)

[[info | **NOTE**:]]
| A healed step reports **Passed**, because the step completed. The run itself carries a **Healed** status in the run list, which distinguishes it from a run that passed without intervention.

---

## **Review the Heal on the Analysis Tab**

The **Analysis** tab shows a **Healed this step** card explaining what happened: "Existing locator failed during execution, and we've auto-healed it using AI. The element locator was updated with a new XPath to ensure your test continues to run smoothly."

Choose one of the following:
![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Healed_Details_in_Results.png)
- Click **Approve as Primary** to make the healed locator the locator the test uses from now on.
- Click **Ignore** to leave the original locator in place. The heal still applied to this run only.

[[info | **NOTE**:]]
| In the **Visual Evidence** section, the current run panel carries a **Healed** badge, and the **Element** field has an edit icon for correcting the locator directly.

---

## **View Autoheal Details**

Open the **Autoheal Details** panel to see exactly which locator changed.

The panel shows:
![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Auto_HeaL_Accept_Reject.png)
- The element that was healed, named at the top.
- The prompt "Do you want to update the autohealed element in all the linked test cases?" with **Update** and **Ignore** buttons.
- The healing method and how long it took, such as "Autohealed using CSS Selector" and "32s 912ms".
- The locator that failed, struck through, followed by the locator that replaced it.

Click **Update** to apply the healed locator across every test case linked to the element, or **Ignore** to leave those test cases unchanged.

**Additional Information**: Use the feedback icons under "Is this autoheal helpful?" to tell us whether the heal was correct. The same feedback icons appear on the auto-healed banner above the step list.

---

Once you’ve executed your tests using Auto-Heal, you can review detailed insights to understand how the feature worked during execution. The Auto-Heal Insights section helps you identify which elements were healed, how their locators were updated, and whether any of those updates should be made permanent.
## **Read the Locator Trace**

Every auto-heal event records a locator trace: the full sequence the engine worked through to arrive at a heal, and whether that heal succeeded or failed.

This article discusses how to view and manage Auto-Heal insights after test execution.
Use the trace to understand why a particular locator was chosen, or why no replacement could be found.

**Additional Information**: The locator trace is provided by the Auto Heal V2 architecture.

---

## **Steps to View Auto-Heal Insights**
## **When a Heal Fails**

A heal attempt that fails gets the same root cause treatment as a failed step. Open the **Root cause** block on the **Analysis** tab and click **Explain this failure** to see why the engine could not resolve the element.

1. Click the test step where the element was auto-healed to view insights.
[[info | **NOTE**:]]
| This requires Analyzer V2. Without it, a failed heal reports that it did not succeed, but no explanation is generated.

2. Go to the **Step Result** and click **Auto-Heal Details**. This opens the **Auto-Heal Details** overlay.
![Auto-Heal Details](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Auto_heal_insights_1.png)
---

3. Review the **Auto-Heal Insights**.
![Auto-Heal Insights](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Auto_heal_insights_2.png)
## **Fix the Locator Yourself**

4. To update the element value permanently, click **Update**.
![Update](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Auto_heal_insights_3.png)
If you would rather not accept the healed locator, you have two alternatives:

5. On the **Update Element** dialog, click **Update** again to confirm.
![Update](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Auto_heal_insights_4.png)
- **Update element** corrects the locator directly. In the **Visual Evidence** section, the **Element** field on the current run side carries an edit icon for this.
- **Relearn step** re-captures the step so a fresh locator is recorded.

---
---
Loading
Loading