Dev >>>>>> Main

src/components/header.jsx

@@ -52,14 +52,14 @@ const Header = () => {
             >
               BOOK A DEMO
             </a>
-            <a
+            {/* <a
               id={'signup-btn'}
               target={'_blank'}
               className='border border-primary_teal_green px-4 py-1.5 base-teal-gradient text-white rounded'
               href='/signup'
             >
               GET STARTED FREE
-            </a>
+            </a> */}
           </div>
           <nav className='flex w-11/12 gap-4'>
             <a

src/pages/docs/api/export-test-reports.md

@@ -18,6 +18,9 @@ contextual_links:
 - type: link
   name: "Report Generation Flow"
   url: "#report-generation-flow"
+- type: link
+  name: "Retrieve the Result IDs"
+  url: "#retrieve-the-result-ids"
 - type: link
   name: "API Specification"
   url: "#api-specification"
@@ -46,7 +49,7 @@ Testsigma allows you to export test reports in XML, PDF, or Excel format at any
 > Before you begin, ensure that:
 > 1. An API key exists for your Testsigma account. Refer to the [documentation on generating API keys](https://testsigma.com/docs/configuration/api-keys/).
 > 2. The test plan run is complete.
-> 3. The result ID for the level you want to export is available. Refer to the [documentation on fetching test results at all levels](https://testsigma.com/docs/api/test-results-at-all-levels/).
+> 3. The result ID for the level you want to export is available. Refer to [Retrieve the Result IDs](#retrieve-the-result-ids) for test machine and test suite exports, or to the [documentation on fetching test results at all levels](https://testsigma.com/docs/api/test-results-at-all-levels/).
 > 4. PDF report export is enabled for your account, if you export in PDF format.
 
 ---
@@ -81,6 +84,46 @@ Report generation is asynchronous. The same endpoint both triggers the report an
 
 ---
 
+## **Retrieve the Result IDs**
+
+The test machine and test suite result IDs are not exposed in the UI. Retrieve them from the network requests that the **Run Results** page sends, then use them in the export endpoint for that level.
+
+[[info | NOTE:]]
+| The test plan run ID is available in the URL of the **Run Results** page. Refer to the [documentation on obtaining the run ID](https://testsigma.com/docs/api/test-plans/#obtaining-the-run-id).
+
+### **Retrieve the Test Machine Result ID**
+
+1. Open the completed test plan run on the **Run Results** page.
+2. From the view dropdown, select **Test Machines**.
+3. Select the test machine you want to export.
+4. Open the browser developer tools and go to the **Network** tab.
+5. Clear the network log.
+6. Reload the page.
+7. Select the **Environments** request in the network log.
+8. In the **Preview** panel, copy the machine result ID from the response.
+   ![Machine ID](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/machine_id_fetch.png)
+
+9. Use the copied value as **{MACHINE\_RESULT\_ID}** in the export request.
+
+### **Retrieve the Test Suite Result ID**
+
+1. Open the completed test plan run on the **Run Results** page.
+2. From the view dropdown, select **Test Suites**.
+3. Select the test suite you want to export.
+4. Open the browser developer tools and go to the **Network** tab.
+5. Clear the network log.
+6. Reload the page.
+7. Select the **Test Suite** request in the network log.
+8. In the **Preview** panel, copy the test suite result ID from the response.
+   ![Suite ID](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/fetch_suite_id.png)
+
+9. Use the copied value as **{SUITE\_RESULT\_ID}** in the export request.
+
+[[info | NOTE:]]
+| The test case result ID follows the same pattern at the test case level. Refer to the [documentation on fetching test results at all levels](https://testsigma.com/docs/api/test-results-at-all-levels/) for the response fields at each level.
+
+---
+
 ## **API Specification**
 
 ### **Export a Test Plan Run Report**

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

@@ -41,7 +41,7 @@ Testsigma also integrates seamlessly with tools like Jira, Figma, Xray, and qTes
 >
 > 1. From the **Dashboard**, go to **Settings > Preferences**.
 > 2. Turn on the **Generative AI features** toggle.
-   ![GenAI Features](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/GenAI_Toggle_in_Preferences.png)
+   ![GenAI Features](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Gen_AI_Preferences_Updated.png)
 
 [[info | **NOTE**:]]
 | 

src/pages/docs/auto-healing/enable-the-auto-healing-feature.md

@@ -29,8 +29,8 @@ This article discusses how to enable the auto-healing feature.
 1. Navigate to **Settings > Preferences**.
    ![Preferences](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/auto_heal_1.png)
 
-2. On the **Preferences** page, enable the toggle on the **Auto Healing** widget.
-   ![Auto-healing](https://s3.amazonaws.com/website-static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/auto_heal_2.png)
+2. On the **Preferences** page, enable the toggle on the **Generative AI Autoheal** widget.
+   ![Auto-healing](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/AI_Auto_healing_toggle.png)
 
 Your tests are ready to execute without manual intervention whenever there are changes in the build. The Auto Healing feature will automatically correct the elements.
 

src/pages/docs/desktop-automation/batch-elements.md

@@ -13,69 +13,83 @@ contextual_links:
   name: "Prerequisites"
   url: "#prerequisites"
 - type: link
-  name: "Interactive Demo"
-  url: "#interactive-demo"
+  name: "Steps to Record Elements Using the Batch Tab"
+  url: "#steps-to-record-elements-using-the-batch-tab"
 - type: link
-  name: "Steps to Create Elements Using Batch Element Recorder"
-  url: "#steps-to-create-elements-using-batch-element-recorder"
+  name: "Element Recorder Controls"
+  url: "#element-recorder-controls"
+- type: link
+  name: "Keyboard Shortcuts"
+  url: "#keyboard-shortcuts"
 ---
 
 ---
 
-The Batch Element Recorder lets you capture all UI elements in a desktop application window at once, without manually selecting each element. Once recorded, the elements are displayed in a hierarchical tree structure for easy viewing and locating while creating test cases. This article discusses how to create multiple elements using Batch Elements Recorder. 
+Capture every UI element in a desktop application window at once using the **Batch** tab of the Element Recorder. Recorded elements appear in a hierarchical tree along with their properties and can be used while creating test steps.
 
 ---
 
 > <p id="prerequisites">Prerequisites</p>
 > 
 > Before you begin, ensure that:
-> 1. You have referred to the [documentation on creating projects](https://testsigma.com/docs/projects/overview/).
-> 2. You have referred to the [docuemntation on creating applications](https://testsigma.com/docs/projects/applications/) in Testsigma.
-> 3. You should have the **Testsigma Terminal** installed.
-> 4. The **WinTest Automation** folder must exist in the **Testsigma Agent** directory. 
-> 5. You have a Windows application to test and make sure it’s open on your device. 
+> 1. A Desktop project and an application exist in Testsigma. See [creating projects](https://testsigma.com/docs/projects/overview/) and [creating applications](https://testsigma.com/docs/projects/applications/).
+> 2. **Testsigma Terminal** is installed on your Windows system.
+> 3. The **WinTest Automation** folder exists in the **Testsigma Agent** directory.
+> 4. The Windows application you want to record is open on your device.
 
 ---
 
-## **Interactive Demo**
-
-<div>
-  <script async src="https://js.storylane.io/js/v2/storylane.js"></script>
-  <div class="sl-embed" style="position:relative;padding-bottom:calc(50.57% + 25px);width:100%;height:0;transform:scale(1)">
-    <iframe loading="lazy" class="sl-demo" src="https://app.storylane.io/demo/do1gq6a2hpnl?embed=inline" name="sl-embed" allow="fullscreen" allowfullscreen style="position:absolute;top:0;left:0;width:100%!important;height:100%!important;border:1px solid rgba(63,95,172,0.35);box-shadow: 0px 0px 18px rgba(26, 19, 72, 0.15);border-radius:10px;box-sizing:border-box;"></iframe>
-  </div>
-</div>
-
----
-
-## **Steps to Create Elements Using Batch Element Recorder**
+## **Steps to Record Elements Using the Batch Tab**
 
 1. From the left navigation bar, go to **Create Tests > Elements**.
 
-2. In the Elements list page, click **Record**. 
-
-3. In the **Desktop Element Recorder** dialog, select the **Batch Element Recorder** radio button and click **Launch**.
-
-4. In the **Select Application** window, select an application and click **Start Recording**. 
+2. On the Elements list page, click **Record**.
+   ![Elements](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Desktop_Elements.png)
+3. In the **Select application** window, select the desktop application you want to record against.
 
 [[info | **NOTE**:]]
-| - To record multiple elements in a desktop application, ensure the application is open on your device.
+| Only applications running on your device are listed. Use the search field to filter the list, or click the refresh icon to reload it after opening a new application.
 
-5. The **Batch Element Recorder** automatically captures all elements in the currently open window of the application. 
+4. Click **Start recording**.
+
+5. In the Element Recorder, click the **Batch** tab. The recorder captures every element in the currently open window of the application and lists them in a hierarchical tree.
+   ![Batch Elements](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Desktop_Batch_Elements.png)
 
 [[info | **NOTE**:]]
-| - When you switch windows within the same application, the recorder captures elements from the new window and clears those recorded from the previous one.
+| When you switch windows within the same application, the recorder captures elements from the new window and clears those recorded from the previous one.
 
-6. Once the elements are recorded, select an element name in the recorder and click **Locate Element** to highlight it in the actual application window.
+6. Select an element in the tree to view its details in the **Element properties** panel.
 
-[[info | **NOTE**:]]
-| - You can use the **Expand All** and **Collapse All** buttons at the top of the recorder to quickly view or hide the full hierarchy of recorded elements. 
+7. Click **Locate** to highlight the selected element in the application window.
 
-7. Click **Save all elements & Exit**. 
+8. Click **Save**. The recorded elements are listed under **Create Tests > Elements**.
 
 ---
 
+## **Element Recorder Controls**
 
+| Control | Description |
+|---|---|
+| Selective / Batch | Switches the capture mode. Switch to **Selective** to capture elements one at a time without relaunching the recorder. |
+| Expand all / Collapse all | Expands or collapses the full hierarchy of recorded elements. |
+| Search | Filters the recorded element tree by name. |
+| Element properties | Displays the properties of the selected element, such as Name, Type, Class, AutomationId, and FrameworkId. |
+| Locate | Highlights the selected element in the application window. |
+| Save | Saves the recorded elements to the Elements list. |
 
+The recorder footer displays a running count of captured elements, such as **78 elements recorded**.
 
+[[info | **Additional Information**:]]
+| Batch capture records the full control tree of the window, including containers such as the title bar and tab groups. Use the search field to narrow the tree to the elements you need before saving.
+
+---
 
+## **Keyboard Shortcuts**
+
+| Shortcut | Action |
+|---|---|
+| Alt+R | Record |
+| Alt+S | Stop |
+| Ctrl+Shift+F | Freeze |
+
+---

src/pages/docs/desktop-automation/desktop-projects-and-applications.md

@@ -9,9 +9,6 @@ warning: false
 contextual_links:
 - type: section
   name: "Contents"
-- type: link
-  name: "Interactive Demo"
-  url: "#interactive-demo"
 - type: link
   name: "Steps to Create a Project and an Application"
   url: "#steps-to-create-a-project-and-an-application"
@@ -25,17 +22,6 @@ For more information, refer to the [documentation on creating projects](https://
 
 ---
 
-## **Interactive Demo**
-
-<div>
-  <script async src="https://js.storylane.io/js/v2/storylane.js"></script>
-  <div class="sl-embed" style="position:relative;padding-bottom:calc(50.52% + 25px);width:100%;height:0;transform:scale(1)">
-    <iframe loading="lazy" class="sl-demo" src="https://app.storylane.io/demo/jhwd2o96vx9s?embed=inline" name="sl-embed" allow="fullscreen" allowfullscreen style="position:absolute;top:0;left:0;width:100%!important;height:100%!important;border:1px solid rgba(63,95,172,0.35);box-shadow: 0px 0px 18px rgba(26, 19, 72, 0.15);border-radius:10px;box-sizing:border-box;"></iframe>
-  </div>
-</div>
-
----
-
 ## **Steps to Create a Project and an Application**
 
 1. Navigate to **Project** on the left navigation bar, and click **New Project**.

src/pages/docs/desktop-automation/selective-elements.md

@@ -13,60 +13,84 @@ contextual_links:
   name: "Prerequisites"
   url: "#prerequisites"
 - type: link
-  name: "Steps to Create Elements Using Selective Element Recorder"
-  url: "#steps-to-create-elements-using-selective-element-recorder"
+  name: "Steps to Record Elements Using the Selective Tab"
+  url: "#steps-to-record-elements-using-the-selective-tab"
+- type: link
+  name: "Element Recorder Controls"
+  url: "#element-recorder-controls"
+- type: link
+  name: "Keyboard Shortcuts"
+  url: "#keyboard-shortcuts"
 ---
 
 ---
 
-The Selective Element Recorder lets you capture specific UI elements in a desktop application by selecting one element at a time. Once recorded, the elements are displayed in a hierarchical tree structure for easy viewing and locating while creating test cases. This article explains how to capture individual elements using the Selective Element Recorder.
+Capture UI elements one at a time in a desktop application using the **Selective** tab of the Element Recorder. Recorded elements appear in a hierarchical tree along with their properties and can be used while creating test steps.
 
 ---
 
 > <p id="prerequisites">Prerequisites</p>
 > 
 > Before you begin, ensure that:
-> 1. You have referred to the [documentation on creating projects](https://testsigma.com/docs/projects/overview/).
-> 2. You have referred to the [docuemntation on creating applications](https://testsigma.com/docs/projects/applications/) in Testsigma.
-> 3. You should have the **Testsigma Terminal** installed.
-> 4. The **WinTest Automation** folder must exist in the **Testsigma Agent** directory. 
-> 5. You have a Windows application to test and make sure it’s open on your device. 
+> 1. A Desktop project and an application exist in Testsigma. See [creating projects](https://testsigma.com/docs/projects/overview/) and [creating applications](https://testsigma.com/docs/projects/applications/).
+> 2. **Testsigma Terminal** is installed on your Windows system.
+> 3. The **WinTest Automation** folder exists in the **Testsigma Agent** directory.
+> 4. The Windows application you want to record is open on your device.
 
 ---
 
-## **Steps to Create Elements Using Selective Element Recorder**
-
-1. From the left navigation bar, go to **Create Tests > Elements**. 
+## **Steps to Record Elements Using the Selective Tab**
 
-2. In the Elements list page, click **Record**. 
+1. From the left navigation bar, go to **Create Tests > Elements**.
 
-3. In the **Desktop Element Recorder** dialog box, select the **Selective Element Recorder** radio button and click **Launch**.
+2. On the Elements list page, click **Record**.
+   ![Elements](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Desktop_Elements.png)
 
-4. In the **Select Application** window, select an application and click **Start Recording**. 
+3. In the **Select application** window, select the desktop application you want to record against.
 
 [[info | **NOTE**:]]
-| - To record an element in a desktop application, make sure the application is open on your device.
+| Only applications running on your device are listed. Use the search field to filter the list, or click the refresh icon to reload it after opening a new application.
 
-5. Click the **Record** button in the recorder to start capturing the element. 
+4. Click **Start recording**. The Element Recorder opens on the **Selective** tab, with the application name displayed in the recorder header.
+   ![Selective Elements](https://s3.amazonaws.com/static-docs.testsigma.com/new/projects/applications/Desktop_Selective_Elements.png)
 
-6. Hover over the element in your application until it is highlighted in green, then click on it to capture it.
-
-7. Once the element is recorded, select an element name in the recorder and click **Locate Element** to highlight it in the actual application window.
+5. Hover over an element in the application until it is highlighted in green, then click it to capture it.
 
 [[info | **NOTE**:]]
-| - You can use the **Expand All** and **Collapse All** buttons at the top of the recorder to quickly view or hide the full hierarchy of recorded elements. 
-
-8. Click **Save Element**. 
-
----
+| To capture elements that disappear on hover, such as menus and dropdowns, click **Freeze** or press **Ctrl+Shift+F** to hold the current UI state, then click the element.
 
+6. Select a captured element in the tree to view its details in the **Element properties** panel.
 
+7. Click **Locate** to highlight the selected element in the application window.
 
+8. Click **Save**. The recorded elements are listed under **Create Tests > Elements**.
 
+---
 
+## **Element Recorder Controls**
 
+| Control | Description |
+|---|---|
+| Selective / Batch | Switches the capture mode. Switch to **Batch** to capture every element in the current window without relaunching the recorder. |
+| Pause | Pauses capture. The application stays open and recorded elements are retained. |
+| Stop | Ends the recording session. |
+| Freeze | Holds the current UI state so transient elements such as menus and dropdowns can be captured. |
+| Expand all / Collapse all | Expands or collapses the full hierarchy of recorded elements. |
+| Search | Filters the recorded element tree by name. |
+| Element properties | Displays the properties of the selected element, such as Name, Type, Class, AutomationId, and FrameworkId. |
+| Locate | Highlights the selected element in the application window. |
+| Save | Saves the recorded elements to the Elements list. |
 
+The recorder footer displays a running count of captured elements, such as **2 elements recorded**.
 
+---
 
+## **Keyboard Shortcuts**
 
+| Shortcut | Action |
+|---|---|
+| Alt+R | Record |
+| Alt+S | Stop |
+| Ctrl+Shift+F | Freeze |
 
+---