diff --git a/src/pages/docs/FAQs/web-apps/automating-captcha.md b/src/pages/docs/FAQs/web-apps/automating-captcha.md index a5205e49..d8b1e52a 100644 --- a/src/pages/docs/FAQs/web-apps/automating-captcha.md +++ b/src/pages/docs/FAQs/web-apps/automating-captcha.md @@ -10,10 +10,10 @@ contextual_links: name: "Contents" - type: link name: "1. Why is CAPTCHA used?" - url: "#1-why-is-captcha-used?" + url: "#1-why-is-captcha-used" - type: link name: "2. Can I automate CAPTCHA testing in my test environment?" - url: "#2-can-i-automate-captcha-testing-in-my-test-environment?" + url: "#2-can-i-automate-captcha-testing-in-my-test-environment" --- --- diff --git a/src/pages/docs/FAQs/web-apps/why-chrome-extension.md b/src/pages/docs/FAQs/web-apps/why-chrome-extension.md index 4f0b8a34..fe6991dd 100644 --- a/src/pages/docs/FAQs/web-apps/why-chrome-extension.md +++ b/src/pages/docs/FAQs/web-apps/why-chrome-extension.md @@ -28,7 +28,7 @@ With Testsigma’s Chrome Extension you capture these elements and record the us
--- -##**Security Disclaimer** +## **Security Disclaimer** * Testsigma Chrome Extension doesn’t track user browsing outside the application and does not collect private information such as IP address and passwords. * We don’t modify the source code of your application. diff --git a/src/pages/docs/agent/setup-on-kubernetes.md b/src/pages/docs/agent/setup-on-kubernetes.md index bd359b9c..ab45fb98 100644 --- a/src/pages/docs/agent/setup-on-kubernetes.md +++ b/src/pages/docs/agent/setup-on-kubernetes.md @@ -438,6 +438,6 @@ kubectl -n testsigma delete pvc data-ts-agent-testsigma-agent-0 | Pod rejected on creation | The namespace enforces the `restricted` Pod Security Standard. The agent image requires `baseline`. | | Browser crashes mid test | The browser needs more shared memory. Raise `browsers.chrome.shmSize` and its memory limit together. | -For issues with agent startup or registration itself, see [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/setup-issues/). +For issues with agent startup or registration itself, see [Agent - Startup and Registration Errors](https://testsigma.com/docs/agent/troubleshooting/how-to-fix-setup-issues/). --- diff --git a/src/pages/docs/agent/troubleshooting/how-to-fix-setup-issues.md b/src/pages/docs/agent/troubleshooting/how-to-fix-setup-issues.md index 8e89e6c0..3b9c17f2 100644 --- a/src/pages/docs/agent/troubleshooting/how-to-fix-setup-issues.md +++ b/src/pages/docs/agent/troubleshooting/how-to-fix-setup-issues.md @@ -177,7 +177,7 @@ Follow the below steps to fix the issue. 2. Restart the Agent. 3. If the Agent is not updated, update the Agent. *For more information, refer to the [documentation on updating Agents](https://testsigma.com/docs/agent/update-agent-manually/)*. -If the above troubleshooting steps does not resolve the issue, contact Testsigma support at [support@testsigma.com](mailto:support@testsigma.com) with the Agent logs files. *For more information on how to fetch agent logs refer to the [documentation on torubleshooting agent logs](https://testsigma.com/docs/agent/troubleshooting/logs/)*. +If the above troubleshooting steps does not resolve the issue, contact Testsigma support at [support@testsigma.com](mailto:support@testsigma.com) with the Agent logs files. *For more information on how to fetch agent logs refer to the [documentation on troubleshooting agent logs](https://testsigma.com/docs/agent/troubleshooting/how-to-configure-agent-logs/)*. --- diff --git a/src/pages/docs/agent/update-drivers-manually.md b/src/pages/docs/agent/update-drivers-manually.md index 1c3f1870..076f3094 100644 --- a/src/pages/docs/agent/update-drivers-manually.md +++ b/src/pages/docs/agent/update-drivers-manually.md @@ -19,7 +19,7 @@ contextual_links: url: "#adding-drivers-manually" - type: link name: "Additional steps for Mac or Linux" - url: "#additional-steps-for-maclinux" + url: "#additional-steps-for-mac-or-linux" --- diff --git a/src/pages/docs/api/examples/trigger-test-plan-wait-completion.md b/src/pages/docs/api/examples/trigger-test-plan-wait-completion.md index b7d880bb..1cb2d1dd 100644 --- a/src/pages/docs/api/examples/trigger-test-plan-wait-completion.md +++ b/src/pages/docs/api/examples/trigger-test-plan-wait-completion.md @@ -30,7 +30,7 @@ You should already be familiar with creating and running Test Plans. Refer to th | You need to authenticate these requests with your Testsigma API Key. To know more about obtaining API Keys, refer to the [documentation on generating API keys](https://testsigma.com/docs/configuration/api-keys/) --- -##**Checking the Test Run Results** +## **Checking the Test Run Results** The below steps give an overview of how the script given at the bottom of this page works: @@ -53,7 +53,7 @@ We can poll the Test Plan Execution Results API with this Run ID at regular inte We have provided the Powershell and Bash scripts for the same below. Please feel free to make changes as required and plug the same into your CI Pipeline. --- -##**Powershell script** +## **Powershell script** The Script triggers the executions and also waits until the Timeout(MAX\_WAIT\_TIME\_FOR\_SCRIPT\_TO\_EXIT) for the execution to complete. @@ -182,7 +182,7 @@ saveFinalResponseToAFile --- -##**Bash Script** +## **Bash Script** ```shell #!/bin/bash diff --git a/src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md b/src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md index 4645ef69..2313056b 100644 --- a/src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md +++ b/src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md @@ -14,7 +14,7 @@ contextual_links: url: "#prerequisites" - type: link name: "Steps to Get OpenAI Details" - url: "#Steps-to-get-openai-details" + url: "#steps-to-get-openai-details" --- --- diff --git a/src/pages/docs/atto/generative-ai/generate-tests/automate-test-cases.md b/src/pages/docs/atto/generative-ai/generate-tests/automate-test-cases.md index 0bc6267c..ddcf19ca 100644 --- a/src/pages/docs/atto/generative-ai/generate-tests/automate-test-cases.md +++ b/src/pages/docs/atto/generative-ai/generate-tests/automate-test-cases.md @@ -99,6 +99,6 @@ When you generate automated test cases, Atto checks for existing test cases. If [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/). -| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). +| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). --- diff --git a/src/pages/docs/atto/generative-ai/generate-tests/desktop.md b/src/pages/docs/atto/generative-ai/generate-tests/desktop.md index b238b352..fa4ecd97 100644 --- a/src/pages/docs/atto/generative-ai/generate-tests/desktop.md +++ b/src/pages/docs/atto/generative-ai/generate-tests/desktop.md @@ -82,6 +82,6 @@ Testsigma’s Gen AI capabilities help you streamline test case creation for Des [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/). -| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). +| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). --- diff --git a/src/pages/docs/atto/generative-ai/generate-tests/mobile-web.md b/src/pages/docs/atto/generative-ai/generate-tests/mobile-web.md index 627088a8..5db4703c 100644 --- a/src/pages/docs/atto/generative-ai/generate-tests/mobile-web.md +++ b/src/pages/docs/atto/generative-ai/generate-tests/mobile-web.md @@ -101,7 +101,7 @@ You can generate test cases for mobile web applications using Testsigma’s Gene [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/). -| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). +| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). --- \ No newline at end of file diff --git a/src/pages/docs/atto/generative-ai/generate-tests/mobile.md b/src/pages/docs/atto/generative-ai/generate-tests/mobile.md index 46a537f6..7c4a3ec8 100644 --- a/src/pages/docs/atto/generative-ai/generate-tests/mobile.md +++ b/src/pages/docs/atto/generative-ai/generate-tests/mobile.md @@ -98,7 +98,7 @@ You can generate test cases for android and iOS applications using Testsigma’s [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/). -| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). +| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent in Testsigma](https://testsigma.com/docs/ai-agents/generator/). diff --git a/src/pages/docs/atto/generative-ai/generate-tests/salesforce.md b/src/pages/docs/atto/generative-ai/generate-tests/salesforce.md index 8386d483..305c007f 100644 --- a/src/pages/docs/atto/generative-ai/generate-tests/salesforce.md +++ b/src/pages/docs/atto/generative-ai/generate-tests/salesforce.md @@ -76,6 +76,6 @@ You can quickly generate test cases for Salesforce requirements in Testsigma usi [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/). -| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). +| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). --- \ No newline at end of file diff --git a/src/pages/docs/atto/generative-ai/generate-tests/web.md b/src/pages/docs/atto/generative-ai/generate-tests/web.md index 62c150d9..6ad1aafa 100644 --- a/src/pages/docs/atto/generative-ai/generate-tests/web.md +++ b/src/pages/docs/atto/generative-ai/generate-tests/web.md @@ -101,6 +101,6 @@ You can generate test cases for web and mobile web applications using Testsigma [[info | **NOTE**:]] | - To learn about **Agentic Learning**, please refer to the [documentation on Generator Agent](https://testsigma.com/docs/ai-agents/generator/). -| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](http://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). +| - To understand the difference between **Run with Copilot** and **Agentic Learning**, please refer to the [documentation on Run with Copilot vs Agentic Learning](https://testsigma.com/docs/atto/generative-ai/copilot/agentic-learning-vs-copilot/). --- \ No newline at end of file diff --git a/src/pages/docs/atto/generative-ai/overview.md b/src/pages/docs/atto/generative-ai/overview.md index a6870605..305c95d9 100644 --- a/src/pages/docs/atto/generative-ai/overview.md +++ b/src/pages/docs/atto/generative-ai/overview.md @@ -14,7 +14,7 @@ contextual_links: url: "#prerequisites" - type: link name: "Testsigma Copiot Capabilities" - url: "#testsigma-copiot-capabilities" + url: "#testsigma-copilot-capabilities" - type: link name: "Generate Tests from Generative AI" url: "#generate-tests-from-generative-ai" diff --git a/src/pages/docs/continuous-integration/github-cicd.md b/src/pages/docs/continuous-integration/github-cicd.md index 1448fd19..a5d76a7b 100644 --- a/src/pages/docs/continuous-integration/github-cicd.md +++ b/src/pages/docs/continuous-integration/github-cicd.md @@ -9,7 +9,7 @@ contextual_links: name: "Contents" - type: link name: "Pre-requisites:" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "For Github CICD Integration" url: "#for-github-cicd-integration" diff --git a/src/pages/docs/continuous-integration/gitlab-cicd.md b/src/pages/docs/continuous-integration/gitlab-cicd.md index f231a673..e0fc92dc 100644 --- a/src/pages/docs/continuous-integration/gitlab-cicd.md +++ b/src/pages/docs/continuous-integration/gitlab-cicd.md @@ -10,10 +10,10 @@ contextual_links: name: "Contents" - type: link name: "Pre-requisites:" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "Steps to integrate GitLab with Testsigma" - url: "#steps-to-integrate-gitLab-with-testsigma" + url: "#steps-to-integrate-gitlab-with-testsigma" --- diff --git a/src/pages/docs/continuous-integration/jenkins.md b/src/pages/docs/continuous-integration/jenkins.md index 9bb799e1..913d3a24 100644 --- a/src/pages/docs/continuous-integration/jenkins.md +++ b/src/pages/docs/continuous-integration/jenkins.md @@ -37,7 +37,7 @@ Jenkins is an open-source automation server used for CI/CD and build automation. > Before you begin, ensure that you have: > - Reviewed the following documentation: > 1. [Generating API keys](https://testsigma.com/docs/configuration/api-keys/). -> 2. [Getting a test plan ID](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/get-test-plan-id.png). +> 2. [Getting a test plan ID](https://testsigma.com/docs/continuous-integration/get-test-plan-details/). > - A working **Jenkins** server with administrative access. --- diff --git a/src/pages/docs/continuous-integration/shell-script.md b/src/pages/docs/continuous-integration/shell-script.md index 39962a54..c3e93fe3 100644 --- a/src/pages/docs/continuous-integration/shell-script.md +++ b/src/pages/docs/continuous-integration/shell-script.md @@ -10,7 +10,7 @@ contextual_links: name: "Contents" - type: link name: "Pre-requisites:" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "For Powershell Script" url: "#for-powershell-script" diff --git a/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md b/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md index e446ffb8..d760df31 100644 --- a/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md +++ b/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md @@ -11,7 +11,7 @@ contextual_links: name: "Contents" - type: link name: "Pre-Requisite" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "Pre-Requisite Software and Service Installation" url: "#pre-requisite-software-and-service-installation" diff --git a/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md b/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md index 420151f5..5f7df674 100644 --- a/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md +++ b/src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md @@ -11,7 +11,7 @@ contextual_links: name: "Contents" - type: link name: "Pre-Requisite" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "Pre-Requisite Software and Service Installation" url: "#pre-requisite-software-and-service-installation" diff --git a/src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md b/src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md index 2fea664c..2ef7e68a 100644 --- a/src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md +++ b/src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md @@ -36,7 +36,7 @@ contextual_links:
-## **Pre-Requisite Software and Service Installation**
+## **Pre-Requisite Software and Service Installation** **OPEN JDK 11 or greater**
Open JDK 11 can be installed from Oracle. Please make sure JDK 11 or above is taken into consideration as there are a few unsupported libraries below JDK 11 while setting up the dev environment. diff --git a/src/pages/docs/contributing/setup-dev-environment-addons.md b/src/pages/docs/contributing/setup-dev-environment-addons.md index bdc347ea..df7a2f19 100644 --- a/src/pages/docs/contributing/setup-dev-environment-addons.md +++ b/src/pages/docs/contributing/setup-dev-environment-addons.md @@ -14,7 +14,7 @@ contextual_links: url: "#prerequisites" - type: link name: "Setup Instructions" - url: "#setup-instruction" + url: "#setup-instructions" - type: link name: "Contributors" url: "#contributors" diff --git a/src/pages/docs/desired-capabilities/biometric-authentication.md b/src/pages/docs/desired-capabilities/biometric-authentication.md index 61fe5bde..d5656d69 100644 --- a/src/pages/docs/desired-capabilities/biometric-authentication.md +++ b/src/pages/docs/desired-capabilities/biometric-authentication.md @@ -15,7 +15,7 @@ contextual_links: url: "#prerequisites" - type: link name: "How to Add Biometric Authentication Desired Capability?" - url: "#how-to-add-biometric-authentication-desired-capability?" + url: "#how-to-add-biometric-authentication-desired-capability" - type: link name: Using Biometric Authentication Desired Capability" url: "#using-biometric-authentication-desired-capability" diff --git a/src/pages/docs/desired-capabilities/emulate-mobile-devices-with-chrome.md b/src/pages/docs/desired-capabilities/emulate-mobile-devices-with-chrome.md index 109b2fed..b9b54be4 100644 --- a/src/pages/docs/desired-capabilities/emulate-mobile-devices-with-chrome.md +++ b/src/pages/docs/desired-capabilities/emulate-mobile-devices-with-chrome.md @@ -25,7 +25,7 @@ contextual_links: Chrome Browser provides a built-in feature to emulate mobile device screen resolutions. This can be useful for testing the responsiveness of your website on mobile devices, without the time and effort required to set up a full mobile automation system. You can test for mobile even without a dedicated device. --- -##**Obtaining the device name** +## **Obtaining the device name** 1.Open the Browser Developer Console by pressing the F12 key or Ctrl+Shift+I (For Mac, Command+Shift+I). You can also right-click on any web page and select ‘Inspect’ from the menu to open the ‘Developer Console - Elements’ Tab. @@ -49,7 +49,7 @@ You can use the name of any of the above-given default devices while automating This is possible by specifying the device name in the Desired Capabilities while defining a Test Environment as shown in the next section. --- -##**Using available Devices for emulation** +## **Using available Devices for emulation** You should already know how to add Desired Capabilities to your Tests. Refer to the [documentation on managing desired capabilities](https://testsigma.com/docs/desired-capabilities/overview/). @@ -64,7 +64,7 @@ On execution, it will display as mobile device view as shown here: ![Chrome Dev tools Default device Mobile view](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/chrome-dev-tools-default-device-mobile-view.png) --- -##**Advanced: Using a Custom Device for emulation** +## **Advanced: Using a Custom Device for emulation** You can use a custom Device Resolution by providing the width, height, pixelRatio and userAgent values. diff --git a/src/pages/docs/desired-capabilities/enable-browser-console-logs.md b/src/pages/docs/desired-capabilities/enable-browser-console-logs.md index ab5b07f0..86ad7f56 100644 --- a/src/pages/docs/desired-capabilities/enable-browser-console-logs.md +++ b/src/pages/docs/desired-capabilities/enable-browser-console-logs.md @@ -15,7 +15,7 @@ contextual_links: url: "#desired-capabilities-for-console-logs" - type: link name: "Enable Console Log in Ad-hoc Run" - url: "#enable-console-log-in-ad-hoc-run" + url: "#enable-console-log-in-ad-hoc-runs" - type: link name: "Enable Console Log in Test Plan" url: "#enable-console-log-in-test-plan" diff --git a/src/pages/docs/desired-capabilities/set-geo-location.md b/src/pages/docs/desired-capabilities/set-geo-location.md index 15ca0a3b..0e3e2b54 100644 --- a/src/pages/docs/desired-capabilities/set-geo-location.md +++ b/src/pages/docs/desired-capabilities/set-geo-location.md @@ -25,7 +25,7 @@ For setting the location of the Test Environment where the Tests are run, we jus You should already know how to add Desired Capabilities to your Tests. Refer to the [documentation on configuring desired capabilities](https://testsigma.com/docs/desired-capabilities/overview/) --- -##**Setting Desired Capabilities in different Browsers** +## **Setting Desired Capabilities in different Browsers** ### **Google Chrome** @@ -60,7 +60,7 @@ Similarly, the value for the location **'Central Park, NYC, USA'** will be **{"l | Setting the Geolocation is not yet supported in IE and Safari --- -##**Example websites to test current location** +## **Example websites to test current location** You can use https://www.mapcoordinates.net/en for the latitude and longitude information for your desired location, and https://mycurrentlocation.net/ to check current location. diff --git a/src/pages/docs/elements/web-apps/supported-locator-types.md b/src/pages/docs/elements/web-apps/supported-locator-types.md index d85c41fe..195932fd 100644 --- a/src/pages/docs/elements/web-apps/supported-locator-types.md +++ b/src/pages/docs/elements/web-apps/supported-locator-types.md @@ -28,7 +28,7 @@ contextual_links: url: "#5-name" - type: link name: "Class Name" - url: "#6class-name" + url: "#6-class-name" - type: link name: "Tag Name" url: "#7-tag-name" diff --git a/src/pages/docs/projects/requirements.md b/src/pages/docs/projects/requirements.md index 18b015cf..8b87483a 100644 --- a/src/pages/docs/projects/requirements.md +++ b/src/pages/docs/projects/requirements.md @@ -11,7 +11,7 @@ contextual_links: name: "Contents" - type: link name: "Pre-requisites" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "Create a Requirement" url: "#create-a-requirement" diff --git a/src/pages/docs/runs/run-on-cloud-vendor-platforms.md b/src/pages/docs/runs/run-on-cloud-vendor-platforms.md index 75e22eb3..7f58413c 100644 --- a/src/pages/docs/runs/run-on-cloud-vendor-platforms.md +++ b/src/pages/docs/runs/run-on-cloud-vendor-platforms.md @@ -10,7 +10,7 @@ contextual_links: name: "Contents" - type: link name: "Pre-requisites" - url: "#pre-requisites" + url: "#prerequisites" - type: link name: "How to run test cases and test plans on cloud vendor platforms with Testsigma" url: "#how-to-run-test-cases-and-test-plans-on-cloud-vendor-platforms-with-testsigma" diff --git a/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md index b82f6a7e..d2b4ead9 100644 --- a/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md +++ b/src/pages/docs/test-cases/create-test-steps/actions-and-options-manual/step-options.md @@ -11,7 +11,7 @@ contextual_links: name: "Contents" - type: link name: "Prerequesties" - url: "#prerequesties" + url: "#prerequisites" - type: link name: "Clear Step" url: "#clear-step" diff --git a/src/pages/docs/test-data/data-generators/numberfunctions-function-type.md b/src/pages/docs/test-data/data-generators/numberfunctions-function-type.md index acc3d155..4e9c97e1 100644 --- a/src/pages/docs/test-data/data-generators/numberfunctions-function-type.md +++ b/src/pages/docs/test-data/data-generators/numberfunctions-function-type.md @@ -17,7 +17,7 @@ contextual_links: url: "#selecting-numberfunctions-as-a-function-type-for-data-generator" - type: link name: "Custom Calculation" - url: "#custom-calculations" + url: "#custom-calculation" --- --- diff --git a/src/pages/docs/test-data/data-generators/phone-function-type.md b/src/pages/docs/test-data/data-generators/phone-function-type.md index dda44471..7d148a85 100644 --- a/src/pages/docs/test-data/data-generators/phone-function-type.md +++ b/src/pages/docs/test-data/data-generators/phone-function-type.md @@ -17,10 +17,10 @@ contextual_links: url: "#selecting-phone-number-as-a-function-type-for-data-generator" - type: link name: "Cell Phone" - url: "#cellphone" + url: "#cell-phone" - type: link name: "Phone Number" - url: "#phonenumber" + url: "#phone-number" --- --- diff --git a/src/pages/docs/test-data/types/parameter.md b/src/pages/docs/test-data/types/parameter.md index 3b739df8..f6645ce9 100644 --- a/src/pages/docs/test-data/types/parameter.md +++ b/src/pages/docs/test-data/types/parameter.md @@ -10,7 +10,7 @@ contextual_links: name: "Contents" - type: link name: "How to Use Parameters in a Test Case?" - url: "#how-to-use-parameters-in-a-test-case?" + url: "#how-to-use-parameters-in-a-test-case" --- --- diff --git a/src/pages/docs/test-plans/after-test.md b/src/pages/docs/test-plans/after-test.md index 30fe15aa..2928645e 100644 --- a/src/pages/docs/test-plans/after-test.md +++ b/src/pages/docs/test-plans/after-test.md @@ -11,7 +11,7 @@ contextual_links: name: "Contents" - type: link name: "After test in Test Cases" - url: "#after-test-in-test-cases" + url: "#aftertest-in-test-cases" - type: link name: "After test in Step groups" url: "#after-test-in-step-groups" diff --git a/src/pages/docs/test-plans/cross-browser-testing.md b/src/pages/docs/test-plans/cross-browser-testing.md index b2a23bd3..ed6924ba 100644 --- a/src/pages/docs/test-plans/cross-browser-testing.md +++ b/src/pages/docs/test-plans/cross-browser-testing.md @@ -37,13 +37,13 @@ Cross Browser Testing is testing web applications across multiple browsers to en ## **Steps to Enable Cross Browser Testing** -1. Navigate to **Test Machines & Suites Selection** under the **Create Test Plan** page. *For more information on creating a test plan, refer to the [documentation on creating test plans](https://testsigma.com/docs/test-management/test-plans/overview/)*. +1. Navigate to **Test Machines & Suites Selection** under the **Create Test Plan** page. *For more information on creating a test plan, refer to the [documentation on creating test plans](https://testsigma.com/docs/test-plans/overview/)*. ![Test Plan](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_cb_1.png) -2. Under the **Test machines & suites selection** tab, select the test suite for which you want to add the test machine for test execution. *For more information on adding test suites to a test plan, refer to the [documentation on adding test suites to a test plan](https://testsigma.com/docs/test-management/test-plans/manage-test-suites/)*. +2. Under the **Test machines & suites selection** tab, select the test suite for which you want to add the test machine for test execution. *For more information on adding test suites to a test plan, refer to the [documentation on adding test suites to a test plan](https://testsigma.com/docs/test-plans/manage-test-suites/)*. ![Test Suites](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_cb_2.png) -3. Once you have selected the test suites, select the test machines to run the corresponding test suite. *For more information on adding test machines to a test plan, refer to the [documentation on adding test machines to a test plan](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/)*. +3. Once you have selected the test suites, select the test machines to run the corresponding test suite. *For more information on adding test machines to a test plan, refer to the [documentation on adding test machines to a test plan](https://testsigma.com/docs/test-plans/manage-test-machines/)*. ![Test Machines](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_cb_3.png) Note that, for *Cross Browser Testing*, test machines and test suites are selected separately. On execution, all the selected test suites are run on all selected test machines (in parallel or sequentially - depending on your selection). diff --git a/src/pages/docs/test-plans/distributed-testing.md b/src/pages/docs/test-plans/distributed-testing.md index 9fcbd6bd..543f15d1 100644 --- a/src/pages/docs/test-plans/distributed-testing.md +++ b/src/pages/docs/test-plans/distributed-testing.md @@ -35,7 +35,7 @@ Distributed testing is achieved in Testsigma by splitting up test plan execution >

Prerequisites

> > Before you begin, ensure that you have referred to: -> 1. [Documentation on creating test plans](https://testsigma.com/docs/test-management/test-plans/overview/). +> 1. [Documentation on creating test plans](https://testsigma.com/docs/test-plans/overview/). > 2. [Documentation on creating test suites](https://testsigma.com/docs/test-suites/overview/). > 3. [Documentation on creating test machine](https://testsigma.com/docs/test-plans/manage-test-machines/). diff --git a/src/pages/docs/test-plans/overview.md b/src/pages/docs/test-plans/overview.md index 1b525417..3187cfeb 100644 --- a/src/pages/docs/test-plans/overview.md +++ b/src/pages/docs/test-plans/overview.md @@ -86,7 +86,7 @@ In Testsigma, the Test Plan helps plan and organise software testing. The Test P - **Element Timeout**: Duration for which the test should wait for the element to load.![Additional Settings](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_plans_9.png) - **Accessibility Testing**: Enable this option to verify that the application meets accessibility standards, ensuring equal access and usability for users with disabilities. It follows WCAG guidelines to maintain compliance. Once enabled, accessibility reports are generated and shared via notifications. You can also select the appropriate **WCAG Version & Conformance Level** based on your requirements. Note that this feature is currently supported only on **Safari** and **Firefox** browsers. ![Accessibility Testing](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_plans_10.png) - **Recovery Actions**: Click **Recovery Actions** to open the recovery actions section and define what actions should happen. ![Recovery Actions](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_plans_11.png) - - **Post Plan Hook**: Select the Post Plan Hook and define actions or tasks to be performed once the test plan is executed and conditions are met (for more information, refer to [Post Plan Hook](https://testsigma.com/docs/test-management/test-plans/post-plan-hook/)). ![Post Plan](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_plans_12.png) + - **Post Plan Hook**: Select the Post Plan Hook and define actions or tasks to be performed once the test plan is executed and conditions are met (for more information, refer to [Post Plan Hook](https://testsigma.com/docs/test-plans/post-plan-hook/)). ![Post Plan](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/update_plans_12.png) ---