diff --git a/assets/images/kane-ai/features/new-test-run-instance/test-run-instance-auto-heal-step.png b/assets/images/kane-ai/features/new-test-run-instance/test-run-instance-auto-heal-step.png new file mode 100644 index 000000000..0adb529e5 Binary files /dev/null and b/assets/images/kane-ai/features/new-test-run-instance/test-run-instance-auto-heal-step.png differ diff --git a/assets/images/kane-ai/features/new-test-run-instance/test-run-instance-share.png b/assets/images/kane-ai/features/new-test-run-instance/test-run-instance-share.png new file mode 100644 index 000000000..6d1fcfb00 Binary files /dev/null and b/assets/images/kane-ai/features/new-test-run-instance/test-run-instance-share.png differ diff --git a/assets/images/mobile-app-testing/ai-test-case-generator-walkthrough.mp4 b/assets/images/mobile-app-testing/ai-test-case-generator-walkthrough.mp4 new file mode 100644 index 000000000..ab24e8dc8 Binary files /dev/null and b/assets/images/mobile-app-testing/ai-test-case-generator-walkthrough.mp4 differ diff --git a/assets/images/rbac-roles-and-permissions/create-new-role.png b/assets/images/rbac-roles-and-permissions/create-new-role.png index 335900103..3bb8f5460 100644 Binary files a/assets/images/rbac-roles-and-permissions/create-new-role.png and b/assets/images/rbac-roles-and-permissions/create-new-role.png differ diff --git a/assets/images/rbac-roles-and-permissions/roles-and-permissions-page.png b/assets/images/rbac-roles-and-permissions/roles-and-permissions-page.png index 51782be10..897e28a0c 100644 Binary files a/assets/images/rbac-roles-and-permissions/roles-and-permissions-page.png and b/assets/images/rbac-roles-and-permissions/roles-and-permissions-page.png differ diff --git a/docs/agent-features-and-metrics.md b/docs/agent-features-and-metrics.md index 8511a0b48..d43b6e023 100644 --- a/docs/agent-features-and-metrics.md +++ b/docs/agent-features-and-metrics.md @@ -11,7 +11,7 @@ keywords: - voice agent - phone caller agent - image analyzer agent - - agent to agent testing + - agent testing url: https://www.testmu.ai/support/docs/agent-features-and-metrics/ site_name: LambdaTest slug: agent-features-and-metrics/ diff --git a/docs/agent-to-agent-faqs.md b/docs/agent-to-agent-faqs.md index e7f24c3dd..390b424bd 100644 --- a/docs/agent-to-agent-faqs.md +++ b/docs/agent-to-agent-faqs.md @@ -1,11 +1,11 @@ --- id: agent-testing-platform-faqs -title: Agent to Agent FAQs !! +title: Agent Testing Platform FAQs hide_title: false sidebar_label: FAQs -description: Get quick answers to all your Agent to Agent queries with our comprehensive FAQs! +description: Get quick answers to all your Agent Testing Platform queries with our comprehensive FAQs! keywords: - - Agent to Agent FAQs + - Agent Testing FAQs - FAQs url: https://www.testmuai.com/support/docs/agent-testing-platform-faqs/ site_name: TestMu AI @@ -44,7 +44,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; Below are a few commonly asked questions about our Agent Testing Platform: -#### 1. **Does Agent to Agent provide AI-enabled translation or multilingual analysis capabilities for testing?** +#### 1. **Does the Agent Testing Platform provide AI-enabled translation or multilingual analysis capabilities for testing?** Yes. It supports AI-enabled multilingual requirement analysis, allowing teams to extract and analyze requirements from documents written in multiple languages. It generates test scenarios that account for multilingual support requirements defined in agent specifications and supports testing AI agents that handle multiple languages across interactions. diff --git a/docs/ai-agent-testing-platform-overview.md b/docs/ai-agent-testing-platform-overview.md index 69f622e88..481f0a2c1 100644 --- a/docs/ai-agent-testing-platform-overview.md +++ b/docs/ai-agent-testing-platform-overview.md @@ -9,7 +9,7 @@ keywords: - agent evaluation platform - voice agent testing - chat agent testing - - agent to agent testing + - agent testing - ai agent qa url: https://www.testmu.ai/support/docs/ai-agent-testing-platform-overview/ site_name: LambdaTest @@ -134,7 +134,7 @@ The platform is built as a cloud-native, API-first system composed of three logi **Testing Flow:** -`Requirements Input` → `Scenario Generation` → `Agent-to-Agent Execution` → `AI Evaluation` → `Results & Go-Live` +`Requirements Input` → `Scenario Generation` → `Agent Execution` → `AI Evaluation` → `Results & Go-Live`
diff --git a/docs/appium-languages-and-frameworks.md b/docs/appium-languages-and-frameworks.md
index c19226f24..a2de94856 100644
--- a/docs/appium-languages-and-frameworks.md
+++ b/docs/appium-languages-and-frameworks.md
@@ -150,6 +150,49 @@ We are preparing documentation for more frameworks. If you want us to prioritize
:::
+
+
+## Using the Appium Agent Skill with TestMu AI
+***
+
+The [appium-skill](https://github.com/LambdaTest/agent-skills/tree/main/appium-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The appium-skill package includes:
+
+```
+appium-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Appium Agent Skill
+***
+
+Install a Appium Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/appium-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/appium-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only appium-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
-Once this is complete, you can now run the test by clicking on start session. Once you start the session, a video recording along with detailed information and logs of the test run will be available on the [
diff --git a/docs/application-setup-via-gui.md b/docs/application-setup-via-gui.md
index 9eb39c8c2..04d40750e 100644
--- a/docs/application-setup-via-gui.md
+++ b/docs/application-setup-via-gui.md
@@ -69,13 +69,13 @@ Wait for the file to upload and process. A success message will indicate when yo
> Learn how to [Upload Apps on
+> To get your Username and Access Key, go to your [
Update your username and access key in the "Config.properties" file.
@@ -95,7 +95,7 @@ Below is the step-by-step execution of the AppVeyor CI pipeline.
2. Push the changes to your integrated GitHub repository. For example, we have changed the test name in the forked repository.
3. Once the edit is complete, click on "Commit Changes" to save and commit the changes made. AppVeyor CI is activated as soon as this step is done since we have used "push event" for triggering the AppVeyor CI.
-4. As soon as the AppVeyor CI is triggered (through push event in this case), a new build can be seen in the "Timeline" on your [
+4. As soon as the AppVeyor CI is triggered (through push event in this case), a new build can be seen in the "Timeline" on your [
5. Now based on the tests, this build can pass or fail. If passed, a green tick along with the term **Passed** will appear in the summary of the test. Else if failed, a red cross will appear instead, along with the term **Failed**, as shown below.
diff --git a/docs/authentication.md b/docs/authentication.md
index 76fa40706..f123775ed 100644
--- a/docs/authentication.md
+++ b/docs/authentication.md
@@ -64,7 +64,7 @@ For example -
---
-The auth option will help you in specifying your username and access key. You can find your username and access key in the [
diff --git a/docs/automated-ss-api.md b/docs/automated-ss-api.md
index d28f0da48..59d3fcd6b 100644
--- a/docs/automated-ss-api.md
+++ b/docs/automated-ss-api.md
@@ -65,7 +65,7 @@ This document will help you leverage
@@ -269,7 +269,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Behave)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Behave)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -292,7 +292,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -304,6 +304,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -262,7 +262,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Capybara)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Capybara)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -285,7 +285,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -298,6 +298,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
4. You can also fill in optional environment details, as per your choice. Then click on the **Run TestCase (and See Results)** button to execute your test case.
-Now if you open your [Automation dashboard](https://automation.lambdatest.com/timeline), you can see your Cerberus test case running as per the chosen Robot Executor details.
+Now if you open your [Automation dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/timeline), you can see your Cerberus test case running as per the chosen Robot Executor details.
Once the test is complete, you can view the result of the test on
@@ -240,7 +240,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Puppeteer&framework=Puppeteer-CodeceptJs)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Puppeteer&framework=Puppeteer-CodeceptJs)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -263,7 +263,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
diff --git a/docs/codecept-with-puppeteer.md b/docs/codecept-with-puppeteer.md
index 65af244c6..6dffe8d4c 100644
--- a/docs/codecept-with-puppeteer.md
+++ b/docs/codecept-with-puppeteer.md
@@ -180,4 +180,4 @@ exports.config = {
npx codeceptjs run
```
-3. Visit the [
diff --git a/docs/create-projects.md b/docs/create-projects.md
index 3cdbd1a60..0a5eecf3d 100644
--- a/docs/create-projects.md
+++ b/docs/create-projects.md
@@ -49,7 +49,7 @@ Creating projects within Test Manager is the foundational step in organizing and
**Steps to Create a Project**
-1. Log in to the Test Manager and navigate to the dashboard - [http://test-manager.lambdatest.com/](http://test-manager.lambdatest.com/)
+1. Log in to the Test Manager and navigate to the dashboard - [http://test-manager.lambdatest.com/](https://www.testmuai.com/login/?redirectTo=http://test-manager.lambdatest.com/)
2. Click on the **Create Project** button.
diff --git a/docs/csharp-with-playwright.md b/docs/csharp-with-playwright.md
index 7c6365c16..0e4aaa1bb 100644
--- a/docs/csharp-with-playwright.md
+++ b/docs/csharp-with-playwright.md
@@ -168,7 +168,7 @@ dotnet run single
## View your test results
---
-Go to the [
@@ -273,7 +273,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Cucumber)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Cucumber)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -296,7 +296,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -310,6 +310,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Cypress&framework=Cypress-v10)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Cypress&framework=Cypress-v10)
**Step 2:** Login with TestMu AI credentials. You will be redirected to HyperExecute dashboard with pop-up confirming to **'Proceed'** to Gitpod editor in the new tab and current tab will show hyperexecute dashboard.
@@ -461,7 +461,7 @@ Follow the below steps to run Cypress Tests on HyperExecute using Gitpod:
**Step 4:** As you are running a sample project, Fetching of the Test Scripts, [HyperExecute YAML](/support/docs/deep-dive-into-hyperexecute-yaml/), [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) and Triggering your tests using the `Execution Command` will be automated.
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
## Additional Details
@@ -512,6 +512,49 @@ pre:
For in detailed information on how to configure it properly, visit [Cypress Detailed Command Logs](/support/docs/cypress-detailed-command-logs/#for-cypress-v10-and-later-versions) documentation.
:::
+
+
+## Using the Cypress Agent Skill with TestMu AI
+***
+
+The [cypress-skill](https://github.com/LambdaTest/agent-skills/tree/main/cypress-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The cypress-skill package includes:
+
+```
+cypress-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Cypress Agent Skill
+***
+
+Install a Cypress Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/cypress-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/cypress-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only cypress-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Cypress&framework=Cypress-v9)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Cypress&framework=Cypress-v9)
**Step 2:** Login with TestMu AI credentials. You will be redirected to HyperExecute dashboard with pop-up confirming to **'Proceed'** to Gitpod editor in the new tab and current tab will show hyperexecute dashboard.
@@ -447,7 +447,7 @@ Follow the below steps to run Cypress Tests on HyperExecute using Gitpod:
**Step 4:** As you are running a sample project, Fetching of the Test Scripts, [HyperExecute YAML](/support/docs/deep-dive-into-hyperexecute-yaml/), [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) and Triggering your tests using the `Execution Command` will be automated.
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
## Additional Details
@@ -498,6 +498,49 @@ pre:
For in detailed information on how to configure it properly, visit [Cypress Detailed Command Logs](/support/docs/cypress-detailed-command-logs/#for-cypress-v9-and-previous-versions) documentation.
:::
+
+
+## Using the Cypress Agent Skill with TestMu AI
+***
+
+The [cypress-skill](https://github.com/LambdaTest/agent-skills/tree/main/cypress-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The cypress-skill package includes:
+
+```
+cypress-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Cypress Agent Skill
+***
+
+Install a Cypress Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/cypress-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/cypress-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only cypress-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
-You can click on **View Test** from the **HyperExecute logs**, which will take you to the [App Automation dashboard](https://appautomation.lambdatest.com/build). There, you can access detailed **device logs**, **crash logs**, and **Metadata** for your test. You’ll also be able to watch a **video recording** of the Test sessions for better **debugging** and **analysis**.
+You can click on **View Test** from the **HyperExecute logs**, which will take you to the [App Automation dashboard](https://www.testmuai.com/login/?redirectTo=https://appautomation.lambdatest.com/build). There, you can access detailed **device logs**, **crash logs**, and **Metadata** for your test. You’ll also be able to watch a **video recording** of the Test sessions for better **debugging** and **analysis**.
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**..default})
diff --git a/docs/espresso-visual-regression.md b/docs/espresso-visual-regression.md
index c5ef19511..21f4da746 100644
--- a/docs/espresso-visual-regression.md
+++ b/docs/espresso-visual-regression.md
@@ -61,7 +61,7 @@ In this documentation, you will learn step-by-step how to perform regression tes
- Your
diff --git a/docs/filter-your-selenium-tests.md b/docs/filter-your-selenium-tests.md
index 5ce3adccf..59d9df27b 100644
--- a/docs/filter-your-selenium-tests.md
+++ b/docs/filter-your-selenium-tests.md
@@ -52,7 +52,7 @@ You can filter your tests on TestMu AI using the various filters available on th
---
Use the filter toolbar on the Timeline tab to narrow down tests by date, user, build, and status.
-When you visit the [Timeline](https://automation.lambdatest.com/timeline) on your automation dashboard, you can see a **Filter** icon that allows you to use different filters.
+When you visit the [Timeline](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/timeline) on your automation dashboard, you can see a **Filter** icon that allows you to use different filters.
@@ -126,7 +126,7 @@ Use this option to clear all applied filters. Clicking this option returns the T
---
Use the filter toolbar on the Automation Logs tab to filter by build, date, users, status, and tags.
-When you visit the [Automation Logs](https://automation.lambdatest.com/logs) on your automation dashboard, you also see a filter toolbar.
+When you visit the [Automation Logs](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/logs) on your automation dashboard, you also see a filter toolbar.
@@ -159,7 +159,7 @@ You can also filter tests based on multiple tags. Select multiple custom tags at
---
Use the filter toolbar on the Analytics tab to filter by tags, users, environment, and date range.
-When you visit the [Analytics](https://automation.lambdatest.com/analytics) on your automation dashboard, you also see a filter toolbar.
+When you visit the [Analytics](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/analytics) on your automation dashboard, you also see a filter toolbar.
diff --git a/docs/gauge-framework.md b/docs/gauge-framework.md
index 44d9cf175..182c7b00c 100644
--- a/docs/gauge-framework.md
+++ b/docs/gauge-framework.md
@@ -226,7 +226,7 @@ To remove a browser from parallel execution, delete its folder or comment out th
Check the Automation Dashboard to see exactly what happened during your test.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to see your test results. Each session includes:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to see your test results. Each session includes:
- **Video recording** of the full test execution
- **Screenshots** captured at each step
diff --git a/docs/geb-framework.md b/docs/geb-framework.md
index 4e5d6d931..2b8f6f454 100644
--- a/docs/geb-framework.md
+++ b/docs/geb-framework.md
@@ -153,7 +153,7 @@ mvn -Dlambdageb.capabilities=capabilities clean test
Check the Automation Dashboard to see exactly what happened during your test.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to see your test results. Each session includes:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to see your test results. Each session includes:
- **Video recording** of the full test execution
- **Screenshots** captured at each step
diff --git a/docs/generate-test-cases.md b/docs/generate-test-cases.md
index dac1a1edf..d73c6dca8 100644
--- a/docs/generate-test-cases.md
+++ b/docs/generate-test-cases.md
@@ -554,6 +554,16 @@ The **Create and Automate** option requires KaneAI access. If you do not have Ka
| Regeneration removed refined scenarios | Regeneration replaces all current output. Use targeted conversational messages instead to preserve specific scenarios. |
+---
+
+## Video Walkthrough
+
+Watch the video below for a quick walkthrough of the AI Test Case Generator in action.
+
+
+
---
## Frequently Asked Questions
diff --git a/docs/getting-started-with-agent-to-agent-testing.md b/docs/getting-started-with-agent-to-agent-testing.md
index 6c0f0772f..7115d8ad1 100644
--- a/docs/getting-started-with-agent-to-agent-testing.md
+++ b/docs/getting-started-with-agent-to-agent-testing.md
@@ -5,7 +5,7 @@ hide_title: false
sidebar_label: Getting Started
description: Validate test chatbots, voice assistants, and hybrid deployments across all interaction types with industry's first Agent Testing Platform.
keywords:
- - agent to agent testing
+ - agent testing
- agentic testing
- ai agent testing
url: https://www.testmuai.com/support/docs/getting-started-with-agent-testing-platform/
diff --git a/docs/getting-started-with-flutter-dart-android-automation.md b/docs/getting-started-with-flutter-dart-android-automation.md
index a4ff68194..b59819a8e 100644
--- a/docs/getting-started-with-flutter-dart-android-automation.md
+++ b/docs/getting-started-with-flutter-dart-android-automation.md
@@ -55,7 +55,7 @@ In this guide, we will explore how to run your first Flutter Dart test on an And
## Prerequisites for Getting Started
1. Flutter SDK installed on your system
-2. You will need a
-You can also view the detailed insights of your test execution on [
@@ -102,7 +102,7 @@ Select one or more build tags in the filter toolbar to narrow down your test bui
To group or filter the tests on your automation dashboard with Build tags:
-Navigate to [TestMu AI Automation Dashboard](https://automation.lambdatest.com/timeline/), and you can see a filter by name **Build Tags** on the right corner of the filter toolbar.
+Navigate to [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/timeline/), and you can see a filter by name **Build Tags** on the right corner of the filter toolbar.
Select the Build tag by which you want to filter your test. For example, if we choose _Tag1_, only the test builds with the tag "Tag1" appear:
diff --git a/docs/group-management.md b/docs/group-management.md
index d4544906e..baa3edf2f 100644
--- a/docs/group-management.md
+++ b/docs/group-management.md
@@ -47,7 +47,7 @@ The
diff --git a/docs/group-tests-using-custom-tags.md b/docs/group-tests-using-custom-tags.md
index 5e8019351..8d8a956f9 100644
--- a/docs/group-tests-using-custom-tags.md
+++ b/docs/group-tests-using-custom-tags.md
@@ -86,7 +86,7 @@ There are multiple ways to view custom tags in the automation dashboard, such as
### How to View Custom Tags on Your Timeline
-Navigate to [Timeline](https://automation.lambdatest.com/timeline/) view of your automation dashboard, and toggle the **Build View** to **Test View**:
+Navigate to [Timeline](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/timeline/) view of your automation dashboard, and toggle the **Build View** to **Test View**:
@@ -96,7 +96,7 @@ You can see the applied custom tags below the tests in this Test View.
+Navigate to [Automation Logs](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/logs) of your automation dashboard, and you can see the applied custom tags below the tests in the left panel.
## How to Filter Tests Using Custom Tags on the Platform
---
@@ -104,7 +104,7 @@ Select one or more custom tags in the filter toolbar to narrow down your test re
You can filter tests on your automation dashboard with these custom tags.
-Navigate to [Automation Logs](https://automation.lambdatest.com/logs) of your automation dashboard, and you can see a filter by name **Tags** in the filter toolbar.
+Navigate to [Automation Logs](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/logs) of your automation dashboard, and you can see a filter by name **Tags** in the filter toolbar.
Click on it and select the Tag by which you want to filter the tests on your dashboard. For example, we have filtered the test using _Tag2_ custom tag:
diff --git a/docs/guide-to-nodejs.md b/docs/guide-to-nodejs.md
index e7c2ba71a..69eabf8c3 100644
--- a/docs/guide-to-nodejs.md
+++ b/docs/guide-to-nodejs.md
@@ -79,7 +79,7 @@ Once you have installed the necessary dependencies, you are all set to run your
## Sample Node.js & Selenium Automation Script
***
-Do make sure to add the **Username** and **Key** in the code below. You can find your username and access key using the key icon on the [Automation dashboard](https://automation.lambdatest.com/) or in your [Profile](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/details/profile) section.
+Do make sure to add the **Username** and **Key** in the code below. You can find your username and access key using the key icon on the [Automation dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/) or in your [Profile](https://www.testmuai.com/login/?redirectTo=https://accounts.lambdatest.com/details/profile) section.
```javascript
/*
diff --git a/docs/hyperexecute-algoqa-integration.md b/docs/hyperexecute-algoqa-integration.md
index f87ffafaa..19363d220 100644
--- a/docs/hyperexecute-algoqa-integration.md
+++ b/docs/hyperexecute-algoqa-integration.md
@@ -198,6 +198,6 @@ OR use this command if you have not exported your username and access key in the
## Step 6: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/hyperexecute-api-testing.md b/docs/hyperexecute-api-testing.md
index 54a34e0ab..b13472099 100644
--- a/docs/hyperexecute-api-testing.md
+++ b/docs/hyperexecute-api-testing.md
@@ -181,7 +181,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor and Validate the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
You can validate the tested API via the pre, post, and scenrios logs in the dashboard.
diff --git a/docs/hyperexecute-appium-testing.md b/docs/hyperexecute-appium-testing.md
index db6a1582c..9e6580e68 100644
--- a/docs/hyperexecute-appium-testing.md
+++ b/docs/hyperexecute-appium-testing.md
@@ -297,12 +297,55 @@ Sample Capabilities for both android and iOS are mentioned below -
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute automation dashboard](https://automation.lambdatest.com/hyperexecute/) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute automation dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/hyperexecute/) for checking the status of the test execution.
The snapshot below shows how to navigate to the respective *testID* for viewing the Selenium logs:
+
+
+## Using the Appium Agent Skill with TestMu AI
+***
+
+The [appium-skill](https://github.com/LambdaTest/agent-skills/tree/main/appium-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The appium-skill package includes:
+
+```
+appium-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Appium Agent Skill
+***
+
+Install a Appium Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/appium-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/appium-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only appium-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
diff --git a/docs/hyperexecute-environment-variable-setup.md b/docs/hyperexecute-environment-variable-setup.md
index 6ad57bc47..e53735c41 100644
--- a/docs/hyperexecute-environment-variable-setup.md
+++ b/docs/hyperexecute-environment-variable-setup.md
@@ -50,7 +50,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
# HyperExecute Environment Variable Setup
***
-To provide you with a secure [cross-browser testing](https://www.testmuai.com) environment on-cloud, we recommend integrating
diff --git a/docs/hyperexecute-generate-sample-yaml.md b/docs/hyperexecute-generate-sample-yaml.md
index 9eb42de21..7c95808ce 100644
--- a/docs/hyperexecute-generate-sample-yaml.md
+++ b/docs/hyperexecute-generate-sample-yaml.md
@@ -42,7 +42,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
>
You can also generate the HyperExecute YAML directly from the HyperExecute Portal. To accomplish this, follow the below mentioned steps:
-**Step 1:** Go to [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute), click on the **Help Center** and select **Generate YAML** from the dropdown.
+**Step 1:** Go to [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute), click on the **Help Center** and select **Generate YAML** from the dropdown.
**Step 2:** Select your preferred test automation framework.
diff --git a/docs/hyperexecute-guided-walkthrough.md b/docs/hyperexecute-guided-walkthrough.md
index c359b7284..8c035877c 100644
--- a/docs/hyperexecute-guided-walkthrough.md
+++ b/docs/hyperexecute-guided-walkthrough.md
@@ -44,7 +44,7 @@ This page gives you a guided walkthrough of all the things on the HyperExecute D
## Jobs Page
-All the tests on HyperExecute get executed as a Job. All the Jobs can be found on our [Jobs page](https://hyperexecute.lambdatest.com/hyperexecute). Each [Job](/support/docs/hyperexecute-status/#1-job-level-status) has a [`Status`](/support/docs/hyperexecute-status/#3-stage-level-status), a unique `Job Number`, a set of [`Labels`](/support/docs/deep-dive-into-hyperexecute-yaml/#joblabel), info on number of [`Tasks`](/support/docs/hyperexecute-status/#2-task-level-status) executed as part of that Job, and a `Summary` section followed by the details of the `Job Duration` and who initiated the Job.
+All the tests on HyperExecute get executed as a Job. All the Jobs can be found on our [Jobs page](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute). Each [Job](/support/docs/hyperexecute-status/#1-job-level-status) has a [`Status`](/support/docs/hyperexecute-status/#3-stage-level-status), a unique `Job Number`, a set of [`Labels`](/support/docs/deep-dive-into-hyperexecute-yaml/#joblabel), info on number of [`Tasks`](/support/docs/hyperexecute-status/#2-task-level-status) executed as part of that Job, and a `Summary` section followed by the details of the `Job Duration` and who initiated the Job.
diff --git a/docs/hyperexecute-integration-with-virtual-devices.md b/docs/hyperexecute-integration-with-virtual-devices.md
index 0fe4de2a8..885b81892 100644
--- a/docs/hyperexecute-integration-with-virtual-devices.md
+++ b/docs/hyperexecute-integration-with-virtual-devices.md
@@ -371,4 +371,4 @@ OR use this command if you have not exported your username and access key in the
diff --git a/docs/hyperexecute-maestro-testing.md b/docs/hyperexecute-maestro-testing.md
index fabbe54a4..57685f594 100644
--- a/docs/hyperexecute-maestro-testing.md
+++ b/docs/hyperexecute-maestro-testing.md
@@ -192,7 +192,7 @@ This ensures that each test result is saved with a unique name like test1.xml, t
## Step 7: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/hyperexecute-projects.md b/docs/hyperexecute-projects.md
index dd53c149f..f6a9b1a44 100644
--- a/docs/hyperexecute-projects.md
+++ b/docs/hyperexecute-projects.md
@@ -47,7 +47,7 @@ When you run jobs on HyperExecute, connecting them to projects helps you track p
### Method 1: Use an Existing Project
If you already have a project in HyperExecute, follow these steps to connect your jobs to it:
-1. Go to [Projects List](https://hyperexecute.lambdatest.com/hyperexecute/projects) tab on HyperExecute Dashboard.
+1. Go to [Projects List](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/projects) tab on HyperExecute Dashboard.
2. Select and open the project you want to link your jobs to.
3. Click the copy icon next to the project name. This copies the project configuration you'll need for your YAML file.
4. Paste the copied details into your YAML file before running your job.
diff --git a/docs/hyperexecute-provar-integration.md b/docs/hyperexecute-provar-integration.md
index a9e655e71..4fd879602 100644
--- a/docs/hyperexecute-provar-integration.md
+++ b/docs/hyperexecute-provar-integration.md
@@ -217,6 +217,6 @@ OR use this command if you have not exported your username and access key in the
## Step 5: Monitor Your Tests
-- Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+- Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/hyperexecute-qtest-integration.md b/docs/hyperexecute-qtest-integration.md
index df9fc3ecd..151370d33 100644
--- a/docs/hyperexecute-qtest-integration.md
+++ b/docs/hyperexecute-qtest-integration.md
@@ -169,6 +169,6 @@ You can download the CLI for your desired platform from the below mentioned link
-- Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+- Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/hyperexecute-reports.md b/docs/hyperexecute-reports.md
index 4cc3bf3cb..2a60baa8f 100644
--- a/docs/hyperexecute-reports.md
+++ b/docs/hyperexecute-reports.md
@@ -66,7 +66,7 @@ partialReports:
```
> **Note**: If you do not specify a framework but you do mention the type of the report, then a report of the default framework is created.
-**Step 3:** Now trigger your job and go to the [HyperExecute](https://hyperexecute.lambdatest.com/hyperexecute/jobs) dashboard.
+**Step 3:** Now trigger your job and go to the [HyperExecute](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs) dashboard.
**Step 4:** Click on the **Open** button of the **Reports**.
diff --git a/docs/hyperexecute-run-jmeter-tests.md b/docs/hyperexecute-run-jmeter-tests.md
index b3ae2ee64..f193c28b0 100644
--- a/docs/hyperexecute-run-jmeter-tests.md
+++ b/docs/hyperexecute-run-jmeter-tests.md
@@ -61,7 +61,7 @@ Download or Clone the code sample for the JMeter Performance Testing from the
@@ -89,7 +89,7 @@ To run your Test Scripts on HyperExecute from you Local system, you'll need the
We will be taking care of everything one by one, just follow the steps given below:
-**Step 1:** Go to the [Quickstart](https://hyperexecute.lambdatest.com/quickstart) page.
+**Step 1:** Go to the [Quickstart](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/quickstart) page.
**Step 2:** Choose your test automation framework, Select **Run on Local System** and click on **Get Started**.
@@ -135,7 +135,7 @@ In case of MAC, if you get a permission denied warning while executing CLI, simp
## 3. Using Gitpod
-**Step 1:** Go to the [Quickstart](https://hyperexecute.lambdatest.com/quickstart) page.
+**Step 1:** Go to the [Quickstart](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/quickstart) page.
**Step 2:** Choose your test automation framework, select **Run test on Gitpod** and click on **Get Started**.
@@ -148,7 +148,7 @@ In case of MAC, if you get a permission denied warning while executing CLI, simp
**Step 4:** As you are running a sample project, Fetching of the Test Scripts, [HyperExecute YAML](/support/docs/deep-dive-into-hyperexecute-yaml/), [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) and Triggering your tests using the `Execution Command` will be automated.
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
## HyperExecute Webinar Video
diff --git a/docs/hyperexecute-scenario-steps-error.md b/docs/hyperexecute-scenario-steps-error.md
index 0b1b7a5f5..20698a5a6 100644
--- a/docs/hyperexecute-scenario-steps-error.md
+++ b/docs/hyperexecute-scenario-steps-error.md
@@ -77,7 +77,7 @@ If you put the wrong HUB Endpoint in your test file, you will receive the follow
-To rectify this issue, you need to cross-check your HUB URL. You can also visit [this](https://automation.lambdatest.com/build) website and click on **Access Key** button to get your correct HUB URL.
+To rectify this issue, you need to cross-check your HUB URL. You can also visit [this](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) website and click on **Access Key** button to get your correct HUB URL.
## Tunnel Error
diff --git a/docs/hyperexecute-sikuli-integration.md b/docs/hyperexecute-sikuli-integration.md
index 103d2fa56..f1e74cdd4 100644
--- a/docs/hyperexecute-sikuli-integration.md
+++ b/docs/hyperexecute-sikuli-integration.md
@@ -174,4 +174,4 @@ OR use this command if you have not exported your username and access key in the
-> Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+> Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/hyperexecute-smart-ui-capture-onboarding.md b/docs/hyperexecute-smart-ui-capture-onboarding.md
index 31a1ec038..131ab66e3 100644
--- a/docs/hyperexecute-smart-ui-capture-onboarding.md
+++ b/docs/hyperexecute-smart-ui-capture-onboarding.md
@@ -86,7 +86,7 @@ This integration is ideal for:
The first step is to create a SmartUI project in the dashboard. This project will contain all your builds and visual comparisons.
-1. Go to [SmartUI Projects page](https://smartui.lambdatest.com/)
+1. Go to [SmartUI Projects page](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/)
2. Click on the **New Project** button
3. Select the platform as **CLI** for executing your capture tests
4. Add the following details:
@@ -521,14 +521,14 @@ npx smartui capture urlTest.json --config config.json --buildName "Release-v1.0"
### HyperExecute Dashboard
-1. Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute)
+1. Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute)
2. Find your job in the job list
3. Click on the job to view detailed execution logs
4. Monitor test progress in real-time
### SmartUI Dashboard
-1. After test execution completes, navigate to [SmartUI Dashboard](https://smartui.lambdatest.com/)
+1. After test execution completes, navigate to [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/)
2. Select your project
3. View the build with your specified build name
4. Review captured screenshots
diff --git a/docs/hyperexecute-smart-ui-sdk-maestro.md b/docs/hyperexecute-smart-ui-sdk-maestro.md
index 6b0baad78..24941796c 100644
--- a/docs/hyperexecute-smart-ui-sdk-maestro.md
+++ b/docs/hyperexecute-smart-ui-sdk-maestro.md
@@ -65,7 +65,7 @@ Before you begin, ensure you have the following prerequisites in place:
First, you need to create a project in SmartUI. All your visual regression test builds for this project will be grouped here.
-1. Navigate to the [SmartUI Projects page](https://smartui.lambdatest.com/).
+1. Navigate to the [SmartUI Projects page](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/).
2. Click on **New Project**.
3. Select **CLI** as the platform.
4. Provide a **Project Name**, select approvers, and add any relevant tags.
@@ -222,7 +222,7 @@ After the HyperExecute job is finished, all screenshots captured using the `take
-1. Navigate to the [SmartUI Dashboard](https://smartui.lambdatest.com/).
+1. Navigate to the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/).
2. Select your project and the most recent build.
3. Here, you can compare screenshots against the baseline, highlight differences, and approve or reject changes. You can use features like Smart Ignore to mask dynamic areas for more stable comparisons.
diff --git a/docs/hyperexecute-smart-ui-sdk-selenium-csharp.md b/docs/hyperexecute-smart-ui-sdk-selenium-csharp.md
index d432b4a86..6ab1cec50 100644
--- a/docs/hyperexecute-smart-ui-sdk-selenium-csharp.md
+++ b/docs/hyperexecute-smart-ui-sdk-selenium-csharp.md
@@ -60,13 +60,13 @@ To run the Tests on HyperExecute from your Local System, you are required:
- [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) in order to initiate a test execution Job .
- Setup the [Environmental Variable](/support/docs/hyperexecute-environment-variable-setup/)
- [HyperExecute YAML](/support/docs/hyperexecute-yaml-version0.2/) file which contains all the necessary instructions.
-- Login to [
diff --git a/docs/hyperexecute-smart-ui-sdk-using-cypress.md b/docs/hyperexecute-smart-ui-sdk-using-cypress.md
index d16c09e0b..d6d63ddfd 100644
--- a/docs/hyperexecute-smart-ui-sdk-using-cypress.md
+++ b/docs/hyperexecute-smart-ui-sdk-using-cypress.md
@@ -61,13 +61,13 @@ To run the Tests on HyperExecute from your Local System, you are required:
- [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) in order to initiate a test execution Job .
- Setup the [Environmental Variable](/support/docs/hyperexecute-environment-variable-setup/)
- [HyperExecute YAML](/support/docs/hyperexecute-yaml-version0.2/) file which contains all the necessary instructions.
-- Login to [
diff --git a/docs/hyperexecute-smart-ui-sdk-using-playwright.md b/docs/hyperexecute-smart-ui-sdk-using-playwright.md
index 48221c419..7cfb403da 100644
--- a/docs/hyperexecute-smart-ui-sdk-using-playwright.md
+++ b/docs/hyperexecute-smart-ui-sdk-using-playwright.md
@@ -58,13 +58,13 @@ To run the Tests on HyperExecute from your Local System, you are required:
- [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) in order to initiate a test execution Job .
- Setup the [Environmental Variable](/support/docs/hyperexecute-environment-variable-setup/)
- [HyperExecute YAML](/support/docs/hyperexecute-yaml-version0.2/) file which contains all the necessary instructions.
-- Login to [
\ No newline at end of file
diff --git a/docs/hyperexecute-smart-ui-sdk-using-puppeteer.md b/docs/hyperexecute-smart-ui-sdk-using-puppeteer.md
index b370f8af1..6ea9a9778 100644
--- a/docs/hyperexecute-smart-ui-sdk-using-puppeteer.md
+++ b/docs/hyperexecute-smart-ui-sdk-using-puppeteer.md
@@ -60,13 +60,13 @@ You must do the following in order to run the tests on HyperExecute from your lo
- Download [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) in order to initiate a test execution Job .
- Set your [Environmental Variables](/support/docs/hyperexecute-environment-variable-setup/)
- [HyperExecute YAML](/support/docs/hyperexecute-yaml-version0.2/) file which contains all the necessary instructions.
-- Use your login credentials to access [
diff --git a/docs/hyperexecute-smart-ui-test-using-playwright.md b/docs/hyperexecute-smart-ui-test-using-playwright.md
index 567f6779b..04f1fa619 100644
--- a/docs/hyperexecute-smart-ui-test-using-playwright.md
+++ b/docs/hyperexecute-smart-ui-test-using-playwright.md
@@ -223,7 +223,7 @@ OR use this command if you have not exported your username and access key in the
## Step 5: Monitor the Test Execution
-- Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status. Click on the **Approved** button.
+- Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status. Click on the **Approved** button.
diff --git a/docs/hyperexecute-smart-ui-testing-using-cypress.md b/docs/hyperexecute-smart-ui-testing-using-cypress.md
index 45ac210a8..d84a193f1 100644
--- a/docs/hyperexecute-smart-ui-testing-using-cypress.md
+++ b/docs/hyperexecute-smart-ui-testing-using-cypress.md
@@ -144,7 +144,7 @@ To execute the project run the below command in your terminal at the root folder
```bash
./hyperexecute --config
diff --git a/docs/hyperexecute-testng-use-cases.md b/docs/hyperexecute-testng-use-cases.md
index 52926431a..6a1013521 100644
--- a/docs/hyperexecute-testng-use-cases.md
+++ b/docs/hyperexecute-testng-use-cases.md
@@ -41,7 +41,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
})
}}
>
-This guide outlines common **Java + TestNG** scenarios for running tests on [HyperExecute](https://hyperexecute.lambdatest.com/hyperexecute/jobs)
+This guide outlines common **Java + TestNG** scenarios for running tests on [HyperExecute](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs)
## Q: How can I ensure my tests operate with the appropriate Java version on HyperExecute?
diff --git a/docs/hyperexecute-webapp-appium-testing.md b/docs/hyperexecute-webapp-appium-testing.md
index 29e6cbd7e..e1ef70df7 100644
--- a/docs/hyperexecute-webapp-appium-testing.md
+++ b/docs/hyperexecute-webapp-appium-testing.md
@@ -403,7 +403,7 @@ Sample Capabilities for both android and iOS web app mentioned below -
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute automation dashboard](https://automation.lambdatest.com/hyperexecute/) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute automation dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/hyperexecute/) for checking the status of the test execution.
The snapshot below shows how to navigate to the respective *testID* for viewing the Selenium logs:
diff --git a/docs/hyperexecute-xcui-testing.md b/docs/hyperexecute-xcui-testing.md
index b346cd178..fa8410ddb 100644
--- a/docs/hyperexecute-xcui-testing.md
+++ b/docs/hyperexecute-xcui-testing.md
@@ -296,6 +296,6 @@ OR use this command if you have not exported your username and access key in the
## Step 7: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/hyperexecute-zephyr-integration.md b/docs/hyperexecute-zephyr-integration.md
index 55f0d3b8c..1de4ad307 100644
--- a/docs/hyperexecute-zephyr-integration.md
+++ b/docs/hyperexecute-zephyr-integration.md
@@ -204,7 +204,7 @@ OR use this command if you have not exported your username and access key in the
## Step 6: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
diff --git a/docs/inside-lambdatest-automation-platform.md b/docs/inside-lambdatest-automation-platform.md
index c5b454f8d..c6b08e096 100644
--- a/docs/inside-lambdatest-automation-platform.md
+++ b/docs/inside-lambdatest-automation-platform.md
@@ -45,7 +45,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
---
-The [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) is where you view results, debug failures, and track every test you run on the grid. This page walks you through each section of the dashboard.
+The [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) is where you view results, debug failures, and track every test you run on the grid. This page walks you through each section of the dashboard.
diff --git a/docs/integrating-your-jenkins-pipeline-with-lambdatest.md b/docs/integrating-your-jenkins-pipeline-with-lambdatest.md
index 6e8617417..b8ec25602 100644
--- a/docs/integrating-your-jenkins-pipeline-with-lambdatest.md
+++ b/docs/integrating-your-jenkins-pipeline-with-lambdatest.md
@@ -59,7 +59,7 @@ Jenkins Pipeline is also referred to as "Pipeline" offers a suite of plugins to
3. Ensure you have the Pipeline plugin, although, it is displayed under the "suggested plugins" during the post-installation setup of Jenkins.
4. **
- After your build is successful, go to the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to monitor the progress of your tests.
+ After your build is successful, go to the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to monitor the progress of your tests.
diff --git a/docs/jest-on-hyperexecute.md b/docs/jest-on-hyperexecute.md
index b900930d4..4ac751836 100644
--- a/docs/jest-on-hyperexecute.md
+++ b/docs/jest-on-hyperexecute.md
@@ -236,7 +236,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -254,7 +254,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Puppeteer&framework=Jest)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Puppeteer&framework=Jest)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -277,7 +277,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -290,6 +290,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -275,7 +275,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=JUnit)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=JUnit)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -298,7 +298,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -312,6 +312,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -72,6 +72,6 @@ Select your Project and the folder where you want to save your test cases. The *
### Step 4: Execute your test
-To execute your test, click on the **HyperExecute** button and you will be redirected to the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute/jobs) where your tests will be executed.
+To execute your test, click on the **HyperExecute** button and you will be redirected to the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs) where your tests will be executed.
diff --git a/docs/kane-ai-drag-drop.md b/docs/kane-ai-drag-drop.md
index 4bffdebdb..0416f1378 100644
--- a/docs/kane-ai-drag-drop.md
+++ b/docs/kane-ai-drag-drop.md
@@ -36,6 +36,23 @@ You can author a drag step in two ways:
- **Natural Language (NL)** — describe the drag in plain English (e.g. `drag "Card A" to "Column B"`).
- **Manual Interaction** — perform the gesture on the device or browser viewport and have it captured as a step.
+## Drag and Drop vs Click and Drag
+
+KaneAI supports two distinct drag interactions. They look similar but behave differently, and they are **not interchangeable**:
+
+- **Drag and Drop** — the element is first **long-pressed** to pick it up, and only then moved to the target. This is the standard gesture for moving items between containers and works on **all platforms**.
+- **Click and Drag** — the element is pressed and moved **immediately, without any long press**. This is how interactions such as sliders, canvas drawing, and element resizing work, and it is available on **Desktop Web only**.
+
+| | Drag and Drop | Click and Drag |
+| --- | --- | --- |
+| **Gesture** | Long press on the element first, then move it to the target | Press and move in one continuous motion — no long press |
+| **Platforms** | Desktop Web, Android App, iOS App, Mobile Web | Desktop Web only |
+| **Typical scenarios** | Kanban cards, list reordering, container-to-container transfer | Sliders, canvas drawing, element resizing, range selection |
+
+:::note
+If a drag step fails on an element that doesn't respond to a long press (for example a slider thumb or a canvas), the element likely expects **Click and Drag** rather than Drag and Drop. Click and Drag has its own constraints — see [Limitations](#limitations).
+:::
+
## Supported Platforms
@@ -190,6 +207,8 @@ Use Manual Interaction to adjust date-range sliders, resize chart panels, and re
- **Cross-context dragging** — drags between iframes or shadow DOMs are not supported.
- **Multi-element dragging** — cannot drag multiple elements simultaneously.
- **Advanced NL** (e.g., `drag X up by 50px`, offset-based reorder) — on the roadmap; currently rejected with a graceful error.
+- **Click and Drag via NL** — not supported as a natural language test step; supported only via Manual Interaction. Desktop Web only.
+- **Click and Drag speed** — executes slowly by design so the dragged element stays in focus during the movement; faster execution could cause the element to lose focus mid-drag.
- **NL slider authoring** — not supported. Use Manual Interaction.
- **NL confirmation gestures** (slide-to-confirm) — not supported. Use Manual Interaction.
- **Drag and drop on canvas-based elements via NL** — canvas elements rely on custom rendering; use Manual Interaction.
@@ -197,6 +216,12 @@ Use Manual Interaction to adjust date-range sliders, resize chart panels, and re
## FAQs
+**What is the difference between Drag and Drop and Click and Drag?**
+Drag and Drop long-presses the element to pick it up before moving it, and works on all platforms. Click and Drag presses and moves the element immediately without a long press, and is available on Desktop Web only. See [Drag and Drop vs Click and Drag](#drag-and-drop-vs-click-and-drag).
+
+**Why is my Click and Drag step slow?**
+This is expected. Click and Drag executes deliberately slowly to keep the dragged element in focus throughout the movement — a faster gesture could cause the element to lose focus mid-drag and fail the step.
+
**Can I author a slider drag with natural language?**
No. Sliders have moving targets that NL cannot resolve reliably. Use Manual Interaction to capture the slider gesture directly. The captured step replays at ≥ 95% success rate across devices.
diff --git a/docs/kane-ai-guided-walkthrough.md b/docs/kane-ai-guided-walkthrough.md
index facad3fc2..b8d6c62c9 100644
--- a/docs/kane-ai-guided-walkthrough.md
+++ b/docs/kane-ai-guided-walkthrough.md
@@ -43,7 +43,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
>
This guided walkthrough will help you understand the various components and features available, ensuring you can efficiently navigate and use the platform for managing your automated tests after you have successfully [run your first test](/support/docs/kane-ai-web-test/).
-> Navigate to the [Test Manager](https://test-manager.lambdatest.com/projects) and [select your project and folder](/support/docs/kane-ai-web-test/#step-3-save-your-test-case) into which you have saved your tests to manage your tests.
+> Navigate to the [Test Manager](https://www.testmuai.com/login/?redirectTo=https://test-manager.lambdatest.com/projects) and [select your project and folder](/support/docs/kane-ai-web-test/#step-3-save-your-test-case) into which you have saved your tests to manage your tests.
## Projects Page
All the Test Cases generated are accessible from the Test Manager page in the Test Cases section. Each of the Test Case has a unique `Test Case ID` and `Labels` to uniquely identify them. The top section displays the project name, number of Test Cases in that particular project folder, Test Plans, Builds and its creation details.
diff --git a/docs/kane-ai-using-variables.md b/docs/kane-ai-using-variables.md
index 1c096f083..409ab0d49 100644
--- a/docs/kane-ai-using-variables.md
+++ b/docs/kane-ai-using-variables.md
@@ -88,7 +88,7 @@ For such _local_ variables, only the scope of the variable can be changed to a g
### Via UI from Variables page
-By visiting the [variables page](https://kaneai.lambdatest.com/variables), you can click on "Create new" option and add relevant details and scope. You can list of all global and environment variables on this page.
+By visiting the [variables page](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/variables), you can click on "Create new" option and add relevant details and scope. You can list of all global and environment variables on this page.
You can edit the session value for the variables here which will lead to updation of the value in all new test executions and sessions for that variable.
### From a Manual Interaction step
diff --git a/docs/kane-ai-web-test.md b/docs/kane-ai-web-test.md
index 0fa94e868..42c5705c6 100644
--- a/docs/kane-ai-web-test.md
+++ b/docs/kane-ai-web-test.md
@@ -46,7 +46,7 @@ In this guide, we'll walk you through the process of generating, and executing a
## Steps to generate the test cases
### Step 1: Create a Web Test
-Navigate to the [KaneAI homepage](https://kaneai.lambdatest.com/objective) and click on the **Create a Web Test** button to initiate the process of generating test cases for your web app. In the right side, a window will open with which you can navigate to your platform to perform the testing.
+Navigate to the [KaneAI homepage](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/objective) and click on the **Create a Web Test** button to initiate the process of generating test cases for your web app. In the right side, a window will open with which you can navigate to your platform to perform the testing.
diff --git a/docs/kane-cli-skills.md b/docs/kane-cli-skills.md
index a09d365e9..9b470f4c3 100644
--- a/docs/kane-cli-skills.md
+++ b/docs/kane-cli-skills.md
@@ -57,6 +57,18 @@ Skills are plain markdown files. Review and customize them by editing the instal
---
+## Install
+
+The quickest way to install the Kane CLI skill globally for all supported agents (Claude Code, Codex CLI, and Gemini CLI) in one command:
+
+```bash
+npx @testmuai/kane-cli-skill
+```
+
+If you prefer to install manually for a specific agent, follow the instructions below.
+
+---
+
## Install by Agent
diff --git a/docs/kaneai-database.md b/docs/kaneai-database.md
index fb20f7538..6a57b0c38 100644
--- a/docs/kaneai-database.md
+++ b/docs/kaneai-database.md
@@ -53,7 +53,7 @@ This document provides a step-by-step process to connect databases within the Ka
## Creating a database connection
-To begin, you need to access the [database connections](https://kaneai.lambdatest.com/databases "database connections") page within KaneAI and initiate the creation of a new connection by clicking on **Create New Connection**.
+To begin, you need to access the [database connections](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/databases "database connections") page within KaneAI and initiate the creation of a new connection by clicking on **Create New Connection**.
diff --git a/docs/kaneai-github-app.md b/docs/kaneai-github-app.md
index c5855c7fb..c8aa4d90c 100644
--- a/docs/kaneai-github-app.md
+++ b/docs/kaneai-github-app.md
@@ -90,7 +90,7 @@ Before implementing the
diff --git a/docs/kaneai-kb-authentication-and-session-management.md b/docs/kaneai-kb-authentication-and-session-management.md
index 80aba0bed..14e8b9f86 100644
--- a/docs/kaneai-kb-authentication-and-session-management.md
+++ b/docs/kaneai-kb-authentication-and-session-management.md
@@ -117,7 +117,7 @@ You can find more information about environment variables in [this guide](/suppo
Store passwords securely using KaneAI Secrets (backed by HashiCorp Vault):
-1. Go to [KaneAI Variables](https://kaneai.lambdatest.com/variables)
+1. Go to [KaneAI Variables](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/variables)
2. Create a secret variable for the password
3. Reference it in your test: `type {{secret.admin_password}} in the password field`
diff --git a/docs/kaneai-kb-mobile-app-testing-patterns.md b/docs/kaneai-kb-mobile-app-testing-patterns.md
index 61c99eef7..126053d44 100644
--- a/docs/kaneai-kb-mobile-app-testing-patterns.md
+++ b/docs/kaneai-kb-mobile-app-testing-patterns.md
@@ -48,7 +48,7 @@ Mobile native app testing in KaneAI follows many of the same principles as web t
## Getting Started with Mobile Tests
-1. Navigate to the [KaneAI home page](https://kaneai.lambdatest.com/objective)
+1. Navigate to the [KaneAI home page](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/objective)
2. Choose **App Test** (Android or iOS)
3. Select a real device from the device cloud
4. Upload your app (APK for Android, IPA for iOS) or select a previously uploaded app
diff --git a/docs/kaneai-scroll-until-mobile.md b/docs/kaneai-scroll-until-mobile.md
index 5b9a52eab..c41459bfc 100644
--- a/docs/kaneai-scroll-until-mobile.md
+++ b/docs/kaneai-scroll-until-mobile.md
@@ -11,6 +11,8 @@ keywords:
- scroll until element
- natural language commands
- mobile scrolling
+ - horizontal scrolling
+ - nested container scrolling
url: https://www.testmuai.com/support/docs/kaneai-scroll-until-mobile/
site_name: TestMu AI
slug: kaneai-scroll-until-mobile/
@@ -95,6 +97,8 @@ Clearly specify what the agent should find and what action to perform once found
| Button Interaction | `Scroll until Submit button and click on it.` |
| Subsection Navigation | `Scroll inside a subsection until date input field and click on it.` |
| Dropdown Selection | `Scroll inside the dropdown until 'New option' and select it.` |
+| Horizontal Scrolling (Mobile App) | `Scroll right inside the carousel until 'Best Sellers' is visible.` |
+| Nested Container (Mobile App) | `Scroll inside the reviews section until 'Load more' button and click on it.` |
---
@@ -106,12 +110,12 @@ Please be aware of the following constraints in the current version.
### Mobile App Authoring
+:::tip Now Supported
+Mobile app authoring now supports **horizontal scrolling** and **scrolling inside nested containers** (element scrolling). You can scroll left or right — for example inside carousels — and scroll within specific container elements such as dropdowns, lists, and subsections instead of only the main viewport.
+:::
+
- **Scroll Limit**:
Maximum of **20 scroll attempts** are performed. If the element is not found, the action fails.
-- **Horizontal Scrolling**:
- ❌ Not supported (only vertical scrolling is available).
-- **Nested Containers**:
- ❌ Scrolling inside specific container elements is not supported; only the main viewport can be scrolled.
- **Directional Extremes**:
❌ Commands such as *“Scroll to top”* or *“Scroll to bottom”* are not supported.
@@ -137,7 +141,7 @@ If you encounter execution issues, refer to the table below:
|------------------------|-----------------|----------|
| Maximum Scroll Limit Reached | Element is beyond 20 scrolls or not present | Verify element visibility and ensure it appears within 20 scrolls |
| Element Not Found | Non-interactable or plain text element (Mobile Browser) | Target a button, link, or input field instead |
-| Scroll Timeout | Element is inside a nested container (App Agent) | Use manual scroll steps if element is not in the main viewport |
+| Scroll Timeout | Element is inside a nested container that was not specified in the command | Name the container in the instruction (e.g., "Scroll inside the reviews section until ...") |
| Command Not Recognized | Usage of IDs, XPaths, or attributes | Rewrite using visible text or element type (e.g., "button") |
---
diff --git a/docs/kaneai-smartui-visual-testing.md b/docs/kaneai-smartui-visual-testing.md
index 9013ecb50..e3ed37947 100644
--- a/docs/kaneai-smartui-visual-testing.md
+++ b/docs/kaneai-smartui-visual-testing.md
@@ -54,7 +54,7 @@ This guide provides a detailed walkthrough on how to leverage KaneAI to create,
## Creating Your First Visual Test
### Initiate a Web Test
-To begin, navigate to the [KaneAI dashboard](https://kaneai.lambdatest.com/objective) and click **Author Browser Test**. You can configure network settings before clicking **Start Testing** to launch the test authoring environment.
+To begin, navigate to the [KaneAI dashboard](https://www.testmuai.com/login/?redirectTo=https://kaneai.lambdatest.com/objective) and click **Author Browser Test**. You can configure network settings before clicking **Start Testing** to launch the test authoring environment.
@@ -146,6 +146,6 @@ After the Test Run job is finished, all screenshots captured using the `/Visual
-1. Navigate to the [SmartUI Dashboard](https://smartui.lambdatest.com/).
+1. Navigate to the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/).
2. Select your project and the most recent build.
3. Here, you can compare screenshots against the baseline, highlight differences, and approve or reject changes. You can use features like Smart Ignore to mask dynamic areas for more stable comparisons.
diff --git a/docs/kaneai-test-run-instance-view.md b/docs/kaneai-test-run-instance-view.md
index dd12120bb..3cfa275ed 100644
--- a/docs/kaneai-test-run-instance-view.md
+++ b/docs/kaneai-test-run-instance-view.md
@@ -13,6 +13,8 @@ keywords:
- root cause analysis
- test debugging
- test manager
+ - auto-heal visibility
+ - share test run
url: https://www.testmuai.com/support/docs/kaneai-test-run-instance-view/
site_name: TestMu AI
slug: kaneai-test-run-instance-view/
@@ -90,6 +92,12 @@ Steps that include sub-actions - such as loops, conditionals, or JavaScript snip
+#### Auto-Heal Visibility
+
+When [Auto-Heal](/support/docs/kaneai-auto-heal/) recovers a step during execution, that step displays an **auto-heal indicator** icon next to its execution duration in the steps panel. This gives you clear, step-level visibility into exactly which steps were healed in a run — without digging through execution logs.
+
+
+
#### Autoplay Steps
Click the **Autoplay Steps** button at the top of the steps panel to automatically walk through each step in sequence. As each step is highlighted, the center panel updates to show the corresponding screenshot captured during execution. This provides a visual replay of the entire test execution without needing to click through each step manually.
@@ -173,6 +181,20 @@ Click the **View tests** button in the top-right corner to open a panel listing
+## Share a Test Run Instance
+
+You can share a test run instance page publicly with stakeholders — including people who do not have a
+
+The share dialog provides the following options:
+
+- **Expiry Duration** - Choose how long the shared link remains accessible (for example, **View: 7 Days**). After the link expires, it can no longer be opened.
+- **Email ID(s)** - Enter one or more email addresses and click **Invite** to send the link directly, with an optional **Message** for context.
+- **Copy Link** - Copy a shareable link to the clipboard and distribute it yourself.
+
+Anyone with an active shared link can view the test run instance — including the steps, screenshots, and execution details — until the link expires.
+
---
## Limitations
diff --git a/docs/karma-integration-with-lambdatest.md b/docs/karma-integration-with-lambdatest.md
index 0a4c45681..ce3665b17 100644
--- a/docs/karma-integration-with-lambdatest.md
+++ b/docs/karma-integration-with-lambdatest.md
@@ -149,7 +149,7 @@ ng test
## Step 5: View Your Results
---
-After running the test, view your results on the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/).
+After running the test, view your results on the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/).
The dashboard provides:
- Video recordings of each test session
diff --git a/docs/katalon-integration.md b/docs/katalon-integration.md
index 5c7a8b4fd..74c62171c 100644
--- a/docs/katalon-integration.md
+++ b/docs/katalon-integration.md
@@ -77,7 +77,7 @@ By the end of this topic, you will know:
Before you can start performing App automation using Katalon Studio with Lambdatest, you would need to follow these steps:
-- You will need a
diff --git a/docs/key-features-of-hyperexecute.md b/docs/key-features-of-hyperexecute.md
index 4784af11f..bb092f22c 100644
--- a/docs/key-features-of-hyperexecute.md
+++ b/docs/key-features-of-hyperexecute.md
@@ -176,7 +176,7 @@ HyperExecute prioritises the safety and security of your data above everything e
## Enterprise
For enterprises that want to keep everything behind their own firewalls, HyperExecute comes with [private cloud facilities](/support/docs/hyperexecute-private-cloud-setup/). You can set up your own cloud runners and storage which ensures that no data leaves your organisation’s firewalls.
-You can use HyperExecute’s [Quickstart feature](https://hyperexecute.lambdatest.com/quickstart) to run your first test, and go through our Concepts page to understand the ins and out of HyperExecute.
+You can use HyperExecute’s [Quickstart feature](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/quickstart) to run your first test, and go through our Concepts page to understand the ins and out of HyperExecute.
[Frequently asked questions](/support/docs/hyperexecute-feature-faqs/) about HyperExecute Features.
diff --git a/docs/lambdatest-running-your-first-selenium-test.md b/docs/lambdatest-running-your-first-selenium-test.md
index ffee5a17e..4d5551d82 100644
--- a/docs/lambdatest-running-your-first-selenium-test.md
+++ b/docs/lambdatest-running-your-first-selenium-test.md
@@ -174,7 +174,7 @@ Execute a single test or run multiple tests in parallel:
Check the Automation Dashboard to see exactly what happened during your test.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to see your test results. Each session includes:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to see your test results. Each session includes:
- **Video recording** of the full test execution
- **Screenshots** captured at each step
diff --git a/docs/laravel-php-framework.md b/docs/laravel-php-framework.md
index 811338241..2a6d47ccf 100644
--- a/docs/laravel-php-framework.md
+++ b/docs/laravel-php-framework.md
@@ -169,7 +169,7 @@ php artisan dusk
---
Check the test output on the console and the TestMu AI dashboard.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
- Text logs for each test step
- Screenshots captured during execution
diff --git a/docs/manual-to-automated-test-conversion.md b/docs/manual-to-automated-test-conversion.md
index 5cf2ebae3..3e92523a9 100644
--- a/docs/manual-to-automated-test-conversion.md
+++ b/docs/manual-to-automated-test-conversion.md
@@ -76,7 +76,7 @@ The conversion flow has four stages:
Start by creating a project in
diff --git a/docs/mocha-on-hyperexecute.md b/docs/mocha-on-hyperexecute.md
index 09a6451fa..74f9a7aca 100644
--- a/docs/mocha-on-hyperexecute.md
+++ b/docs/mocha-on-hyperexecute.md
@@ -234,7 +234,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -252,7 +252,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Puppeteer&framework=Mocha)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Puppeteer&framework=Mocha)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -275,7 +275,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -288,6 +288,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -268,7 +268,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=NightwatchJS)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=NightwatchJS)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -291,7 +291,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -304,6 +304,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -264,7 +264,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=NUnit)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=NUnit)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -287,7 +287,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -300,6 +300,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
diff --git a/docs/perform-selenium-automation-on-headless-browsers.md b/docs/perform-selenium-automation-on-headless-browsers.md
index b6c0638d3..019012d46 100644
--- a/docs/perform-selenium-automation-on-headless-browsers.md
+++ b/docs/perform-selenium-automation-on-headless-browsers.md
@@ -245,7 +245,7 @@ public class HeadlessAutomation {
}
```
-After you execute the above code, the test runs on TestMu AI successfully. View the status of the test on your [Automation dashboard](https://automation.lambdatest.com/timeline).
+After you execute the above code, the test runs on TestMu AI successfully. View the status of the test on your [Automation dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/timeline).
diff --git a/docs/php-framework.md b/docs/php-framework.md
index 491470fd3..878c2a9e0 100644
--- a/docs/php-framework.md
+++ b/docs/php-framework.md
@@ -164,7 +164,7 @@ php tests/LambdaTest.php
---
Check the test output on the console and the TestMu AI dashboard.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
- Text logs for each test step
- Screenshots captured during execution
diff --git a/docs/phpunit-php-framework.md b/docs/phpunit-php-framework.md
index 0585f4da6..d5d78f925 100644
--- a/docs/phpunit-php-framework.md
+++ b/docs/phpunit-php-framework.md
@@ -168,7 +168,7 @@ composer test
---
Check the test output on the console and the TestMu AI dashboard.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
- Text logs for each test step
- Screenshots captured during execution
diff --git a/docs/playwright-accessibility-test.md b/docs/playwright-accessibility-test.md
index b40e82284..e540cc43d 100644
--- a/docs/playwright-accessibility-test.md
+++ b/docs/playwright-accessibility-test.md
@@ -200,7 +200,7 @@ npx playwright test --config=./playwright.config.js
diff --git a/docs/playwright-agent-skills.md b/docs/playwright-agent-skills.md
index ea0552c18..f38226807 100644
--- a/docs/playwright-agent-skills.md
+++ b/docs/playwright-agent-skills.md
@@ -61,7 +61,7 @@ Agent Skills are self-contained packages of instructions, code patterns, debuggi
## Prerequisites
- A
@@ -241,7 +241,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Playwright-CodeceptJs)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Playwright-CodeceptJs)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -264,7 +264,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -277,6 +277,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -254,7 +254,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Playwright-.Net)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Playwright-.Net)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -277,7 +277,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -290,6 +290,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -243,7 +243,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Playwright-Jest)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Playwright-Jest)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -266,7 +266,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -279,6 +279,50 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -260,7 +260,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=JUnit)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=JUnit)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -283,7 +283,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -296,6 +296,50 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
diff --git a/docs/playwright-python-on-hyperexecute.md b/docs/playwright-python-on-hyperexecute.md
index e3b4a7a62..ea6f3bbe7 100644
--- a/docs/playwright-python-on-hyperexecute.md
+++ b/docs/playwright-python-on-hyperexecute.md
@@ -229,7 +229,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -247,7 +247,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Python)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=Python)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -270,7 +270,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -283,6 +283,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -161,3 +161,45 @@ Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexec
HyperExecute also facilitates the provision to download the [Artifacts](/support/docs/hyperexecute-artifacts/) and [Reports](/support/docs/hyperexecute-reports/) on your local machine. Click on the corresponding button to download your generated artifacts and reports.
+
+
+## Using the Playwright Agent Skill with TestMu AI
+***
+
+The [playwright-skill](https://github.com/LambdaTest/agent-skills/tree/main/playwright-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The playwright-skill package includes:
+
+```
+playwright-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Playwright Agent Skill
+***
+
+Install a Playwright Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/playwright-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/playwright-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only playwright-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
diff --git a/docs/playwright-test-runner.md b/docs/playwright-test-runner.md
index 32a180ce5..a40b12f9b 100644
--- a/docs/playwright-test-runner.md
+++ b/docs/playwright-test-runner.md
@@ -16,7 +16,7 @@ keywords:
url: https://www.testmuai.com/support/docs/playwright-test-runner/
site_name: TestMu AI
slug: playwright-test-runner/
-canonical: https://www.testmu.ai/support/docs/playwright-test-runner/
+canonical: https://www.testmuai.com/support/docs/playwright-test-runner/
---
import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
@@ -212,6 +212,49 @@ test.describe('Browse LambdaTest in different search engines', () => {
})
```
+
+
+## Using the Playwright Agent Skill with TestMu AI
+***
+
+The [playwright-skill](https://github.com/LambdaTest/agent-skills/tree/main/playwright-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The playwright-skill package includes:
+
+```
+playwright-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Playwright Agent Skill
+***
+
+Install a Playwright Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/playwright-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/playwright-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only playwright-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
@@ -242,7 +242,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Playwright&framework=Playwright-JS)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Playwright&framework=Playwright-JS)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -265,7 +265,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -278,6 +278,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
diff --git a/docs/playwright-with-cucumberjs.md b/docs/playwright-with-cucumberjs.md
index d520cb9c0..ade856fbf 100644
--- a/docs/playwright-with-cucumberjs.md
+++ b/docs/playwright-with-cucumberjs.md
@@ -16,7 +16,7 @@ keywords:
url: https://www.testmuai.com/support/docs/playwright-with-cucumberjs/
site_name: TestMu AI
slug: playwright-with-cucumberjs/
-canonical: https://www.testmu.ai/support/docs/playwright-with-cucumberjs/
+canonical: https://www.testmuai.com/support/docs/playwright-with-cucumberjs/
---
import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
@@ -210,6 +210,50 @@ try {
4. After that, you can run your test.
+
+
+
+## Using the Cucumber Agent Skill with TestMu AI
+***
+
+The [cucumber-skill](https://github.com/LambdaTest/agent-skills/tree/main/cucumber-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The cucumber-skill package includes:
+
+```
+cucumber-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Cucumber Agent Skill
+***
+
+Install a Cucumber Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/cucumber-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/cucumber-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only cucumber-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
@@ -258,7 +258,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&framework=Protractor)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&framework=Protractor)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -281,7 +281,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -294,6 +294,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -266,7 +266,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=PyTest)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=PyTest)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -289,7 +289,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -302,6 +302,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -248,7 +248,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=PyTest)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=PlayWright&framework=PyTest)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -271,7 +271,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -284,6 +284,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
@@ -269,7 +269,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=PyUnit)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=PyUnit)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -292,7 +292,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
diff --git a/docs/real-time-upload-and-download-files.md b/docs/real-time-upload-and-download-files.md
index 2a306b3b8..0816eb865 100644
--- a/docs/real-time-upload-and-download-files.md
+++ b/docs/real-time-upload-and-download-files.md
@@ -63,7 +63,7 @@ The Upload and Download Files feature allows you to manage files directly within
diff --git a/docs/reqnroll-on-hyperexecute-grid.md b/docs/reqnroll-on-hyperexecute-grid.md
index 7ee945227..c6e0772c5 100644
--- a/docs/reqnroll-on-hyperexecute-grid.md
+++ b/docs/reqnroll-on-hyperexecute-grid.md
@@ -238,9 +238,9 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
diff --git a/docs/reqnroll-with-selenium.md b/docs/reqnroll-with-selenium.md
index 443b0e3f4..930b460c1 100644
--- a/docs/reqnroll-with-selenium.md
+++ b/docs/reqnroll-with-selenium.md
@@ -166,7 +166,7 @@ make reqnroll-automation-test
---
Check the test output on the console and the TestMu AI dashboard.
-Navigate to the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/) to check the status of the test execution.
+Navigate to the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/) to check the status of the test execution.
diff --git a/docs/rkvalidate-integration.md b/docs/rkvalidate-integration.md
index 9bba2d924..7a7b1be64 100644
--- a/docs/rkvalidate-integration.md
+++ b/docs/rkvalidate-integration.md
@@ -75,7 +75,7 @@ rkresults
1. Build your app with the RKTracer tool embedded.
2. Login to your
diff --git a/docs/robot-on-hyperexecute-grid.md b/docs/robot-on-hyperexecute-grid.md
index 7a49710ad..1a7d08f33 100644
--- a/docs/robot-on-hyperexecute-grid.md
+++ b/docs/robot-on-hyperexecute-grid.md
@@ -21,7 +21,7 @@ keywords:
url: https://www.testmuai.com/support/docs/robot-on-hyperexecute-grid/
site_name: TestMu AI
slug: robot-on-hyperexecute-grid/
-canonical: https://www.testmu.ai/support/docs/robot-on-hyperexecute-grid/
+canonical: https://www.testmuai.com/support/docs/robot-on-hyperexecute-grid/
---
import CodeBlock from '@theme/CodeBlock';
@@ -242,7 +242,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -260,7 +260,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Robot)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=Robot)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -283,7 +283,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -296,6 +296,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
Happy testing!
+
+
+## Using the Robot Framework Agent Skill with TestMu AI
+***
+
+The [robot-framework-skill](https://github.com/LambdaTest/agent-skills/tree/main/robot-framework-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The robot-framework-skill package includes:
+
+```
+robot-framework-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Robot Framework Agent Skill
+***
+
+Install a Robot Framework Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/robot-framework-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/robot-framework-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only robot-framework-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
@@ -248,7 +248,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=RSpec)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=RSpec)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -271,7 +271,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
diff --git a/docs/ruby-rspec.md b/docs/ruby-rspec.md
index 06abdeb09..9002a8004 100644
--- a/docs/ruby-rspec.md
+++ b/docs/ruby-rspec.md
@@ -149,7 +149,7 @@ bundle exec rake parallel
---
Check the test output on the console and the TestMu AI dashboard.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
- Text logs for each test step
- Screenshots captured during execution
diff --git a/docs/ruby-testunit.md b/docs/ruby-testunit.md
index fe04adbc5..c99e6f46c 100644
--- a/docs/ruby-testunit.md
+++ b/docs/ruby-testunit.md
@@ -153,7 +153,7 @@ ruby LambdaTest.rb
---
Check the test output on the console and the TestMu AI dashboard.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
- Text logs for each test step
- Screenshots captured during execution
diff --git a/docs/ruby.md b/docs/ruby.md
index 2768b28fc..f9b658477 100644
--- a/docs/ruby.md
+++ b/docs/ruby.md
@@ -159,7 +159,7 @@ ruby todo-click-test.rb
---
Check the test output on the console and the TestMu AI dashboard.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to view your test results. The dashboard provides:
- Text logs for each test step
- Screenshots captured during execution
diff --git a/docs/run-automation-tests-using-angularjs-with-karma.md b/docs/run-automation-tests-using-angularjs-with-karma.md
index fdeca5c00..1e208d8c4 100644
--- a/docs/run-automation-tests-using-angularjs-with-karma.md
+++ b/docs/run-automation-tests-using-angularjs-with-karma.md
@@ -159,7 +159,7 @@ ng test
## Step 5: View Your Results
---
-After running the test, view your results on the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build).
+After running the test, view your results on the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build).
The dashboard provides:
- Video recordings of each test session
diff --git a/docs/run-nightwatch-tests-on-lambdatest-selenium-grid.md b/docs/run-nightwatch-tests-on-lambdatest-selenium-grid.md
index 2715ab548..80b3bc447 100644
--- a/docs/run-nightwatch-tests-on-lambdatest-selenium-grid.md
+++ b/docs/run-nightwatch-tests-on-lambdatest-selenium-grid.md
@@ -134,7 +134,7 @@ npm run parallel
## Step 5: View Your Results
---
-After running the test, view your results on the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build).
+After running the test, view your results on the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build).
diff --git a/docs/run-parallel-tests-with-selenium.md b/docs/run-parallel-tests-with-selenium.md
index e49c8e42a..744d17d6b 100644
--- a/docs/run-parallel-tests-with-selenium.md
+++ b/docs/run-parallel-tests-with-selenium.md
@@ -252,14 +252,14 @@ Follow these guidelines to get the most out of parallel execution.
- **Keep tests independent.** Parallel tests must not share state, test data, or depend on execution order. Each test should set up and tear down its own data.
- **Always call `driver.quit()`.** If a test exits without quitting, the session stays open until the idle timeout expires, wasting concurrency slots.
- **Use unique build and test names.** Set the `build` and `name` capabilities to identify which parallel thread ran which test on the dashboard.
-- **Start small.** Begin with 2-3 parallel threads and increase gradually. Monitor the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) for failures caused by test interference.
+- **Start small.** Begin with 2-3 parallel threads and increase gradually. Monitor the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for failures caused by test interference.
## Verify Your Parallel Runs
---
Check the dashboard to confirm tests ran simultaneously.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) and open your build. If tests ran in parallel, you will see multiple sessions with overlapping start times. The build duration should be roughly equal to the duration of the longest individual test, not the sum of all tests.
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) and open your build. If tests ran in parallel, you will see multiple sessions with overlapping start times. The build duration should be roughly equal to the duration of the longest individual test, not the sum of all tests.
diff --git a/docs/run-selenium-ide-tests-on-lambdatest-selenium-cloud-grid.md b/docs/run-selenium-ide-tests-on-lambdatest-selenium-cloud-grid.md
index 07b4b1f88..23d77b0de 100644
--- a/docs/run-selenium-ide-tests-on-lambdatest-selenium-cloud-grid.md
+++ b/docs/run-selenium-ide-tests-on-lambdatest-selenium-cloud-grid.md
@@ -72,7 +72,7 @@ In this document, we will see how to run Selenium IDE tests on
@@ -141,7 +141,7 @@ selenium-side-runner -w 4 "LambdaTest-IDE.side" --server https://user-name:acces
```
-We have successfully executed all the steps to run Selenium IDE tests on
diff --git a/docs/run-wd-atomation-test-on-lambdatest-selenium-grid.md b/docs/run-wd-atomation-test-on-lambdatest-selenium-grid.md
index 8db00febe..a6288f7bc 100644
--- a/docs/run-wd-atomation-test-on-lambdatest-selenium-grid.md
+++ b/docs/run-wd-atomation-test-on-lambdatest-selenium-grid.md
@@ -149,7 +149,7 @@ npm run parallel
## Step 5: View Your Results
---
-After running the test, view your results on the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build).
+After running the test, view your results on the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build).
The dashboard provides:
- Video recordings of each test session
diff --git a/docs/run-webdriverio-automation-scripts-on-lambdatest.md b/docs/run-webdriverio-automation-scripts-on-lambdatest.md
index f1547350d..c10b61c71 100644
--- a/docs/run-webdriverio-automation-scripts-on-lambdatest.md
+++ b/docs/run-webdriverio-automation-scripts-on-lambdatest.md
@@ -184,7 +184,7 @@ npm run parallel
## Step 5: View Your Results
---
-After running the test, view your results on the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build).
+After running the test, view your results on the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build).
The dashboard provides:
- Video recordings of each test session
diff --git a/docs/run-your-cypress-tests-in-parallel.md b/docs/run-your-cypress-tests-in-parallel.md
index 0f86f12c9..3bf3b5c71 100644
--- a/docs/run-your-cypress-tests-in-parallel.md
+++ b/docs/run-your-cypress-tests-in-parallel.md
@@ -19,7 +19,7 @@ keywords:
url: https://www.testmuai.com/support/docs/run-your-cypress-tests-in-parallel/
site_name: TestMu AI
slug: run-your-cypress-tests-in-parallel/
-canonical: https://www.testmu.ai/support/docs/run-your-cypress-tests-in-parallel/
+canonical: https://www.testmuai.com/support/docs/run-your-cypress-tests-in-parallel/
---
# Run Your Cypress Tests In Parallel
---
@@ -83,6 +83,49 @@ The number of parallel test running on the
diff --git a/docs/selenide-framework.md b/docs/selenide-framework.md
index 541514b09..7c5c38d9e 100644
--- a/docs/selenide-framework.md
+++ b/docs/selenide-framework.md
@@ -356,7 +356,7 @@ For parallel execution, the sample project includes a `parallel.testng.xml` that
Check the Automation Dashboard to see exactly what happened during your test.
-Visit the [TestMu AI Automation Dashboard](https://automation.lambdatest.com/build) to see your test results. Each session includes:
+Visit the [TestMu AI Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) to see your test results. Each session includes:
- **Video recording** of the full test execution
- **Screenshots** captured at each step
diff --git a/docs/selenified-integration-with-lambdatest.md b/docs/selenified-integration-with-lambdatest.md
index 5a041ad55..7771b465d 100644
--- a/docs/selenified-integration-with-lambdatest.md
+++ b/docs/selenified-integration-with-lambdatest.md
@@ -71,7 +71,7 @@ You can also run your Selenified test automation scripts on
diff --git a/docs/semaphore-integration-with-hyperexecute.md b/docs/semaphore-integration-with-hyperexecute.md
index df5cd8b21..69441d55a 100644
--- a/docs/semaphore-integration-with-hyperexecute.md
+++ b/docs/semaphore-integration-with-hyperexecute.md
@@ -95,7 +95,7 @@ Click on **Run the workflow** button.
-- Output in the [HyperExecute](https://hyperexecute.lambdatest.com/hyperexecute/jobs) Dashboard
+- Output in the [HyperExecute](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs) Dashboard
diff --git a/docs/sharding-espresso.md b/docs/sharding-espresso.md
index 024d61c22..280b6546b 100644
--- a/docs/sharding-espresso.md
+++ b/docs/sharding-espresso.md
@@ -310,9 +310,9 @@ You can refer to this example and screenshot below:
5. After the test is started you can follow the test on the below links.
-- [
-- [
:::note
diff --git a/docs/sharding-xcui.md b/docs/sharding-xcui.md
index 748165eab..91fbcd97a 100644
--- a/docs/sharding-xcui.md
+++ b/docs/sharding-xcui.md
@@ -166,7 +166,7 @@ Response of above cURL will be a **JSON** object containing the `App URL` of the
1. Firstly, create a folder on your local.
2. Download the HyperExecute CLI file and put it under this folder. You may download HyperExecute CLI from either of the following ways:
- Download it from our HyperExecute documentation page [here](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/), or
-- "Get Started" through HyperExecute [onboarding](https://hyperexecute.lambdatest.com/quickstart) and download the CLI.
+- "Get Started" through HyperExecute [onboarding](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/quickstart) and download the CLI.
3. Refer to the sample `.ipa` files and `.yaml` file given below. Put all of them under this folder.
- [ProverbialTest.ipa](https://prod-mobile-artefacts.lambdatest.com/assets/docs/ProverbialTest.ipa)
- [LambdaUiKitIOS.ipa](https://prod-mobile-artefacts.lambdatest.com/assets/docs/LambdaUiKitIOS.ipa)
@@ -252,9 +252,9 @@ You can refer to this example and screenshot below:
5. After the test is started you can follow the test on the below links.
-- [
-- [
:::note
diff --git a/docs/siesta-integration.md b/docs/siesta-integration.md
index deda86a2d..320f4e56c 100644
--- a/docs/siesta-integration.md
+++ b/docs/siesta-integration.md
@@ -55,7 +55,7 @@ Siesta is a JavaScript and UI testing tool for web pages and Node.js processes.
2. Download Siesta from official Bryntum website.
-3. In order to run your Siesta tests, you will need to set your
diff --git a/docs/simplifyqa-integration.md b/docs/simplifyqa-integration.md
index e0d20e6c9..55cdbb4e0 100644
--- a/docs/simplifyqa-integration.md
+++ b/docs/simplifyqa-integration.md
@@ -81,4 +81,4 @@ This document will guide you step-by-step method to integrate the SimplifyQA wit
- Click on test data and paste the App ID copied from Lambda Test in **APP Id** parameter.
- In the Execute Tab, choose **Cloud Automation**. Click on
+
+
diff --git a/docs/smartui-running-your-first-project.md b/docs/smartui-running-your-first-project.md
index 2445b4303..935942880 100644
--- a/docs/smartui-running-your-first-project.md
+++ b/docs/smartui-running-your-first-project.md
@@ -18,7 +18,7 @@ keywords:
url: https://www.testmuai.com/support/docs/smartui-running-your-first-project/
site_name: TestMu AI
slug: smartui-running-your-first-project/
-canonical: https://www.testmu.ai/support/docs/smartui-running-your-first-project/
+canonical: https://www.testmuai.com/support/docs/smartui-running-your-first-project/
---
import Tabs from '@theme/Tabs';
@@ -57,14 +57,14 @@ This guide will walk you through the process of running your first visual regres
## Prerequisites
- Basic understanding of Command Line Interface and Selenium is required.
-- Login to [
diff --git a/docs/smartui-with-bitbucket.md b/docs/smartui-with-bitbucket.md
index 960120407..a16f672bc 100644
--- a/docs/smartui-with-bitbucket.md
+++ b/docs/smartui-with-bitbucket.md
@@ -85,7 +85,7 @@ You can also store your *LT_USERNAME*, *LT_ACCESS_KEY* and *PROJECT_TOKEN* as se
### Step 3: Check the output
-- After triggering the workflow, check your results in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+- After triggering the workflow, check your results in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
diff --git a/docs/smartui-with-buildkite.md b/docs/smartui-with-buildkite.md
index 900c8a6a1..b0121648b 100644
--- a/docs/smartui-with-buildkite.md
+++ b/docs/smartui-with-buildkite.md
@@ -99,7 +99,7 @@ steps:
### Step 5: Check the output
-- After triggering the workflow, check your results in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+- After triggering the workflow, check your results in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
diff --git a/docs/smartui-with-circle-ci.md b/docs/smartui-with-circle-ci.md
index eaf794653..c4ac05efe 100644
--- a/docs/smartui-with-circle-ci.md
+++ b/docs/smartui-with-circle-ci.md
@@ -107,7 +107,7 @@ workflows:
### Step 5: Check the output
-- After triggering the workflow, check your results in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+- After triggering the workflow, check your results in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
diff --git a/docs/smartui-with-github-actions.md b/docs/smartui-with-github-actions.md
index 5ceb81c0a..6b41edb59 100644
--- a/docs/smartui-with-github-actions.md
+++ b/docs/smartui-with-github-actions.md
@@ -83,7 +83,7 @@ To run the new pipeline that you just created, click the **Run workflow** button
-> Check your output in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+> Check your output in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
## Best Practices
diff --git a/docs/smartui-with-gitlab.md b/docs/smartui-with-gitlab.md
index 694e01962..c1e8c2e64 100644
--- a/docs/smartui-with-gitlab.md
+++ b/docs/smartui-with-gitlab.md
@@ -85,7 +85,7 @@ You can also store your *LT_USERNAME*, *LT_ACCESS_KEY* and *PROJECT_TOKEN* as se
### Step 3: Check the output
-- After triggering the workflow, check your results in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+- After triggering the workflow, check your results in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
diff --git a/docs/smartui-with-netlify.md b/docs/smartui-with-netlify.md
index fd042378d..a3ac60eff 100644
--- a/docs/smartui-with-netlify.md
+++ b/docs/smartui-with-netlify.md
@@ -215,7 +215,7 @@ Your changes will be triggered and deployed.
**Solutions**:
1. Verify project exists in SmartUI dashboard:
- - Log into [SmartUI Dashboard](https://smartui.lambdatest.com/)
+ - Log into [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/)
- Check if project with specified name exists
- Create project if it doesn't exist
diff --git a/docs/smartui-with-semaphore.md b/docs/smartui-with-semaphore.md
index a9a7e1a56..d3ec68974 100644
--- a/docs/smartui-with-semaphore.md
+++ b/docs/smartui-with-semaphore.md
@@ -78,7 +78,7 @@ You can also store your *LT_USERNAME*, *LT_ACCESS_KEY* and *PROJECT_TOKEN* as se
### Step 3: Check the output
-- After triggering the workflow, check your results in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+- After triggering the workflow, check your results in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
diff --git a/docs/smartui-with-travis-ci.md b/docs/smartui-with-travis-ci.md
index 33ae3c7e0..4837335ed 100644
--- a/docs/smartui-with-travis-ci.md
+++ b/docs/smartui-with-travis-ci.md
@@ -98,7 +98,7 @@ script:
### Step 5: Check the output
-- After triggering the workflow, check your results in the [SmartUI Dashboard](https://smartui.lambdatest.com/projects)
+- After triggering the workflow, check your results in the [SmartUI Dashboard](https://www.testmuai.com/login/?redirectTo=https://smartui.lambdatest.com/projects)
diff --git a/docs/specflow-on-hyperexecute-grid.md b/docs/specflow-on-hyperexecute-grid.md
index 1c3c4fa25..ef57c557c 100644
--- a/docs/specflow-on-hyperexecute-grid.md
+++ b/docs/specflow-on-hyperexecute-grid.md
@@ -21,7 +21,7 @@ keywords:
url: https://www.testmuai.com/support/docs/specflow-on-hyperexecute-grid/
site_name: TestMu AI
slug: specflow-on-hyperexecute-grid/
-canonical: https://www.testmu.ai/support/docs/specflow-on-hyperexecute-grid/
+canonical: https://www.testmuai.com/support/docs/specflow-on-hyperexecute-grid/
---
import CodeBlock from '@theme/CodeBlock';
@@ -256,7 +256,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -274,7 +274,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=SpecFlow)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=SpecFlow)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -297,7 +297,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -310,6 +310,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
Happy testing!
+
+
+## Using the SpecFlow Agent Skill with TestMu AI
+***
+
+The [specflow-skill](https://github.com/LambdaTest/agent-skills/tree/main/specflow-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The specflow-skill package includes:
+
+```
+specflow-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing SpecFlow Agent Skill
+***
+
+Install a SpecFlow Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/specflow-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/specflow-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only specflow-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
-
-
diff --git a/docs/test-intelligence-ftd.md b/docs/test-intelligence-ftd.md
index d74dc9b6f..cb576cf46 100644
--- a/docs/test-intelligence-ftd.md
+++ b/docs/test-intelligence-ftd.md
@@ -124,7 +124,7 @@ Currently, these features only support `Selenium` based tests for Web Automation
To view the Flaky Test Detection report, you can follow the below steps:
-- Go to the [
in the test list.
- Now, select the test for which you want to view the flaky test details.
diff --git a/docs/testcomplete-integration.md b/docs/testcomplete-integration.md
index 0cee465f4..5ae7294c4 100644
--- a/docs/testcomplete-integration.md
+++ b/docs/testcomplete-integration.md
@@ -73,7 +73,7 @@ TestComplete, from SmartBear, streamlines automated testing across desktop, web,
-2. Visit [
@@ -173,7 +173,7 @@ Click on the run button to check your script.
-Your test results would be displayed on on the [**
diff --git a/docs/testing-flutter-apps.md b/docs/testing-flutter-apps.md
index 2022e5ecb..3749a1ae8 100644
--- a/docs/testing-flutter-apps.md
+++ b/docs/testing-flutter-apps.md
@@ -13,7 +13,7 @@ keywords:
url: https://www.testmuai.com/support/docs/testing-flutter-apps/
site_name: TestMu AI
slug: testing-flutter-apps/
-canonical: https://www.testmu.ai/support/docs/testing-flutter-apps/
+canonical: https://www.testmuai.com/support/docs/testing-flutter-apps/
---
import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
@@ -216,6 +216,49 @@ Below is a screenshot showing Appium test automation running with the Flutter In
>In case you have any questions or need any additional information, you could reach out at our window.openLTChatWidget()}>**24X7 Chat Support** or mail us directly at support@testmuai.com.
+
+
+## Using the Flutter Testing Agent Skill with TestMu AI
+***
+
+The [flutter-testing-skill](https://github.com/LambdaTest/agent-skills/tree/main/flutter-testing-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The flutter-testing-skill package includes:
+
+```
+flutter-testing-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing Flutter Testing Agent Skill
+***
+
+Install a Flutter Testing Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/flutter-testing-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/flutter-testing-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only flutter-testing-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
-🎉 Congratulations! You've successfully triggered the TestNG tests on HyperExecute. Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+🎉 Congratulations! You've successfully triggered the TestNG tests on HyperExecute. Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -227,7 +227,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -245,7 +245,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=TestNG)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=TestNG)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -268,7 +268,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -280,6 +280,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
> For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
+
+
+## Using the TestNG Agent Skill with TestMu AI
+***
+
+The [testng-skill](https://github.com/LambdaTest/agent-skills/tree/main/testng-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The testng-skill package includes:
+
+```
+testng-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing TestNG Agent Skill
+***
+
+Install a TestNG Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/testng-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/testng-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only testng-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
-3. Click the *Enable
diff --git a/docs/testsigma-integration.md b/docs/testsigma-integration.md
index d442ee757..86e57038f 100644
--- a/docs/testsigma-integration.md
+++ b/docs/testsigma-integration.md
@@ -87,7 +87,7 @@ Now that you have integrated
diff --git a/docs/tosca-integration-with-hyperexecute-for-sap.md b/docs/tosca-integration-with-hyperexecute-for-sap.md
index 2c1a75617..1aeeaa136 100644
--- a/docs/tosca-integration-with-hyperexecute-for-sap.md
+++ b/docs/tosca-integration-with-hyperexecute-for-sap.md
@@ -58,7 +58,7 @@ To Integrate Tosca with HyperExecute, follow the below mentioned steps:
### Step 1: Initialize the Tosca Project
-- Go to the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/). Click on the **Projects**.
+- Go to the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/). Click on the **Projects**.
- Click on the **Setup a New Project** button.
@@ -92,7 +92,7 @@ To Integrate Tosca with HyperExecute, follow the below mentioned steps:
### Step 4: Check the Logs Status in Dashboard
-- Now go to the [**Jobs**](https://hyperexecute.lambdatest.com/hyperexecute/jobs) section and check the results.
+- Now go to the [**Jobs**](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs) section and check the results.
-> Results will get updated in the **Common Repository** once execution is completed on HyperExecute. The live video of running tests can be viewed from the [HyperExecute job-detail](https://hyperexecute.lambdatest.com/hyperexecute/jobs)dashboard.
+> Results will get updated in the **Common Repository** once execution is completed on HyperExecute. The live video of running tests can be viewed from the [HyperExecute job-detail](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs)dashboard.
diff --git a/docs/tosca-integration-with-hyperexecute-using-commander.md b/docs/tosca-integration-with-hyperexecute-using-commander.md
index c42c5b9d3..9abd06d94 100644
--- a/docs/tosca-integration-with-hyperexecute-using-commander.md
+++ b/docs/tosca-integration-with-hyperexecute-using-commander.md
@@ -56,7 +56,7 @@ This documentation provides a detailed guide on seamlessly integrating Tosca wit
To Integrate Tosca with HyperExecute, follow the below mentioned steps:
-**Step 1:** Go to the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/). Click on the **Projects**.
+**Step 1:** Go to the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/). Click on the **Projects**.
**Step 2:** Click on the **Setup a New Project** button.
@@ -82,10 +82,10 @@ Enter the **Workspace Details**, i.e., Username (mandatory) and Password (option
**Step 7:** Now set the total number of **Concurrent Sessions** that you want to run on HyperExecute and click on the **Run** button.
-**Step 8:** Now go to the [**Jobs**](https://hyperexecute.lambdatest.com/hyperexecute/jobs) section and check the results.
+**Step 8:** Now go to the [**Jobs**](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs) section and check the results.
-> Results will get updated in the **Common Repository** once execution is completed on HyperExecute. The live video of running tests can be viewed from the [HyperExecute job-detail](https://hyperexecute.lambdatest.com/hyperexecute/jobs)dashboard.
+> Results will get updated in the **Common Repository** once execution is completed on HyperExecute. The live video of running tests can be viewed from the [HyperExecute job-detail](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs)dashboard.
***
## Integrate Tosca with HyperExecute using YAML
@@ -94,7 +94,7 @@ To Integrate Tosca with HyperExecute using YAML, follow the below mentioned step
#### Prerequisite
-- Ensure that you have integrated Tosca with [
-Monitor and analyze your test result on the [
diff --git a/docs/travis-ci-with-lambdatest.md b/docs/travis-ci-with-lambdatest.md
index a99a08904..e4da46437 100644
--- a/docs/travis-ci-with-lambdatest.md
+++ b/docs/travis-ci-with-lambdatest.md
@@ -71,7 +71,7 @@ npm install npm@latest -g
**2.
diff --git a/docs/vividus-integration.md b/docs/vividus-integration.md
index c37ef40bb..bf81db0a4 100644
--- a/docs/vividus-integration.md
+++ b/docs/vividus-integration.md
@@ -76,7 +76,7 @@ selenium.grid.password=
diff --git a/docs/webdriverio-on-hyperexecute-grid.md b/docs/webdriverio-on-hyperexecute-grid.md
index 87431e6ab..a1a579070 100644
--- a/docs/webdriverio-on-hyperexecute-grid.md
+++ b/docs/webdriverio-on-hyperexecute-grid.md
@@ -22,7 +22,7 @@ keywords:
url: https://www.testmuai.com/support/docs/webdriverio-on-hyperexecute-grid/
site_name: TestMu AI
slug: webdriverio-on-hyperexecute-grid/
-canonical: https://www.testmu.ai/support/docs/webdriverio-on-hyperexecute-grid/
+canonical: https://www.testmuai.com/support/docs/webdriverio-on-hyperexecute-grid/
---
import CodeBlock from '@theme/CodeBlock';
@@ -245,7 +245,7 @@ OR use this command if you have not exported your username and access key in the
### Step 5: Monitor the Test Execution
-Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+Visit the [HyperExecute Dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
@@ -263,7 +263,7 @@ Follow the below steps to run Test using Gitpod:
**Step 1:** Click '**Open in Gitpod**' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=WebdriverIO)
+[
](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=WebdriverIO)
**Step 2:** Login with
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://www.testmuai.com/login/?redirectTo=https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
:::tip
@@ -286,7 +286,7 @@ You can also implement [Secret Keys](/support/docs/hyperexecute-how-to-save-and-
## Navigation in Automation Dashboard
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://www.testmuai.com/login/?redirectTo=https://automation.lambdatest.com/build) for checking the status of the test execution.
You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
@@ -300,6 +300,49 @@ The snapshot below shows the videos, logs and other meta data for that specific
For any query or doubt, please feel free to contact us via window.openLTChatWidget()}>**24×7 chat support** or you can also drop a mail to **support@testmuai.com**.
Happy testing!
+
+
+## Using the WebdriverIO Agent Skill with TestMu AI
+***
+
+The [webdriverio-skill](https://github.com/LambdaTest/agent-skills/tree/main/webdriverio-skill) is a part of [TestMu AI Skills](https://github.com/LambdaTest/agent-skills/) that guide AI coding assistants in generating production-ready test automation.
+
+The webdriverio-skill package includes:
+
+```
+webdriverio-skill/
+├── SKILL.md
+└── reference/
+ ├── playbook.md
+ └── advanced-patterns.md
+```
+
+It provides structured guidance for:
+
+* Project structure and setup
+* Dependency configuration
+* Local execution
+* TestMu AI cloud execution
+* Debugging patterns
+* CI/CD integration
+
+
+### Installing WebdriverIO Agent Skill
+***
+
+Install a WebdriverIO Agent Skill using the command below:
+
+```
+# Clone the repo and copy the skill you need
+git clone https://github.com/LambdaTest/agent-skills.git
+cp -r agent-skills/webdriverio-skill .claude/skills/
+
+# Or for Cursor / Copilot
+cp -r agent-skills/webdriverio-skill .cursor/skills/
+```
+
+**Note**: If you prefer installing all available framework skills instead of only webdriverio-skill, clone the repository directly into your tool's skills directory (for example, .claude/skills/, .cursor/skills/, .gemini/skills/, or .agent/skills/).
+
diff --git a/sidebars.js b/sidebars.js
index 30343c515..238701ed5 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -3181,6 +3181,7 @@ module.exports = {
"audio-injection",
"regular-expression-appium",
"appium-upload-media",
+ "appium-upload-contacts",
"network-configurations",
"app-auto-network-throttling",
"sim-support",
@@ -3648,6 +3649,11 @@ module.exports = {
collapsed: true,
label: "Core Features",
items: [
+ {
+ type: "doc",
+ label: "SmartUI in Automation Dashboard",
+ id: "smartui-automation-dashboard",
+ },
{
type: "doc",
label: "Baseline Management",
@@ -3852,6 +3858,11 @@ module.exports = {
label: "Handle Sticky Elements",
id: "smartui-handle-sticky-elements",
},
+ {
+ type: "doc",
+ label: "CustomScroll Screenshots",
+ id: "smartui-customscroll",
+ },
],
},
diff --git a/static/img/support/Integration-dark-icon.svg b/static/img/support/Integration-dark-icon.svg
new file mode 100644
index 000000000..c4404a000
--- /dev/null
+++ b/static/img/support/Integration-dark-icon.svg
@@ -0,0 +1,10 @@
+
diff --git a/static/img/support/Integration-light-icon.svg b/static/img/support/Integration-light-icon.svg
new file mode 100644
index 000000000..3b6a36419
--- /dev/null
+++ b/static/img/support/Integration-light-icon.svg
@@ -0,0 +1,10 @@
+
diff --git a/static/img/support/Realtime-dark-icon.svg b/static/img/support/Realtime-dark-icon.svg
new file mode 100644
index 000000000..6afe2e5a5
--- /dev/null
+++ b/static/img/support/Realtime-dark-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/Realtime-light-icon.svg b/static/img/support/Realtime-light-icon.svg
new file mode 100644
index 000000000..bf126ed57
--- /dev/null
+++ b/static/img/support/Realtime-light-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/accessibility-dark.svg b/static/img/support/accessibility-dark.svg
new file mode 100644
index 000000000..b2b9840ec
--- /dev/null
+++ b/static/img/support/accessibility-dark.svg
@@ -0,0 +1,13 @@
+
diff --git a/static/img/support/accessibility-light.svg b/static/img/support/accessibility-light.svg
new file mode 100644
index 000000000..53ca84a68
--- /dev/null
+++ b/static/img/support/accessibility-light.svg
@@ -0,0 +1,13 @@
+
diff --git a/static/img/support/analytics-dark-icon.svg b/static/img/support/analytics-dark-icon.svg
new file mode 100644
index 000000000..f8e2227dc
--- /dev/null
+++ b/static/img/support/analytics-dark-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/analytics-light-icon.svg b/static/img/support/analytics-light-icon.svg
new file mode 100644
index 000000000..b8625fb51
--- /dev/null
+++ b/static/img/support/analytics-light-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/appAutomation-dark-icon.svg b/static/img/support/appAutomation-dark-icon.svg
new file mode 100644
index 000000000..c9ef92071
--- /dev/null
+++ b/static/img/support/appAutomation-dark-icon.svg
@@ -0,0 +1,5 @@
+
diff --git a/static/img/support/appAutomation-light-icon.svg b/static/img/support/appAutomation-light-icon.svg
new file mode 100644
index 000000000..603da58c9
--- /dev/null
+++ b/static/img/support/appAutomation-light-icon.svg
@@ -0,0 +1,5 @@
+
diff --git a/static/img/support/automation-dark-icon.svg b/static/img/support/automation-dark-icon.svg
new file mode 100644
index 000000000..eef72597e
--- /dev/null
+++ b/static/img/support/automation-dark-icon.svg
@@ -0,0 +1,5 @@
+
diff --git a/static/img/support/automation-light-icon.svg b/static/img/support/automation-light-icon.svg
new file mode 100644
index 000000000..ebb7915a3
--- /dev/null
+++ b/static/img/support/automation-light-icon.svg
@@ -0,0 +1,5 @@
+
diff --git a/static/img/support/home_dark.png b/static/img/support/home_dark.png
new file mode 100644
index 000000000..bbaeb4586
Binary files /dev/null and b/static/img/support/home_dark.png differ
diff --git a/static/img/support/home_light.png b/static/img/support/home_light.png
new file mode 100644
index 000000000..c6fa7ab42
Binary files /dev/null and b/static/img/support/home_light.png differ
diff --git a/static/img/support/hyp-dark-icon.svg b/static/img/support/hyp-dark-icon.svg
new file mode 100644
index 000000000..54523a988
--- /dev/null
+++ b/static/img/support/hyp-dark-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/hyp-light-icon.svg b/static/img/support/hyp-light-icon.svg
new file mode 100644
index 000000000..bfa6f2e64
--- /dev/null
+++ b/static/img/support/hyp-light-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/other-dark-icon.svg b/static/img/support/other-dark-icon.svg
new file mode 100644
index 000000000..86b718847
--- /dev/null
+++ b/static/img/support/other-dark-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/other-light-icon.svg b/static/img/support/other-light-icon.svg
new file mode 100644
index 000000000..85cbc5d74
--- /dev/null
+++ b/static/img/support/other-light-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/realDevice-dark.svg b/static/img/support/realDevice-dark.svg
new file mode 100644
index 000000000..9320b9b96
--- /dev/null
+++ b/static/img/support/realDevice-dark.svg
@@ -0,0 +1,10 @@
+
diff --git a/static/img/support/realDevice-light.svg b/static/img/support/realDevice-light.svg
new file mode 100644
index 000000000..598cf7324
--- /dev/null
+++ b/static/img/support/realDevice-light.svg
@@ -0,0 +1,10 @@
+
diff --git a/static/img/support/settings-dark-icon.svg b/static/img/support/settings-dark-icon.svg
new file mode 100644
index 000000000..314923781
--- /dev/null
+++ b/static/img/support/settings-dark-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/settings-light-icon.svg b/static/img/support/settings-light-icon.svg
new file mode 100644
index 000000000..ebb17a9b0
--- /dev/null
+++ b/static/img/support/settings-light-icon.svg
@@ -0,0 +1,4 @@
+
diff --git a/static/img/support/testManager-dark.svg b/static/img/support/testManager-dark.svg
new file mode 100644
index 000000000..276805bf4
--- /dev/null
+++ b/static/img/support/testManager-dark.svg
@@ -0,0 +1,10 @@
+
diff --git a/static/img/support/testManager-light.svg b/static/img/support/testManager-light.svg
new file mode 100644
index 000000000..8b7277fe2
--- /dev/null
+++ b/static/img/support/testManager-light.svg
@@ -0,0 +1,10 @@
+
diff --git a/static/img/support/testing-locally-dark-icon.svg b/static/img/support/testing-locally-dark-icon.svg
new file mode 100644
index 000000000..7a75bb30b
--- /dev/null
+++ b/static/img/support/testing-locally-dark-icon.svg
@@ -0,0 +1,8 @@
+
diff --git a/static/img/support/testing-locally-light-icon.svg b/static/img/support/testing-locally-light-icon.svg
new file mode 100644
index 000000000..7ace09cde
--- /dev/null
+++ b/static/img/support/testing-locally-light-icon.svg
@@ -0,0 +1,8 @@
+
diff --git a/static/img/support/visual-dark-icon.svg b/static/img/support/visual-dark-icon.svg
new file mode 100644
index 000000000..4a207e345
--- /dev/null
+++ b/static/img/support/visual-dark-icon.svg
@@ -0,0 +1,6 @@
+
diff --git a/static/img/support/visual-light-icon.svg b/static/img/support/visual-light-icon.svg
new file mode 100644
index 000000000..81cfbe9fb
--- /dev/null
+++ b/static/img/support/visual-light-icon.svg
@@ -0,0 +1,6 @@
+
diff --git a/static/img/support/webscanner-dark-icon.svg b/static/img/support/webscanner-dark-icon.svg
new file mode 100644
index 000000000..cf93ffadc
--- /dev/null
+++ b/static/img/support/webscanner-dark-icon.svg
@@ -0,0 +1,7 @@
+
\ No newline at end of file
diff --git a/static/img/support/webscanner-light-icon.svg b/static/img/support/webscanner-light-icon.svg
new file mode 100644
index 000000000..cf93ffadc
--- /dev/null
+++ b/static/img/support/webscanner-light-icon.svg
@@ -0,0 +1,7 @@
+
\ No newline at end of file
diff --git a/static/img/testmuai-logo-dark.svg b/static/img/testmuai-logo-dark.svg
new file mode 100644
index 000000000..57e7ec5c5
--- /dev/null
+++ b/static/img/testmuai-logo-dark.svg
@@ -0,0 +1,44 @@
+
diff --git a/static/img/testmuai-logo-light.svg b/static/img/testmuai-logo-light.svg
new file mode 100644
index 000000000..9d927814e
--- /dev/null
+++ b/static/img/testmuai-logo-light.svg
@@ -0,0 +1,44 @@
+