Merge pull request #2189 from Ishavyas9/main

Ishavyas9 · web-flow · commit 31d701819b37 · 2025-10-15T14:07:54.000+05:30
MITM Proxy,hyp hackathon items,Release Notes HYP
diff --git a/assets/images/hyperexecute/release-notes/logs-categorization.png b/assets/images/hyperexecute/release-notes/logs-categorization.png
diff --git a/docs/hyperexecute-how-to-configure-tunnel.md b/docs/hyperexecute-how-to-configure-tunnel.md
@@ -1,7 +1,7 @@
 ---
 id: hyperexecute-how-to-configure-tunnel
-title: How to Configure Tunnel with HyperExecute
-hide_title: true
+title: Tunnel Configuration in HyperExecute
+hide_title: false
 sidebar_label: How to Configure Tunnel with HyperExecute
 description: Learn to set up a Tunnel with HyperExecute effortlessly with our straightforward guide, simplifying the configuration process for you!
 keywords:
@@ -37,37 +37,36 @@ slug: hyperexecute-how-to-configure-tunnel/
       })
     }}
 ></script>
+You can configure a secure tunnel in HyperExecute to test applications that are:
 
-# Tunnel Configuration
+- Hosted locally on your system, or
+- Behind a private network/firewall.
 
-***
+## Prerequisites
+- HyperExecute YAML file -> HyperExecute supports multiple ways of setting up tunnels directly from your YAML configuration. You can use any version of [YAML](https://www.lambdatest.com/support/docs/hyperexecute-yaml-parameters/) to pass the Tunnel parameters. 
+- [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) to trigger your tests.
 
-## How to Configure Tunnel with HyperExecute?
-
-> You can use any version of YAML to pass the Tunnel Parameters.
-
-If you want to use a tunnel with HyperExecute, you will have to download the [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) and configure it.
-
-There are 3 ways to use a tunnel in HyperExecute:
+## Ways to Use Tunnel in HyperExecute
+There are 3 main ways to use a tunnel in HyperExecute:
 
 ### 1. Simple `tunnel` Connection
+Enable tunnel directly by setting the `tunnel` flag to `true` in your HyperExecute YAML file. The HyperExecute CLI will launch a tunnel as sub process for accessing your applications which are locally hosted or behind a firewall. 
 
-Set the `tunnel` flag to `true` to enable it. The cli will launch a tunnel as sub process for accessing your applications which are locally hosted or behind a firewall. 
-
-```bash
+```yaml title="hyperexecute.yaml"
 tunnel: true
 ```
+> Recommended if you want to quickly enable tunnel access for locally hosted apps.
 
 ### 2. Using Existing `tunnel`
+If you already have a running tunnel, you can reuse it by specifying its name to access your applications which are locally hosted or behind a firewall.
 
-Specify the list of already running tunnel names which you want to use for accessing your applications which are locally hosted or behind a firewall.
-
-```bash
+```yaml title="hyperexecute.yaml"
 tunnelNames: ["lambdatest_tunnel"]
 ```
 
-### 3. Advanced `tunnel` Configurations
+> Useful when running multiple jobs and you don’t want to spawn new tunnels each time.
 
+### 3. Advanced `tunnel` Configurations
 These are the parameters you can use to configure your [tunnel](/support/docs/deep-dive-into-hyperexecute-yaml/#tunnel) settings when running it.
 
 | Options | Type | Description |
@@ -79,7 +78,11 @@ These are the parameters you can use to configure your [tunnel](/support/docs/de
 |`systemProxy`| Boolean | Should the tunnel be OS system wide? Default false. |
 |`checkTunnelOnFailure`| Boolean | Check tunnel on failure adds a check on our system to check the tunnel connection if a test fails and the tunnel is set to true. This option will retry the test 2 times if tunnel connection is flaky. |
 
-```bash
+> HyperExecute now supports tunnel capabilities for [Maestro](https://www.lambdatest.com/support/docs/hyperexecute-maestro-testing/) tests running on both virtual devices and real devices using the Raw Framework configuration.
+
+```yaml title="hyperexecute.yaml"
+tunnel: true
+
 tunnelOpts:
   global: true
 ```
diff --git a/docs/hyperexecute-maestro-testing.md b/docs/hyperexecute-maestro-testing.md
@@ -135,6 +135,8 @@ https://github.com/LambdaTest/hyperexecute-maestro-sample-test/blob/main/ios-sim
 
 </Tabs>
 
+> HyperExecute now supports [tunnel capabilities](/support/docs/hyperexecute-how-to-configure-tunnel/) for Maestro tests running on both virtual devices and real devices using the Raw Framework configuration.
+
 ## Step 5: Generate JUnit XML Report
 1. Update the `runTest.sh` file to include the `--format junit` flag in the maestro test command:
 
diff --git a/docs/hyperexecute-release-notes-3-0-5.md b/docs/hyperexecute-release-notes-3-0-5.md
@@ -0,0 +1,51 @@
+---
+id: hyperexecute-release-notes-3-0-5
+title: Version 3.0.5
+hide_title: false
+sidebar_label: Version 3.0.5
+description: Version 3.0.5
+keywords:
+  - LambdaTest Hyperexecute
+  - LambdaTest Hyperexecute help
+  - LambdaTest Hyperexecute documentation
+  - FAQs
+url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-5/
+site_name: LambdaTest
+slug: hyperexecute-release-notes-3-0-5/
+---
+
+import NewReleaseTag from '../src/component/newRelease.js';
+import EnhancementTag from '../src/component/enhancementTag';
+import BugFixTag from '../src/component/bugFixTag';
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Version",
+          "item": "https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-5/"
+        }]
+      })
+    }}
+></script>
+## Feature: syncStart
+HyperExecute now supports the `syncStart` directive in the job YAML. When enabled, all VMs in `autosplit` or `matrix` mode start their tasks simultaneously after allocation—ideal for benchmarking or comparative test runs.
+
+If some VMs are not ready within 15 minutes, the job starts with the available ones.
+
+> **NOTE :** For detailed usage and examples, refer to the detailed [HyperExecute documentation](/support/docs/deep-dive-into-hyperexecute-yaml/#syncstart).
diff --git a/docs/hyperexecute-release-notes-3-0-6.md b/docs/hyperexecute-release-notes-3-0-6.md
@@ -0,0 +1,51 @@
+---
+id: hyperexecute-release-notes-3-0-6
+title: Version 3.0.6
+hide_title: false
+sidebar_label: Version 3.0.6
+description: Version 3.0.6
+keywords:
+  - LambdaTest Hyperexecute
+  - LambdaTest Hyperexecute help
+  - LambdaTest Hyperexecute documentation
+  - FAQs
+url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-6/
+site_name: LambdaTest
+slug: hyperexecute-release-notes-3-0-6/
+---
+
+import NewReleaseTag from '../src/component/newRelease.js';
+import EnhancementTag from '../src/component/enhancementTag';
+import BugFixTag from '../src/component/bugFixTag';
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Version",
+          "item": "https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-6/"
+        }]
+      })
+    }}
+></script>
+## Feature: HyperExecute Logs Categorization
+Debugging large test executions often generates extensive logs, making it difficult to identify key issues. The new **Logs Categorization** feature enhances log readability by automatically highlighting and grouping critical entries.
+
+HyperExecute categorizes logs into Errors and Warnings using intelligent pattern detection based on regular expressions (regex). This will help you quickly locate and review the most relevant log lines during test analysis.
+
+<img loading="lazy" src={require('../assets/images/hyperexecute/release-notes/logs-categorization.png').default} alt="Image"  className="doc_img"/> 
diff --git a/docs/hyperexecute-yaml-parameters.md b/docs/hyperexecute-yaml-parameters.md
@@ -165,7 +165,7 @@ The **HyperExecute YAML** file serves as the foundational component for test exe
 | [project](/support/docs/deep-dive-into-hyperexecute-yaml/#project) | String | Segregate data at a project/repo level |
 | [slackChannel](/support/docs/deep-dive-into-hyperexecute-yaml/#slackchannel) | String | Allows you to receive notifications of your Job updates directly in your preferred Slack channel. |
 | [afterEachScenario](/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) | List of Strings | Allows you to trigger your define tasks after each test scenario. |
-| [syncStart](/support/docs/deep-dive-into-hyperexecute-yaml/#execution) | Map | Ensures all VMs are ready before starting parallel tasks. |
+| [syncStart](/support/docs/deep-dive-into-hyperexecute-yaml/#syncstart) | Map | Ensures all VMs are ready before starting parallel tasks.|
 
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">
diff --git a/docs/hyperexecute-yaml-version0.2.md b/docs/hyperexecute-yaml-version0.2.md
@@ -67,6 +67,7 @@ The ```framework``` field in Hyperexecute YAML Version 0.2 allows you to configu
 | [artifacts](#artifacts) | Boolean | No | Specifies whether to generate artifacts or not |
 | [language](#language) | String | No | Specifies the device’s system language for the test session. This determines the language in which your app’s UI and strings will be displayed. |
 | [locale](#locale) | String | No | Defines the regional format settings such as date, time, currency, and number conventions. |
+| [mitmProxy](#mitmProxy) | Boolean | No | Capture network logs directly from emulator sessions using MITM. |
 
 ### `name`
 Specifies the testing framework used in your repository.
@@ -204,6 +205,17 @@ framework:
 ```
 
 
+### `mitmProxy`
+
+You can now capture network logs directly from emulator sessions using MITM. This enhancement enables deeper debugging of API calls, request/response payloads, and overall network traffic during test execution.
+
+```yaml
+framework:
+  args:
+    mitmProxy: true
+```
+
+
 ## Sample Yaml Version 0.2
 
 ```yaml
@@ -231,6 +243,7 @@ framework:
     region: ap
     language: es
     locale: es
+    mitmProxy: true
 
 retryOnFailure: true
 maxRetries: 1
diff --git a/docs/playwright-real-device-on-hyperexecute.md b/docs/playwright-real-device-on-hyperexecute.md
diff --git a/sidebars.js b/sidebars.js
