dev >> main

src/pages/docs/FAQs/web-apps/automating-captcha.md

@@ -10,10 +10,10 @@ contextual_links:
   name: "Contents"
 - type: link
   name: "1. Why is CAPTCHA used?"
-  url: "#1-why-is-captcha-used?"
+  url: "#1-why-is-captcha-used"
 - type: link
   name: "2. Can I automate CAPTCHA testing in my test environment?"
-  url: "#2-can-i-automate-captcha-testing-in-my-test-environment?"
+  url: "#2-can-i-automate-captcha-testing-in-my-test-environment"
 ---
 
 ---

src/pages/docs/FAQs/web-apps/why-chrome-extension.md

@@ -28,7 +28,7 @@ With Testsigma’s Chrome Extension you capture these elements and record the us
 <br>
 
 ---
-##**Security Disclaimer**
+## **Security Disclaimer**
 
 * Testsigma Chrome Extension doesn’t  track user browsing outside the application and does not collect private information such as IP address and passwords.
 * We don’t modify the source code of your application.

src/pages/docs/agent/setup-on-kubernetes.md

@@ -438,6 +438,6 @@ kubectl -n testsigma delete pvc data-ts-agent-testsigma-agent-0
 | Pod rejected on creation | The namespace enforces the `restricted` Pod Security Standard. The agent image requires `baseline`. |
 | Browser crashes mid test | The browser needs more shared memory. Raise `browsers.chrome.shmSize` and its memory limit together. |
 
-For issues with agent startup or registration itself, see [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/setup-issues/).
+For issues with agent startup or registration itself, see [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/how-to-fix-setup-issues/).
 
 ---

src/pages/docs/agent/troubleshooting/how-to-fix-setup-issues.md

@@ -177,7 +177,7 @@ Follow the below steps to fix the issue.
 2. Restart the Agent.
 3. If the Agent is not updated, update the Agent. *For more information, refer to the [documentation on updating Agents](https://testsigma.com/docs/agent/update-agent-manually/)*.
 
-If the above troubleshooting steps does not resolve the issue, contact Testsigma support at [support@testsigma.com](mailto:support@testsigma.com) with the Agent logs files. *For more information on how to fetch agent logs refer to the [documentation on torubleshooting agent logs](https://testsigma.com/docs/agent/troubleshooting/logs/)*.
+If the above troubleshooting steps does not resolve the issue, contact Testsigma support at [support@testsigma.com](mailto:support@testsigma.com) with the Agent logs files. *For more information on how to fetch agent logs refer to the [documentation on troubleshooting agent logs](https://testsigma.com/docs/agent/troubleshooting/how-to-configure-agent-logs/)*.
 
 
 --- 

src/pages/docs/agent/update-drivers-manually.md

@@ -19,7 +19,7 @@ contextual_links:
   url: "#adding-drivers-manually"
 - type: link
   name: "Additional steps for Mac or Linux"
-  url: "#additional-steps-for-maclinux"
+  url: "#additional-steps-for-mac-or-linux"
 
 ---
 

src/pages/docs/ai-agents/analyzer.md

@@ -43,44 +43,47 @@ The Analyzer Agent analyzes a failed test step and returns the error type, the r
 
 2. Select the run that contains failed test steps.
 
-3. Open the test case with failures and select the failed test step.
+3. Click the test case with failures.
 
-   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. On the **Test Case Results** page, select the failed step.
 
-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)
+   The **ANALYZER VERDICT** section on the step already shows a short analysis of the failure. Use the Analyzer Agent for suggested fixes you can apply, follow-up questions, and bug reports. For details on the verdict, refer to the [documentation on debugging test case failures](https://testsigma.com/docs/runs/debug-test-case-failures/).
 
-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.
+5. Click **Analyze with Agent** in the action bar at the bottom of the page.
+   ![Analyze with Agent](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Analyze_with_Agent_Results_2.png)
+
+   The **Analyzer with Atto** panel opens and reads "Analyzing step failure..." while it runs.
+
+6. Review the analysis.
+   ![Anayzer Analysis](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Anayzer_Analysis.png)
+
+   | **Section** | **What it shows** |
+   |---|---|
+   | **Error Type** | The failure type identified during execution |
+   | **Root Cause** | Why the step failed |
+   | **Visual Evidence** | Screenshots **At the time of Recording** and **At the time of Execution**. Only the execution screenshot appears when no recording screenshot exists. |
+   | **Suggestions** | Numbered fixes you can apply to the 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. In the **Suggestions** list, select the suggestion you want to apply.
+1. In the **Suggestions** list, select one suggestion. **Apply Fix** stays disabled until you select one.
 
-   [[info | **NOTE**:]]
-   | You can select only one suggestion at a time.
+2. Click **Apply Fix**. Atto returns an **Add/Update Step** card. 
 
-2. Click **Apply Fix**.
-   ![](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Analyze_with_Agent_Results.png)
+3. Click **Add/Update Step**.
+   ![Add Step](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Apply_Fix_Update_Step.png)
+   In the step list, the updated step appears as an extra row below the original steps, marked with the Analyzer icon. The current result still shows the original step as failed, because the change applies from the next run.
 
-   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. Re-run the test to confirm the fix.
+   - For a test plan run, click the run number in the breadcrumb to return to **Run Results**, then click **Rerun**.
+   - For a dry run, click **Re-Run** in the page header.
 
-3. Compare the two versions of the step.
-
-4. Click **Update Step** to apply the change.
-
-5. Rerun the test to validate the fix.
+   The next run uses the updated step.
 
 ---
 
@@ -98,6 +101,8 @@ The Analyzer Agent analyzes a failed test step and returns the error type, the r
 [[info | **NOTE**:]]
 | 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".
+> <p class="additional-info">Additional Information</p>
+>
+> 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".
 
 ---

src/pages/docs/api/examples/trigger-test-plan-wait-completion.md

@@ -30,7 +30,7 @@ You should already be familiar with creating and running Test Plans. Refer to th
 | You need to authenticate these requests with your Testsigma API Key.  To know more about obtaining API Keys, refer to the [documentation on generating API keys](https://testsigma.com/docs/configuration/api-keys/)
 
 ---
-##**Checking the Test Run Results**
+## **Checking the Test Run Results**
 
 The below steps give an overview of how the script given at the bottom of this page works:
 
@@ -53,7 +53,7 @@ We can poll the Test Plan Execution Results API with this Run ID at regular inte
 We have provided the Powershell and Bash scripts for the same below. Please feel free to make changes as required and plug the same into your CI Pipeline.
 
 ---
-##**Powershell script**
+## **Powershell script**
 
 The Script triggers the executions and also waits until the Timeout(MAX\_WAIT\_TIME\_FOR\_SCRIPT\_TO\_EXIT) for the execution to complete.
 
@@ -182,7 +182,7 @@ saveFinalResponseToAFile
 
 
 ---
-##**Bash Script**
+## **Bash Script**
 
 ```shell
 #!/bin/bash

src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md

@@ -14,7 +14,7 @@ contextual_links:
   url: "#prerequisites"
 - type: link
   name: "Steps to Get OpenAI Details"
-  url: "#Steps-to-get-openai-details"
+  url: "#steps-to-get-openai-details"
 ---
 
 ---

src/pages/docs/atto/generative-ai/generate-tests/automate-test-cases.md

@@ -99,6 +99,6 @@ When you generate automated test cases, Atto checks for existing test cases. If
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/).
-| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
+| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
 
 ---

src/pages/docs/atto/generative-ai/generate-tests/desktop.md

@@ -82,6 +82,6 @@ Testsigma’s Gen AI capabilities help you streamline test case creation for Des
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/).
-| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
+| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
 
 ---

src/pages/docs/atto/generative-ai/generate-tests/mobile-web.md

@@ -101,7 +101,7 @@ You can generate test cases for mobile web applications using Testsigma’s Gene
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/).
-| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
+| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
 
 
 ---

src/pages/docs/atto/generative-ai/generate-tests/mobile.md

@@ -98,7 +98,7 @@ You can generate test cases for android and iOS applications using Testsigma’s
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/).
-| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
+| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent in Testsigma](https://testsigma.com/docs/ai-agents/generator/).

src/pages/docs/atto/generative-ai/generate-tests/salesforce.md

@@ -76,6 +76,6 @@ You can quickly generate test cases for Salesforce requirements in Testsigma usi
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/).
-| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
+| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
 
 ---

src/pages/docs/atto/generative-ai/generate-tests/web.md

@@ -101,6 +101,6 @@ You can generate test cases for web and mobile web applications using Testsigma
 
 [[info | **NOTE**:]]
 | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/).
-| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
+| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). 
 
 ---

src/pages/docs/atto/generative-ai/overview.md

@@ -14,7 +14,7 @@ contextual_links:
   url: "#prerequisites"
 - type: link
   name: "Testsigma Copiot Capabilities"
-  url: "#testsigma-copiot-capabilities"
+  url: "#testsigma-copilot-capabilities"
 - type: link
   name: "Generate Tests from Generative AI"
   url: "#generate-tests-from-generative-ai"