-
Notifications
You must be signed in to change notification settings - Fork 34
Replaced Copilot with Live Editor #851
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,10 +1,10 @@ | ||||||
| --- | ||||||
| title: "Using Auto-Healing in Copilot Test Execution" | ||||||
| page_title: "Using Auto-Healing in Copilot Editor Test Execution" | ||||||
| metadesc: "Enable Auto-Healing in the Copilot Editor to validate and fix element locators in real time, ensuring tests stay stable despite UI changes during execution." | ||||||
| title: "Using Auto-Healing in Live Editor Test Execution" | ||||||
| page_title: "Using Auto-Healing in Live Editor Test Execution" | ||||||
| metadesc: "Enable Auto-Healing in theLive Editor to validate and fix element locators in real time, ensuring tests stay stable despite UI changes during execution." | ||||||
| noindex: false | ||||||
| order: 4.916 | ||||||
| page_id: "using-auto-healing-in-copilot-test-execution" | ||||||
| page_id: "using-auto-healing-in-eive Editor-test-execution" | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix corrupted page_id. The page_id at line 7 contains garbled text "eive Editor" instead of "live-editor". This appears to be a copy-paste or encoding error. Correct to the proper slug format. -page_id: "using-auto-healing-in-eive Editor-test-execution"
+page_id: "using-auto-healing-in-live-editor-test-execution"📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||
| warning: false | ||||||
| contextual_links: | ||||||
| - type: section | ||||||
|
|
@@ -22,7 +22,7 @@ contextual_links: | |||||
|
|
||||||
| --- | ||||||
|
|
||||||
| With Auto-Healing enabled, you can execute test cases directly in the Copilot to validate element locators in real time. This helps ensure that any changes in the application’s UI are automatically detected and corrected during execution. This article discusses how auto-healing identifies and updates element locators while executing test cases in the Copilot. | ||||||
| With Auto-Healing enabled, you can execute test cases directly in the Live Editor to validate element locators in real time. This helps ensure that any changes in the application’s UI are automatically detected and corrected during execution. This article discusses how auto-healing identifies and updates element locators while executing test cases in the Live Editor. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
|
|
@@ -45,16 +45,16 @@ Here are the steps to produce: | |||||
| - Enter demopassword in the Password Input field. | ||||||
| - Click on Log in Button. | ||||||
|
|
||||||
| 1. Once you have created the test steps, click **Copilot**. | ||||||
| 1. Once you have created the test steps, click **Live Editor**. | ||||||
|  | ||||||
|
|
||||||
| 2. On the **Copilot** overlay, configure the required options and click **Launch**. | ||||||
| 2. On the **Live Editor** overlay, configure the required options and click **Launch**. | ||||||
|  | ||||||
|
|
||||||
| - Consider that the XPATH for the element Email address or phone number on step 2 changed. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix list indentation to comply with markdown standards. Lines 54 and 57 have list indentation violations (Expected: 0; Actual: 1) that violate the MD007 rule. The sub-items under the unordered list should have zero indentation at the start. - - Consider that the XPATH for the element Email address or phone number on step 2 changed.
+- Consider that the XPATH for the element Email address or phone number on step 2 changed.

- - When the test case is executed in the Live Editor with the Gen AI auto-healing feature enabled, Testsigma automatically identifies the updated XPath and successfully locates the element.
+- When the test case is executed in the Live Editor with the Gen AI auto-healing feature enabled, Testsigma automatically identifies the updated XPath and successfully locates the element.
Also applies to: 57-57 🧰 Tools🪛 markdownlint-cli2 (0.18.1)54-54: Unordered list indentation (MD007, ul-indent) 🤖 Prompt for AI Agents |
||||||
|  | ||||||
|
|
||||||
| - When the test case is executed in the Copilot with the Gen AI auto-healing feature enabled, Testsigma automatically identifies the updated XPath and successfully locates the element. | ||||||
| - When the test case is executed in the Live Editor with the Gen AI auto-healing feature enabled, Testsigma automatically identifies the updated XPath and successfully locates the element. | ||||||
|  | ||||||
| --- | ||||||
|
|
||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,10 @@ | ||
| --- | ||
| title: "FAQs on Testsigma Terminal" | ||
| pagetitle: "FAQs on Testsigma Copilot" | ||
| metadesc: "Find answers to frequently questions about Testsigma's Copilot (Testsigma Terminal), including its features, installation, usage, and how it helps resolve issues in test cases in real time" | ||
| pagetitle: "FAQs on Testsigma Live Editor" | ||
| metadesc: "Find answers to frequently questions about Testsigma's Live Editor (Testsigma Terminal), including its features, installation, usage, and how it helps resolve issues in test cases in real time" | ||
| noindex: false | ||
| order: 10.6 | ||
| page_id: "Frequently Asked Questions on Copilot" | ||
| page_id: "Frequently Asked Questions on Live Editor" | ||
| search_keyword: "" | ||
| warning: false | ||
| --- | ||
|
|
@@ -14,7 +14,7 @@ warning: false | |
|
|
||
| ### **1. Can I run the old Java agent and Testsigma Terminal on the same machine?** | ||
|
|
||
| **Answer:** No, only one active agent can run at a time. Testsigma Terminal automatically detects an existing Java agent and uses it for **Copilot** and test executions. | ||
| **Answer:** No, only one active agent can run at a time. Testsigma Terminal automatically detects an existing Java agent and uses it for **Live Editor** and test executions. | ||
|
|
||
| --- | ||
|
|
||
|
|
@@ -57,7 +57,7 @@ warning: false | |
|
|
||
| ### **7. Which agent is used for remote executions or ad-hoc runs?** | ||
|
|
||
| **Answer:** Testsigma Terminal integrates with the existing agent, which is used for remote executions, ad-hoc runs, and Copilot. | ||
| **Answer:** Testsigma Terminal integrates with the existing agent, which is used for remote executions, ad-hoc runs, and Live Editor. | ||
|
|
||
| --- | ||
|
|
||
|
|
@@ -73,7 +73,7 @@ warning: false | |
|
|
||
| #### **Managing Testsigma Terminal** | ||
|
|
||
| - **Stop:** Click **Quit Copilot**. | ||
| - **Stop:** Click **Quit Live Editor**. | ||
|
|
||
| - **Start:** Launch **Testsigma Terminal** from your applications. | ||
|
|
||
|
|
@@ -102,7 +102,7 @@ warning: false | |
|
|
||
| - Run: `sh Stop.sh` | ||
|
|
||
| - **Restart:** Relaunch **Testsigma Terminal** or click the **Restart** button on the **Copilot** homepage. | ||
| - **Restart:** Relaunch **Testsigma Terminal** or click the **Restart** button on the **Live Editor** homepage. | ||
|
|
||
|
|
||
| --- | ||
|
|
@@ -162,15 +162,15 @@ warning: false | |
|
|
||
| --- | ||
|
|
||
| ### **15. What should I do if I see a port error during Terminal or Copilot installation?** | ||
| ### **15. What should I do if I see a port error during Terminal or Live Editor installation?** | ||
|
|
||
| **Answer:** You may see an error screen during the download of a new Terminal or Copilot if all required ports are in use. This usually occurs when processes from a previous installation are still running. This article discusses resolving port-in-use errors when installing the Terminal. | ||
| **Answer:** You may see an error screen during the download of a new Terminal or Live Editor if all required ports are in use. This usually occurs when processes from a previous installation are still running. This article discusses resolving port-in-use errors when installing the Terminal. | ||
|
|
||
|  | ||
|
|
||
| **Steps to Resolve for macOS:** | ||
|
|
||
| 1. Quit the **Copilot** if it is open. | ||
| 1. Quit the **Live Editor** if it is open. | ||
|  | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Update image alt text to match updated terminology. The image caption at line 174 still references "Quit Copilot" while the text at line 173 has been updated to "Quit the Live Editor". Update the image caption to maintain consistency. -1. Quit the **Live Editor** if it is open.
- 
+1. Quit the **Live Editor** if it is open.
+ 
🤖 Prompt for AI Agents |
||
|
|
||
| 2. Open Activity Monitor and end any **wrapper** or **atto** processes. | ||
|
|
@@ -197,7 +197,7 @@ warning: false | |
|
|
||
| **Steps to Resolve for Windows:** | ||
|
|
||
| 1. Close the **Copilot** and any previously running agent. | ||
| 1. Close the **Live Editor** and any previously running agent. | ||
|
|
||
| 2. Open **Task Manager** and end the following processes, if they are running: | ||
| - **abd** | ||
|
|
@@ -226,16 +226,16 @@ warning: false | |
| --- | ||
|
|
||
|
|
||
| **16. What should I do if I see an authentication error while installing the Terminal or Copilot?** | ||
| **16. What should I do if I see an authentication error while installing the Terminal or Live Editor?** | ||
|
|
||
| **Answer:** Authentication errors during installation occur if the user switches accounts through the installation or if leftover processes or files from a previous installation remain. To resolve this, perform the common cleanup process as described in the port busy issue. | ||
|
|
||
|  | ||
|
|
||
| --- | ||
|
|
||
| **17. Why do test steps not update and features not work in the Copilot?** | ||
| **17. Why do test steps not update and features not work in the Live Editor?** | ||
|
|
||
| **Answer:** The Copilot may launch the local browser and execute test steps but fail to update results or allow recording additional steps due to agent incompatibility with Chrome version 139. To fix this issue, delete the entire **.testsigma** folder and restart the Terminal. This will trigger a new agent download and restore full Copilot functionality. | ||
| **Answer:** The Live Editor may launch the local browser and execute test steps but fail to update results or allow recording additional steps due to agent incompatibility with Chrome version 139. To fix this issue, delete the entire **.testsigma** folder and restart the Terminal. This will trigger a new agent download and restore full Live Editor functionality. | ||
|
|
||
| --- | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix spacing error in metadesc.
The metadesc at line 4 contains "theLive Editor" with missing space. This affects search engine optimization and readability.
📝 Committable suggestion
🤖 Prompt for AI Agents