diff --git a/src/pages/docs/api/overview.md b/src/pages/docs/api/overview.md
index 8fe372d2..c5dc3dd2 100644
--- a/src/pages/docs/api/overview.md
+++ b/src/pages/docs/api/overview.md
@@ -78,44 +78,33 @@ Let’s use the first URL & retrieve the IDs of projects.
Follow the same steps from 4-6 with the other URLs mentioned in step 3 to get details of applications and uploads.
-Here’s a quick GIF demonstrating how to retrieve IDs of projects, applications, and uploads using APIs in Postman.
-
-
-
### **Get IDs using Testsigma API**
-1. Create a **Test Case** by navigating to **Create Tests > Test Cases**.
-
-
+1. Create a **Test Case** by navigating to **Create Tests > Test Cases** and create a new test case.
+
2. Add a **REST API Step**.
-
-
+
3. On the **REST API** page, select **GET** from the method dropdown.
-
+
4. On the **URL Textbox**,
-
+
- Enter https://app.testsigma.com/api/v1/projects to get project IDs.
- Enter https://app.testsigma.com/api/v1/applications to get application IDs.
- Enter https://app.testsigma.com/api/v1/uploads to get upload IDs.
Let’s use the second URL & retrieve the IDs of applications.
-
5. Click on **Authorization**, select **Authorization type** and enter the **Token**.
-
-
+
6. Click on **Send** to retrieve details of all applications.
-
+
7. You’ll find IDs of all applications in the response body.
-
-
-Here’s a quick GIF demonstrating how to retrieve IDs of projects, applications, and uploads using APIs in Testsigma.
-
+
---
diff --git a/src/pages/docs/atto/generative-ai/generate-tests/web-mobile-web.md b/src/pages/docs/atto/generative-ai/generate-tests/web-mobile-web.md
deleted file mode 100644
index e69de29b..00000000
diff --git a/src/pages/docs/atto/generative-ai/integrations/qtest.md b/src/pages/docs/atto/generative-ai/integrations/qtest.md
index 5e33af6a..0362677c 100644
--- a/src/pages/docs/atto/generative-ai/integrations/qtest.md
+++ b/src/pages/docs/atto/generative-ai/integrations/qtest.md
@@ -32,10 +32,10 @@ With qTest integrated into Testsigma, you can generate test cases by selecting s
## **Steps to Integrate Testsigma with qTest**
1. From the left navigation bar, go to **Settings > Integrations**.
- 
+ 
2. Enable toggle on **qTest** widget.
- 
+ 
3. On the **qTest Details** dialog, enter **Host URL** and **Bearer Token**.
diff --git a/src/pages/docs/configuration/api-keys.md b/src/pages/docs/configuration/api-keys.md
index 1a25d3f1..8beda841 100644
--- a/src/pages/docs/configuration/api-keys.md
+++ b/src/pages/docs/configuration/api-keys.md
@@ -25,12 +25,19 @@ You can access and control it programmatically once you generate the API key. Te
Follow the below steps to generate an API key in Testsigma:
1. Navigate to **Settings** > **API Keys** in the left-side navbar.
+
2. Click the **Generate new API Key** button in the top right corner of the screen on the **API Keys** page, and a **Generate API Key** pop-up overlay will appear.
+
-3. In the pop-up overlay for **Generate API Key**, you can enter a **Name** for your **API Key** and specify the **number of parallel test** executions for this key. The overlay provides a toggle for restricting parallel test execution for this key.
+3. In the **Generate API Key** dialog, enter a **Name** for your API key and define the number of parallel test executions. You can also use the toggle to restrict parallel execution for this key.
+
-4. After entering a name and configuring parallel settings, click the **Generate Key** button. The API key will be displayed on the screen. Click the **Copy API Key** button to copy it to your clipboard for use in your applications or scripts. 
+4. Select the desired validity period for the API key under **Expiration**.
+
+
+5. After entering a name and configuring parallel settings, click the **Generate Key** button. The API key will be automatically copied to your clipboard so you can easily use it in your applications or scripts.
+
[[info | **NOTE**:]]
| Only users with **Admin** or **Super Admin** roles can generate API keys in Testsigma.
diff --git a/src/pages/docs/continuous-integration/travis-ci.md b/src/pages/docs/continuous-integration/travis-ci.md
index 55026d29..ce3c4136 100644
--- a/src/pages/docs/continuous-integration/travis-ci.md
+++ b/src/pages/docs/continuous-integration/travis-ci.md
@@ -57,18 +57,18 @@ Below we will cover the steps in 3 parts:
## **Obtain API and Test Plan ID from Testsigma App**
1. To get API key, navigate to **Settings > API Keys** and click on **Generate API Key**.
-
+
2. On **Generate API Key** overlay, enter **Name** and click on **Generate API Key**.
-
+
3. On **API Keys** page, hover over the generated API and click on **Copy API Key**.
-
+
We will use this API Key to authenticate our remote Test Plan trigger requests from Travis CI.
4. To get Test Plan ID, navigate to **Test Plans > Test Plan > CI/CD Integrations**. You will find the execution ID for the Test Plan within the **REST API call to start Test Plan** section.
-
+
We will be using this Test Plan ID to specify which Test Plan to trigger from Travis CI.
diff --git a/src/pages/docs/desired-capabilities/geo-location-for-localization.md b/src/pages/docs/desired-capabilities/geo-location-for-localization.md
index 19eb778e..c15524f2 100644
--- a/src/pages/docs/desired-capabilities/geo-location-for-localization.md
+++ b/src/pages/docs/desired-capabilities/geo-location-for-localization.md
@@ -92,15 +92,15 @@ Below is a list of countries with their corresponding two-letter country codes t
## **Using Desired Capability to set the Location**
1. Click **Run** from **Test Case Details** page.
-
+
2. On the **Ad-Hoc Run** overlay, click **Desired Capabilities**.
-
+
3. Enter ***geoLocation*** in the **Key** field, select ***String*** as **Data type**, and set the **Value** as per country's country code.
-
+
4. Click **Run Now** to execute the test case.
-
+
---
\ No newline at end of file
diff --git a/src/pages/docs/elements/locator-precedence.md b/src/pages/docs/elements/locator-precedence.md
index 8adb0b40..7efcebd3 100644
--- a/src/pages/docs/elements/locator-precedence.md
+++ b/src/pages/docs/elements/locator-precedence.md
@@ -34,34 +34,31 @@ While creating tests for web applications, identifying locators accurately for U
## **Configuring Locator Precedence**
-1. From the left navigation bar, go to **Create Tests > Elements** and click **Record**.
-
+1. From the left navigation bar, go to **Create Tests > Elements**.
+
-2. This will open a new window with the test recorder and will be ready to start recording. Here, we entered the URL for Simply Travel Web.
-
+2. In the Elements list page, click **Record**.
+
-3. On the test recorder, click on **Locator precedence**.
-
+3. This will open a new window with the test recorder and will be ready to start recording. Here, we entered the URL for Simply Travel Web.
+
-4. This will open the **Locator precedence** overlay on **Recorder**.
-
+4. On the test recorder, click on **Locator precedence**.
+
-5. Use the **Drag Handle** to configure the priority of locators.
-
+5. This will open the **Locator precedence** overlay on **Recorder**.
+
+
+6. Use the **Drag Handle** to configure the priority of locators.
+
[[info | **NOTE**:]]
| The **Locator precedence** configured for an application from a specific user accessible only to the same user & configured application.
-6. Click on **Save** to save the configuration.
-
+7. Click on **Save** to save the configuration.
+
[[info | **NOTE**:]]
| Testsigma will revert to the default **Locator precedence** if you don't save the configuration.
-
-Here's a quick GIF demonstrating how to configure locator precedence in test recorder.
-
-
-
-
---
\ No newline at end of file
diff --git a/src/pages/docs/elements/overview.md b/src/pages/docs/elements/overview.md
index 6c0d3c48..a84a5e8c 100644
--- a/src/pages/docs/elements/overview.md
+++ b/src/pages/docs/elements/overview.md
@@ -40,27 +40,31 @@ Testsigma provides Element List Actions to manage and work with lists of element
## **Search Elements**
-Click inside the **Search bar** in the top right corner of the **Element List** page and type the name of the Element you want to find. As you type, Testsigma will show you the matching element. View the element you want by clicking on it in the search results. 
+Click inside the **Search bar** in the top right corner of the **Element List** page and type the name of the Element you want to find. As you type, Testsigma will show you the matching element. View the element you want by clicking on it in the search results.
+
---
## **Affected List**
-Click **View** in the affected list for the element allows you to see how changes to an element affect your **test cases**, **step groups**, **test suites**, and **test plans**. It helps you understand the impact of any modifications on your tests. 
+Click **View** in the affected list for the element allows you to see how changes to an element affect your **test cases**, **step groups**, **test suites**, and **test plans**. It helps you understand the impact of any modifications on your tests.
+
---
## **Sort Elements**
-Click the **Sort by** option in the menu bar on the **Elements List** page and arrange your elements based on criteria such as **Title**, **Created Date**, or **Updated Date**. Sorting will help you prioritise and manage your elements easily. 
+Click the **Sort by** option in the menu bar on the **Elements List** page and arrange your elements based on criteria such as **Title**, **Created Date**, or **Updated Date**. Sorting will help you prioritise and manage your elements easily.
+
---
## **Filter Elements**
1. Click on **Show Filters** in the menu bar on the **Elements List** page.
-2. Select **Add Filter** from the drop-down list. Choose from the following filtering options: **Element Value**, **Name**, **Linked to Test Case**, **Labels**, **Screen Name**, **Element Type**, **Created By**, **Created Date** and **Updated Date**.
+
-
+2. Select **Add Filter** from the drop-down list. Choose from the following filtering options: **Element Value**, **Name**, **Linked to Test Case**, **Labels**, **Screen Name**, **Element Type**, **Created By**, **Created Date** and **Updated Date**.
+
You can use user-defined custom fields and the default fields to filter elements. You can modify the filtering options by selecting **Add Filter** from the drop-down list and using multiple filters to obtain granular results.
@@ -69,26 +73,41 @@ You can use user-defined custom fields and the default fields to filter elements
## **Save Element Filter**
1. Click **Show Filters** in the menu bar on the **Elements List** page.
+
+
2. Click **Add Filter** to open the drop-down list and select the desired filters.
+
+
3. Click **Save Filter** will make the drop-down list appear for saving the current filter, and select **As New** will open a pop-up window named **Save filter config as**. Click **Reset** to discard the current filter.
+
+
4. Enter a name for the configuration in the **Config Name** field and mark the checkbox to make it **Public** (Visible for all users with access to the project). Then, click **Save** to save the filter.
-5. Click **Saved Filters** in the menu bar on the **Elements List** page to open the drop-down list. In **Custom Filters**, locate the saved filter, select the filter and mouse over to the filter, and click the **Edit** button next to the filter name to edit it. To delete the saved filter, click the **Delete** button. 
+
+
+5. Click **Saved Filters** in the menu bar on the **Elements List** page to open the drop-down list. In **Custom Filters**, locate the saved filter, select the filter and mouse over to the filter, and click the **Edit** button next to the filter name to edit it. To delete the saved filter, click the **Delete** button. 
---
## **View Saved Element Filters**
1. Click on **Saved Filters** in the menu bar to open the drop-down list on the **Elements List** page.
-2. Find the saved filter within **Custom** or **Predefined Filters** and choose it to view the filtered version. 
+
+2. Find the saved filter within **Custom** or **Predefined Filters** and choose it to view the filtered version.
+
---
## **Update Saved Element Filter**
1. In the **Elements List** Page, click **Saved Filters** from the menu bar.
+
2. Open the drop-down list by clicking **Add Filter** and choose the additional filtering options you want to apply to the existing ones.
+
3. Once you have made your desired changes, click on **Save Filter**. This will display a drop-down list, allowing you to save the updated filter. If you want to replace the existing filter, click **Replace Existing**, which will prompt a pop-up window named **Update filter config**.
-4. In the **Update filter config** pop-up window, you can enter a new name for the updated filter if necessary. Additionally, you can continue configuring by marking the checkbox to make it **Public** (visible for all users with access to the project). Finally, click **Update** to save the changes to the filter. 
+
+
+4. In the **Update filter config** pop-up window, you can enter a new name for the updated filter if necessary. Additionally, you can continue configuring by marking the checkbox to make it **Public** (visible for all users with access to the project). Finally, click **Update** to save the changes to the filter.
+
[[info | NOTE:]]
| If you wish to discard the current filter, click All in the menu bar on the Elements List page.
@@ -99,4 +118,4 @@ You can use user-defined custom fields and the default fields to filter elements
Once you create and add elements to a test case, they are saved in the corresponding project in Testsigma. You can reuse these elements in new test steps in the same project.
----
\ No newline at end of file
+---
diff --git a/src/pages/docs/integrations/bug-reporting/jira.md b/src/pages/docs/integrations/bug-reporting/jira.md
index 019104f2..08e12d6a 100644
--- a/src/pages/docs/integrations/bug-reporting/jira.md
+++ b/src/pages/docs/integrations/bug-reporting/jira.md
@@ -92,7 +92,7 @@ You can integrate Testsigma with Jira to push bugs directly to your Jira project
[[info | **NOTE**:]]
-| To link to an existing Jira issue, click **Link to Issue**, search for the issue, and then click **Link to Ticket**.
+| To link to an existing Jira issue, click **Link To Issue**, search for the issue, and then click **Link to Ticket**.
|
| 
diff --git a/src/pages/docs/integrations/bug-reporting/monday.com.md b/src/pages/docs/integrations/bug-reporting/monday.com.md
index 71a3c4f8..4eb71d56 100644
--- a/src/pages/docs/integrations/bug-reporting/monday.com.md
+++ b/src/pages/docs/integrations/bug-reporting/monday.com.md
@@ -36,31 +36,29 @@ Testsigma monday.com integration helps you create issues in monday.com directly
## **Integrating Monday.com With Testsigma**
1. Navigate to **Settings > Integrations** and enable the toggle on **monday.com** widget.
-
+
2. On the **Monday.com details** prompt, enter **Account URL**, **API Key**, **Confirm API Key** and click on **Save & Enable**.
-
+
---
## **Creating a Bug**
1. Navigate to **Run Results > Test Case Result**, where you want to add a bug.
-
+
2. Click on **Report Bug**.
-
-
+
3. On **Report** overlay, click on the **Monday.com** icon.
-
+
4. On the **Create New Issue** prompt, click on **Create Ticket**.
-
+
[[info | **NOTE**:]]
-| - If you want to link to an existing issue on **Monday.com**, click on the **Link to Issue** button, search for a current issue in the search field, and click on Link Issue to add a link to an existing Issue on **Monday.com**. Otherwise, enter the bug details in the form as required.
-| - When the bug is created, some additional details regarding the Test Result, such as the test execution video and step screenshots, are added automatically by Testsigma. This helps the developer who checks the issue in **Monday.com** better understand the issue/bug with more context.
-
+| - To link to an existing Jira issue, click **Link To Issue**, search for the issue, and then click **Link to Ticket**.
+When a bug is created, Testsigma automatically adds additional details about the Test Result, such as the test execution video and step screenshots. This helps the developer who checks the issue in **Monday.com** better understand the issue/bug with more context.
----
\ No newline at end of file
+---
diff --git a/src/pages/docs/integrations/test-management/linear.md b/src/pages/docs/integrations/test-management/linear.md
index 628f1ebd..73016ec7 100644
--- a/src/pages/docs/integrations/test-management/linear.md
+++ b/src/pages/docs/integrations/test-management/linear.md
@@ -34,45 +34,30 @@ You can integrate Testsigma with Linear to push bugs directly to Linear’s proj
## **Steps to Integrate Testsigma with Linear**
1. Navigate to **Settings > Integrations**.
-
+ 
-2. Enable toggle on **Linear** widget.
-
+2. Enable the toggle on the **Linear** widget.
+
-3. On the **Linear Details** prompt, enter **API Key**.
-
-
-4. Click on **Save & Enable**.
-
-
-Here’s a quick GIF demonstrating how to integrate Testsigma with Linear.
-
+3. On the **Linear Details** prompt, enter your API key in the **API Key** and click **Save & Enable**.
+
---
## **Creating a Bug**
1. Navigate to **Run Results > Test Case Result**, where you want to add a bug.
-
+
2. Click on **Report Bug**.
-
+
3. On **Report** overlay, click on **Linear** icon.
-
+
-4. On the **Create New Issue** prompt,
- - Select the **Team & Project**.
- 
- - Enter **Title & Description**.
- 
-
-5. Click on **Create Ticket**.
-
+4. On the **Report** overlay, review the auto-generated title and description. If needed, update them and click **Report Bug**.
+
[[info | **NOTE**:]]
-| If you want to link to an existing issue on Linear, click on the Link to Issue, search for an existing issue in the search field and click on Link Issue to add a link to an existing Issue.
-
-Here’s a GIF demonstrating how to report bugs from Testsigma.
-
+| If you want to link to an existing issue on Linear, click the **Link To Issue** tab, search for an existing issue in the search field and click **Link Issue** to add a link to an existing Issue.
---
\ No newline at end of file
diff --git a/src/pages/docs/live-editor/intro-testsigma-terminal.md b/src/pages/docs/live-editor/intro-testsigma-terminal.md
index d65a7d1a..671b0209 100644
--- a/src/pages/docs/live-editor/intro-testsigma-terminal.md
+++ b/src/pages/docs/live-editor/intro-testsigma-terminal.md
@@ -48,13 +48,19 @@ Testsigma Terminal provides complete control over test case execution and debugg
## **Getting Started**
- - **Installing Testsigma Terminal**
-
- - **Editing a Test Case Using Copilot**
+ - **[Documentation on Installing Testsigma Terminal](https://testsigma.com/docs/live-editor/installing-testsigma-terminal/)**
+
+ - **[Documentation on Installing Testsigma Terminal on Linux](https://testsigma.com/docs/live-editor/installing-testsigma-terminal-on-linux/)**
+
+ - **[Documentation on Installing Testsigma Terminal on Windows](https://testsigma.com/docs/live-editor/installing-testsigma-terminal-on-windows/)**
+
+ - **[Documentation on Components of Testsigma Terminal](https://testsigma.com/docs/live-editor/components-of-testsigma-terminal/)**
+
+ - **[Documentation on Editing a Test Case Using Copilot](https://testsigma.com/docs/live-editor/editing-test-case/)**
- - **FAQs on Testsigma Terminal**
+ - **[Documentation on FAQs on Testsigma Terminal](https://testsigma.com/docs/live-editor/faqs-on-copilot/)**
- - **Troubleshooting Guide for Testsigma Terminal**
+ - **[Documentation on Troubleshooting Guide for Testsigma Terminal](https://testsigma.com/docs/live-editor/troubleshooting-for-copilot/)**
---
diff --git a/src/pages/docs/projects/overview.md b/src/pages/docs/projects/overview.md
index e1f5225a..65485edb 100644
--- a/src/pages/docs/projects/overview.md
+++ b/src/pages/docs/projects/overview.md
@@ -37,71 +37,51 @@ This document will walk you through **creating**, **editing**, **switching**, an
## **Creating a Project**
1. Navigate to **Create New** and click on **Project** from the dropdown menu.
-
+
2. Enter the **Project Name** and **Description** (Optional).
-
+
[[info | **NOTE**:]]
| Custom fields you create for your projects under **Settings > Custom Fields > Projects** will appear here.
-3. If your project involves multiple applications, check **Allow adding multiple applications in this project** checbox. To add an application, click **Add Application**, select the **Application Type** from the drop-down menu, and give it a **Name**. By default, the project is set up for a single application.
-
+3. If your project involves multiple applications, check **Allow adding multiple applications in this project** checkbox. To add an application, click **Add Application**, select the **Application Type** from the drop-down menu, and give it a **Name**. By default, the project is set up for a single application.
+
4. Also, if you want multiple versions for each application, check **Allow multiple versions for applications** checbox.
-
+
5. Click on **Create**.
-
-
-### **Try this interactive demo to learn how to create a Project!**
-
-
+
---
## **Editing a Project**
1. Navigate to **Project > Project Settings**.
-
+
2. This will open the **Edit Project** dialog.
-
+
3. You can update **Project Details**, **Multiple Applications** and **Versions** from here. Also, you can add **Project Members**, **Test Case Types**, and **Requirement Types** on the same dialog.
-
+
4. Click on **Update** to save the changes.
-
-
+
>
> **Adding**, **Editing**, and **Deleting** Applications & Versions can be done under **Project Settings > Applications**.
-
-### **Try this interactive demo to learn how to edit a Project!**
-
-
-
---
## **Switching Projects**
1. Click on the current **Project** from **Dashboard**.
-
+
2. Select **Project**, **Application**, and **Version** from respective dropdowns and click on **Go to project**.
-
+
3. You’ll be redirected to the dashboard of the selected project.
@@ -110,31 +90,17 @@ This document will walk you through **creating**, **editing**, **switching**, an
## **Deleting a Project**
1. Navigate to **Project > Project Settings**.
-
+
2. Click on **Delete**.
-
-
-3. On the **Delete project** dialog, enter **DELETE** and click on **Delete**.
-
-
-4. On the **Delete project** prompt, enter **DELETE** and click on **Delete**.
-
-
-
-### **Try this interactive demo to learn how to delete a Project!**
-
-
+
+3. On the **Delete project** prompt, enter **DELETE** and click on **Delete**.
+
[[info | **NOTE**:]]
| Deleting a Project will delete:
| - All Applications & Application Versions within this Project.
| - All Test cases, Elements, Test data profiles, Custom functions, Uploads, Requirements, Test suites, Test plans, Run results and Environments associated with this project.
----
\ No newline at end of file
+---
diff --git a/src/pages/docs/projects/settings/test-case-priorities.md b/src/pages/docs/projects/settings/test-case-priorities.md
index a9fb6097..96a2138a 100644
--- a/src/pages/docs/projects/settings/test-case-priorities.md
+++ b/src/pages/docs/projects/settings/test-case-priorities.md
@@ -15,7 +15,7 @@ Testsigma provides a default set of Test Case Priorities, which can be edited an
Default **Test Case Priorities** available: **Critical**, **Major**, **Medium**, **Minor**
-
+
[[info | **NOTE**:]]
| Users can no longer add new priorities in Testsigma but can continue using the default priorities available in the application.
diff --git a/src/pages/docs/reports/runs/custom-pdf-report.md b/src/pages/docs/reports/runs/custom-pdf-report.md
index 0fc9f889..7dc11fd1 100644
--- a/src/pages/docs/reports/runs/custom-pdf-report.md
+++ b/src/pages/docs/reports/runs/custom-pdf-report.md
@@ -51,13 +51,15 @@ Custom PDF Report Generator in Testsigma allows you to create detailed and custo
To generate reports, you need specific IDs depending on the level of detail you want:
1. Navigate to the **Run Result** from which you want to retrieve the Run ID.
-2. For **test plan** level reports, Use the Run ID directly from the Run Result page. You can find this in the Execution ID or the URL endpoint. Copy the Run ID from the Run Result page. 
+2. For **test plan** level reports, use the Run ID from the Run Result page. You can find the Run ID in the URL endpoint. For example, in **/results/664/runs/880**, 880 is the Run ID.
+
3. For Test Machine, Test Suite, or Test Case level reports:
- Right-click on the page and select **Inspect** to open Developer Tools.
- Go to the **Network** tab.
- In the Testsigma application, select the test case, suite, or test machine in the Run Result details page to get the response.
- In the Developer Tools, under the **Network** tab, find the response results in the name section and click **Preview**.
- - Unhide the **Content** and copy the required **ID**. 
+ - Unhide the **Content** and copy the required **ID**.
+ 
---
diff --git a/src/pages/docs/salesforce-testing/metadata-connections.md b/src/pages/docs/salesforce-testing/metadata-connections.md
index 3c1bcbfd..257b9b4f 100644
--- a/src/pages/docs/salesforce-testing/metadata-connections.md
+++ b/src/pages/docs/salesforce-testing/metadata-connections.md
@@ -45,23 +45,23 @@ In Testsigma, you can create a Salesforce application and establish a Metadata c
## **Steps to Create Metadata Connection**
1. Click on **Create metadata connection** on **Salesforce connections page**.
- 
+
2. This will open the **Metadata connection** prompt.
- 
+
3. On **Metadata connection** prompt,
- - Enter **Connection name**, which is generally the user role you connect through, e.g., **Admin**.
- 
- [[info | **NOTE**:]]
- | You can also choose a custom name for the connection.
- - Choose the **Production / Developer edition**, if you’re testing the product environment or Sandbox, if you’re testing the staging environment from **Connect with** dropdown.
- 
- - Choose the **Authentication type** from the dropdown. In this example, we are choosing **OAuth 2.0**.
- 
+ - Enter **Connection name**, which is generally the user role you connect through, e.g., **Admin**.
+ 
+ [[info | **NOTE**:]]
+ | You can also choose a custom name for the connection.
+ - Choose the **Production / Developer edition**, if you’re testing the product environment or Sandbox, if you’re testing the staging environment from **Connect with** dropdown.
+ 
+ - Choose the **Authentication type** from the dropdown. In this example, we are choosing **OAuth 2.0**.
+ 
-
+
ℹ️Authentication Types:
@@ -76,37 +76,49 @@ There are two ways to Authenticate:
- - Click on **Authorise & Connect**.
- 
+ - Enter the **Username** associated with your Salesforce account.
+ 
- - A new window will open up requesting for **Salesforce Login**. Enter the credentials and click on **Log In**.
- 
+ - Enter the **Consumer key** generated from your Salesforce Connected App configuration.
+ 
- - This will display the **Environment** associated with the credentials. Click on **Start metadata sync**.
- 
+ - Enter the **Consumer secret** corresponding to the Consumer key.
+ 
- - Wait until the sync is complete. This will take some time.
- 
+ - Enter the **Callback URL** associated with the connected app.
+ 
+
+ - Click on **Authorise & Connect**.
+ 
+
+ - A new window will open up requesting for **Salesforce Login**. Enter the credentials and click on **Log In**.
+ 
+
+ - This will display the **Environment** associated with the credentials. Click on **Start metadata sync**.
+ 
+
+ - Wait until the sync is complete. This will take some time.
+ 
4. Once Metadata sync is successful, you can create test cases by clicking **Create Test Case**.
- 
+ 
---
## **Steps to Add Multiple Metadata Connections**
-1. Navigate to **Settings > SF Metadata**.
- 
+1. Navigate to **Settings > SF Connections**.
+
2. Select a **Project** and **Application** from the dropdown menu where you want to add metadata connections.
- 
+
3. Click **Add New**. This will open the **Metadata Connection** dialog.
- 
+
4. Follow the steps in the [documentation on creating Salesforce Metadata Connections](https://testsigma.com/docs/salesforce-testing/metadata-connections/#steps-to-create-metadata-connection) to add the **Metadata Connections**.
- 
+
[[info | **NOTE**:]]
| You can also copy existing metadata from multiple metadata connections added in older versions while creating a new version by following these steps.
@@ -114,13 +126,13 @@ There are two ways to Authenticate:
|
|
| 1. Go to **Project > Project Settings > Versions**, and click **New Version**.
-| 
+| 
|
| 2. Enter a **Name** and optional **Description**.
-| 
+| 
|
| 3. Go to **Projects**, and then navigate to the newly created **Version**. The system redirects you to the **Salesforce Connections** page.
-| 
+| 
|
| - Click **Select Existing Metadata Connection** to copy metadata from a previous version.
| - Click **Create Metadata Connection** to create a new metadata connection.
@@ -130,11 +142,11 @@ There are two ways to Authenticate:
## **Executing Test Case against a Salesforce Metadata Connection**
1. Create a Test Case and click **Run** on the **Action Panel**.
- 
+
[[info | **NOTE**:]]
| Before you configure **Ad-Hoc Run**, you need to add user connections as **Environments** in Testsigma. For information on creating Environments, see [Environments](https://testsigma.com/docs/test-data/types/environment/).
-| 
+| 
2. On the **Ad-Hoc Run** overlay,
@@ -143,24 +155,24 @@ There are two ways to Authenticate:
- Select a Salesforce Metadata Connection against which you want to execute the test case.
- 
+ 
[[info | **NOTE**:]]
| You can also configure the same for **Test Plans** in **Test Plan Settings > Additional Settings** by selecting **Environment** and a **Salesforce Metadata Connection**.
-| 
+| 
---
## **Steps to Edit Metadata Connection**
1. From the **Dashboard**, click on **SF Connections**.
- 
+
2. In the **Metadata connection** section, hover over the connection, click on the kebab menu, and choose **Edit connection** from the dropdown menu.
- 
+
3. On the **Metadata connection** prompt, make the necessary changes and click on **Authorise & Connect**.
- 
+
[[info | **NOTE**:]]
| You can not update the Metadata connection with a different environment.
@@ -172,11 +184,10 @@ There are two ways to Authenticate:
To refresh metadata, you have two options:
1. From the **Dashboard**, go to **SF Connections** and click on **Refresh Metadata**.
- 
-
+
2. Click on **Refresh Metadata** directly from the dashboard.
- 
+
[[info | **NOTE**:]]
@@ -192,10 +203,10 @@ The activity log tab on the connection details page displays the information abo
### **Steps to View Metadata Activity Logs**
1. Navigate to **SF connections** and click on **Activity log**. This will open the **Activity log** dialog.
- 
+
2. The **Activity log** dialog displays information regarding past metadata sync triggers.
- 
+
diff --git a/src/pages/docs/test-cases/create-steps-restapi/store-variables.md b/src/pages/docs/test-cases/create-steps-restapi/store-variables.md
index cc1c9d53..bf095054 100644
--- a/src/pages/docs/test-cases/create-steps-restapi/store-variables.md
+++ b/src/pages/docs/test-cases/create-steps-restapi/store-variables.md
@@ -32,8 +32,7 @@ Stored variables in RESTful API testing are variables that are used to store dat
1. **Send** an API request, and at the bottom of the screen, the **response body** will appear for the request you sent.
2. Click **Outline**, then select **Store Variable** to upload it directly into **Stored Variables** tab.
-
- 
+ 
[[info | NOTE:]]
| - Navigate to **Stored Variables** > **Response Body** tab, and click **Store Variable** to add the field manually.
@@ -45,8 +44,7 @@ Stored variables in RESTful API testing are variables that are used to store dat
1. Send an **API Request**. The **Response Body** for your request will appear at the bottom of the screen.
2. Hover over the HTML lines in the **Response Body** and select the attribute to store variables. This action automatically stores the attribute and displays info under the **Stored Variables** tab.
-
- 
+ 
---
@@ -55,8 +53,6 @@ Stored variables in RESTful API testing are variables that are used to store dat
1. Click **Store Variable** in the **Headers tab**. Enter the **variable name** and enter the **header name**. Click **Create** to store variable.
2. At the bottom of the page, click the **Headers** tab, mouse over to the response header, and click **store variable**; it will update in the stored variables headers tab.
+ 
- 
-
----
-
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/create-test-steps/overview.md b/src/pages/docs/test-cases/create-test-steps/overview.md
index b717431d..f60c5f88 100644
--- a/src/pages/docs/test-cases/create-test-steps/overview.md
+++ b/src/pages/docs/test-cases/create-test-steps/overview.md
@@ -37,23 +37,23 @@ In Testsigma terminology, each automated action executed by the test script is a
### **Web & Mobile Web**
1. From the left navigation bar, go to **Create Tests** > **Test Cases**.
- 
+ 
2. In the **Test Case Explorer** section, expand the required feature and click the **+** icon next to the target scenario. This will open a dialog box.
- 
+ 
3. On the dialog box, validate the target feature and scenario, enter the name, and click **Create**.
- 
+ 
Alternatively, click the **+** icon next to the search bar and select **New Test Case** from the drop-down menu. Follow the same steps as above.
- 
+ 
[[info | **NOTE**:]]
|
| - You can edit the target feature and scenario by clicking on the **Edit** icon. This will open the **Select Location** dialog.
-| 
+| 
| - In the **Select Location** dialog, select the target feature and scenario and click **Confirm**.
-| 
+| 
| - This feature functions consistently across all applications.
4. Use NLPs to create test steps as per the test case scenario.
@@ -68,21 +68,21 @@ In Testsigma terminology, each automated action executed by the test script is a
7. Click on **Submit**
Here's a screenshot of the test steps that were reproduced in the Testsigma application:
- 
+ 
### **Android and iOS**
1. From the left navigation bar, go to **Create Tests** > **Test Case**.
- 
+ 
2. In the **Test Case Explorer** section, expand the required feature and click the **+** icon next to the target scenario. This will open a dialog box.
- 
+ 
3. On the dialog box, validate the target feature and scenario, enter the name, and click **Create**.
- 
+ 
Alternatively, click the **+** icon next to the search bar and select **New Test Case** from the drop-down menu. Follow the same steps as above.
- 
+ 
4. Use NLPs to create test steps as per the test case scenario.
@@ -90,7 +90,7 @@ In Testsigma terminology, each automated action executed by the test script is a
|
| - By default, the first step for Android and iOS applications is **Launch App**.
| - You can also add steps above and below a test step by clicking on **Step Above** & **Step Below**.
-| 
+| 
---
@@ -100,26 +100,25 @@ In Testsigma terminology, each automated action executed by the test script is a
### **Web and Mobile Web**
1. From the left navigation bar, go to **Create Tests** > **Test Cases**.
- 
+ 
2. In the **Test Case Explorer** section, expand the required feature and click the **+** icon next to the target scenario. This will open a dialog box.
- 
-
+ 
3. On the dialog box, validate the target feature and scenario, enter the name, and click **Create**.
- 
+ 
Alternatively, click the **+** icon next to the search bar and select **New Test Case** from the drop-down menu. Follow the same steps as above.
- 
+ 
4. Create a test step using the URL that you want to automate and click **Create Step**.
- 
+ 
5. Click **Record**.
- 
+ 
6. A new window will open the given URL.
- 
+ 
[[info | **NOTE**:]]
|
@@ -130,36 +129,36 @@ In Testsigma terminology, each automated action executed by the test script is a
8. The actions will be recorded and added to the test case in the background.
9. Once the required actions are complete, click on **Stop** to switch back to the test case details page.
- 
+ 
-10. You can see the steps recorded in the test case details page.
- 
+10. You can see the steps recorded in the test case details page.
+ 
### **Android and iOS**
1. From the left navigation bar, go to **Create Tests** > **Test Cases**.
- 
+ 
2. In the **Test Case Explorer** section, expand the required feature and click the **+** icon next to the target scenario. This will open a dialog box.
- 
+ 
3. On the dialog box, validate the target feature and scenario, enter the name, and click **Create**.
- 
+ 
Alternatively, click the **+** icon next to the search bar and select **New Test Case** from the drop-down menu. Follow the same steps as above.
- 
+ 
4. Click **Create Step** and click **Record**.
- 
+ 
5. In the **Record test steps** overlay, select the required options in the **Test Lab** and **Test Machine** sections.
- 
+ 
6. Click **Upload** and upload the required file.
- 
+ 
7. Click **Record**.
- 
+ 
8. Perform the actions on the application and once the required actions are complete, stop the recording to switch back to the test case details page.
diff --git a/src/pages/docs/test-cases/manage/import-postman-to-testsigma.md b/src/pages/docs/test-cases/manage/import-postman-to-testsigma.md
index 2b632524..d5259609 100644
--- a/src/pages/docs/test-cases/manage/import-postman-to-testsigma.md
+++ b/src/pages/docs/test-cases/manage/import-postman-to-testsigma.md
@@ -43,12 +43,24 @@ Testsigma simplifies API test case migration by seamlessly importing Collections
After exporting your Postman Collection as JSON or Zipped format, follow these steps to import it into Testsigma:
-1. Navigate to **Settings** > **Imports and Exports**.
-2. Click **Import** and select **Import Postman Collection** tab. 
-3. Click **Select File to Import** and choose the file to import; select the **project**, **application**, and **version**.
-4. After you upload the file, Testsigma organizes **Collections**, **Environments**, and **Variables** into **Test Suites**, **Test Cases**, **Test Steps**, **Test Data Profiles**, and **Environments**. This feature enables you to easily understand how the imported file is organized.
-5. Click **Start Importing** to transfer a collection into Testsigma. 
-6. Testsigma will notify you via **email** once the import is complete. 
+1. Navigate to **Settings** > **Imports**.
+
+
+2. In the **Imports** page, click **Import**.
+
+
+3. In the dialog box, click **Select File to Import** and choose the file to import.
+
+
+4. Select the **project**, **application**, and **version**.
+
+
+5. After you upload the file, Testsigma organizes **Collections**, **Environments**, and **Variables** into **Test Suites**, **Test Cases**, **Test Steps**, **Test Data Profiles**, and **Environments**. This feature enables you to easily understand how the imported file is organized.
+
+6. Click **Start Importing** to transfer a collection into Testsigma.
+
+
+7. Testsigma will notify you via **email** once the import is complete.
---
@@ -56,12 +68,24 @@ After exporting your Postman Collection as JSON or Zipped format, follow these s
Import your Postman Environments to Testsigma in JSON or Zipped format. Follow below the simple steps:
-1. Navigate to **Settings** > **Imports and Exports**.
-2. Click **Import** and select **Import Postman Collection** tab. 
-3. Click **Select File to Import** and choose the file to import; select the **project**, **application**, and **version**.
-4. Click **Start Importing** to transfer the environments into Testsigma. 
-5. Testsigma will notify you via **email** once the import is complete. 
-6. After importing, Testsigma organizes **Environments** and **Global Variables** into **Environments**. This helps you quickly see how the imported file is mapped.
+1. Navigate to **Settings** > **Imports**.
+
+
+2. In the **Imports** page, click **Import**.
+
+
+3. In the dialog box, click **Select File to Import** and choose the file to import.
+
+
+4. Select the **project**, **application**, and **version**.
+
+
+5. Click **Start Importing** to transfer the environments into Testsigma.
+
+
+6. Testsigma will notify you via **email** once the import is complete.
+
+7. After importing, Testsigma organizes **Environments** and **Global Variables** into **Environments**. This helps you quickly see how the imported file is mapped.
[[info | NOTE:]]
| You can verify the imported Collection and Environment files by downloading them.
diff --git a/src/pages/docs/test-cases/step-types/for-loop.md b/src/pages/docs/test-cases/step-types/for-loop.md
index e56b23fd..0c68daee 100644
--- a/src/pages/docs/test-cases/step-types/for-loop.md
+++ b/src/pages/docs/test-cases/step-types/for-loop.md
@@ -42,20 +42,20 @@ If you want to run a test case based on the above test data profile, but you jus
## **Using For Loop in Test Cases**
-1. Navigate to **Create Tests > Test Cases**, and click on **Create Test Case**.
- 
+1. Navigate to **Create Tests > Test Cases** and create a test case.
+ 
2. On **Test Case Details** page, click on the option on the left side of the test step.
- 
+ 
3. This will open a side panel.
- 
+ 
4. Hover over to the options and click on **For Loop**.
- 
+ 
5. This option opens a drop down of NLPs that can be used inside the test step.
- 
+ 
- If you want to iterate through all the data sets of your test data profile from start to end use the below NLP:
@@ -75,7 +75,7 @@ If you want to run a test case based on the above test data profile, but you jus
- Another NLP to filter test data profile based on parameter value is the following:
-1. Select the suitable NLP to include in the test step and finish creating **For Loop** test step.
+6. Select the suitable NLP to include in the test step and finish creating **For Loop** test step.
---
diff --git a/src/pages/docs/test-data/create-data-profiles.md b/src/pages/docs/test-data/create-data-profiles.md
index c2078a12..10786904 100644
--- a/src/pages/docs/test-data/create-data-profiles.md
+++ b/src/pages/docs/test-data/create-data-profiles.md
@@ -47,37 +47,44 @@ Test data profiles can significantly enhance the efficiency of your testing proc
## **Create a Test Data Profile**
-1. Navigate to **Test Data** > **Test Data Profiles** and click on **Create Test Data Profile**. 
-2. On the **Test Data Profile** details page, enter the **Title** for your test data profile in the **Test Data Profile Info** section. 
-3. To create rows and columns, click the **+** icon next to the right navigation bar to add a new column, and click the **+** icon below the table to add a new row. 
+1. Navigate to **Test Data** > **Test Data Profiles** and click on **Create Test Data Profile**.
+
+
+2. On the **Test Data Profile** details page, enter the **Title** for your test data profile in the **Test Data Profile Info** section.
+
+
+3. To create rows and columns, click the **+** icon next to the right navigation bar to add a new column, and click the **+** icon below the table to add a new row. 
+
[[info | **NOTE**:]]
| If you must create test data expected to fail, enable the toggle button in the **ETF** (Expected to Fail) column.
-4. Click on **Create** to save your test data profile.
-Here’s a quick GIF that demonstrates how to create a test data profile.
-
+4. Click on **Create** to save your test data profile.
+
---
## **Associate a Test Data Profile with a Test Case**
-1. Navigate to **Create Tests** > **Test Cases** and click on **Create Test Case**. 
+1. Navigate to **Create Tests** > **Test Cases** and open a test case.
+
+2. On the Test Case details page, click on **Test Case Settings** from the right navigation bar.
+
+
+3. In the **Test Case Settings** page, choose a **Test Data Profile** from the dropdown menu.
+
-2. On the Test Case details page, click on **Test Case Settings** from the right navigation bar. 
-3. In the **Test Case Settings** page, choose a **Test Data Profile** from the dropdown menu. 
4. Enable the **Data-Driven** toggle. Once enabled, you can filter and customise the data sets from your test data profile for use in your test case using the filters Iteration, Set Name, and Parameter.
- **Iteration**: Filters sequential data sets using greater than, less than, or between operations.
- **Set Name**: Filters non-sequential data sets by set names using operations like equals, contains, starts with, and ends with.
- - **Parameter**: Filters non-sequential data sets using parameters used in data sets. 
+ - **Parameter**: Filters non-sequential data sets using parameters used in data sets. 
---
## **Using Test Data Profile in a Test Case**
-1. In **Test Case detials** page, click **Add new** step, and use **NLP** to create a new test step. 
-2. Include a placeholder for the **test data**. Click the **test data** placeholder, select @ Parameter from the test data types dropdown, and choose the parameter from right overlay. 
+1. In **Test Case details** page, click **Add new** step, and use **NLP** to create a new test step. 
-Here is a quick GIF demonstrating the above workflow: 
+2. Include a placeholder for the **test data**. Click the **test data** placeholder, select @ Parameter from the test data types dropdown, and choose the parameter from right overlay. 
---
@@ -88,7 +95,8 @@ In data-driven testing, you can iterate values from start to end. To iterate fro
**Set Variables in a Prerequisite Test Case**
1. Navigate to Create Tests > Test Cases.
-2. Store the start and end data values in your test steps using the variables RunTime\_TestData\_Set\_Start and **RunTime\_TestData\_Set\_End**. 
+2. Store the start and end data values in your test steps using the variables RunTime\_TestData\_Set\_Start and **RunTime\_TestData\_Set\_End**.
+