Merge pull request #1179 from amanchopra1905/stage

docs/hyperexecute-espresso-testing.md

@@ -276,6 +276,7 @@ To generate artifacts for your Espresso tests, add the `artifacts: true`, and `r
 
 ```yaml
 report: true
+
 framework:
   name: "android/espresso"
   args:

docs/hyperexecute-release-notes-2-6-5.md

@@ -0,0 +1,61 @@
+---
+id: hyperexecute-release-notes-2-6-5
+title: Version 2.6.5
+hide_title: false
+sidebar_label: Version 2.6.5
+description: Version 2.6.5
+keywords:
+  - LambdaTest Hyperexecute
+  - LambdaTest Hyperexecute help
+  - LambdaTest Hyperexecute documentation
+  - FAQs
+url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-2-6-5/
+site_name: LambdaTest
+slug: hyperexecute-release-notes-2-6-5/
+---
+
+import NewReleaseTag from '../src/component/newRelease.js';
+import EnhancementTag from '../src/component/enhancementTag';
+import BugFixTag from '../src/component/bugFixTag';
+
+<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-2-6-5/"
+        }]
+      })
+    }}
+></script>
+
+## New Regions Added for HyperExecute Performance Testing
+We are excited to announce the addition of four new regions for performance testing in HyperExecute. These regions enable better coverage, reduced latency, and enhanced testing capabilities for global users.
+
+The new regions are:
+- **Central India** - Pune, Maharashtra
+- **Malaysia** - Southeast Asia (Singapore)
+- **Argentina** - South America (Brazil South)
+- **Mexico** - Mexico Central
+
+> 📕 Visit our [Performance Testing Documentation](https://www.lambdatest.com/support/docs/hyperexecute-run-jmeter-tests/) for step-by-step instructions on configuring your tests and making the most of HyperExecute's enhanced regional coverage.
+
+## Download Reports for XCUI Framework
+Now, you can download the [JUnit XML report](https://www.lambdatest.com/support/docs/junit-xml-report/) for your test runs on the XCUI framework.
+
+To generate reports for your XCUI tests, add the `reports: true` flag in your [HyperExecute YAML](https://www.lambdatest.com/support/docs/hyperexecute-yaml-parameters/) file and pass the `--download-report` flag with the CLI command.
+
+> 📕 Refer to our detailed documentation to [Generate XCUI Reports](/support/docs/hyperexecute-xcui-testing/#step-5-generate-reports-and-artifacts)

docs/hyperexecute-release-notes.md

@@ -46,6 +46,7 @@ HyperExecute is an AI Powered Test Orchestration Cloud Platform, enabling test a
 ### December, 2024
 | Release Number | Release Date |
 |----------------|--------------|
+| [Version 2.6.5](/support/docs/hyperexecute-release-notes-2-6-5) | December 23, 2024|
 | [Version 2.6.2](/support/docs/hyperexecute-release-notes-2-6-2) | December 02, 2024|
 
 ### November, 2024

docs/hyperexecute-run-jmeter-tests.md

@@ -66,7 +66,18 @@ After setting up a Test Plan, now you need to associate your test cases and exec
   - **Total Users :** This indicates the number of users you intend to test for.
   - **Duration (min) :** This specifies the desired duration for the test.
   - **Ramp-up Time (min) :** This specifies the amount of time it should take to reach the peak test load.
-  - **Total Load Distribution :** Configure the regions in which you want to distribute the load testing as per the % of the users.
+  - **Total Load Distribution :** Configure the **regions** in which you want to distribute the load testing as per the % of the users.
+
+:::info
+**Supported Regions :** HyperExecute supports the following regions for performance testing
+- West US 2 (Moses Lake, Washington)
+- East US (Richmond, Virginia)
+- Central India (Pune, Maharashtra)
+- Southeast Asia (Singapore)
+- Brazil South (São Paulo State, Brazil)
+- Mexico Central (Querétaro State, Mexico)
+:::
+
 - Click on the **Run Test** button.
 
 <img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/execute.gif').default} alt="HyperExecute" className="doc_img"/>

docs/hyperexecute-xcui-testing.md

@@ -259,18 +259,20 @@ If you are using the `deviceSelectionStrategy: any`, then in that case all the m
 
 :::
 
-## Step 5: Generate Artifacts
-To generate artifacts for your XCUI tests, add the `artifacts: true` flag in your YAML file:
+## Step 5: Generate Reports and Artifacts
+To generate artifacts for your XCUI tests, add the `artifacts: true` and `report: true` flag in your YAML file:
 
 ```yaml
+report: true
+
 framework:
   name: "ios/xcui"
   args:
     artifacts: true
     ...//
 ```
 
-To download these artifacts in your local machine, you can pass the `--download-artifacts` flag with the CLI command to execute the tests as shown in the next step.
+To download these artifacts in your local machine, you can pass the `--download-artifacts` and `--download-report` flag with the CLI command to execute the tests as shown in the next step.
 
 ## Step 6: Execute your Test Suite
 
@@ -279,14 +281,14 @@ To download these artifacts in your local machine, you can pass the `--download-
 Run the below command in your terminal at the root folder of the project:
 
 ```bash
-./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts
+./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts --download-report
 ```
 
 OR use this command if you have not exported your username and access key in the step 2.
 
 <div className="lambdatest__codeblock">
   <CodeBlock className="language-bash">
-    {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts`}
+    {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts --download-report`}
   </CodeBlock>
 </div>
 

docs/playwright-android-guide.md

@@ -95,36 +95,9 @@ export LT_ACCESS_KEY="YOUR_LAMBDATEST_ACCESS_KEY"
 ## Run Your First Test
 ---
 
-1. Add the below code snippet in your test scripts.
+1. Add the below code snippet in your test scripts to initiate your first Playwright test on LambdaTest.
 
-```js
-(async () => {
-  const capabilities = {
-    "LT:Options": {
-      "platformName": "android",
-      "deviceName": "Pixel 5",
-      "platformVersion": "11",
-      "isRealMobile": true,
-      "build": "Playwright android build",
-      "name": "Playwright android test",
-      'user': process.env.LT_USERNAME,
-      "accessKey": process.env.LT_ACCESS_KEY,
-      "network": true,
-      "video": true,
-      "console": true,
-      "projectName": "New UI",
-    },
-  };
-
-  let device = await _android.connect(
-      `wss://cdp.lambdatest.com/playwright?capabilities=${encodeURIComponent(
-          JSON.stringify(capabilities))}`,
-  );
-  ```
-
-Once you are done with the above-mentioned steps, you can initiate your first Playwright test on LambdaTest.
-
-```js
+```javascript title="lambdatest-setup.js"
 const {_android} = require("playwright");
 const expect = require("chai").expect;
 
@@ -156,6 +129,8 @@ const expect = require("chai").expect;
     await device.shell("am force-stop com.android.chrome");
 
     let context = await device.launchBrowser();
+    // highlight-next-line
+    context.setDefaultTimeout(120000);
     let page = await context.newPage();
 
     await page.goto("https://duckduckgo.com");
@@ -180,6 +155,15 @@ const expect = require("chai").expect;
 })();
 ```
 
+:::tip
+The timeout value specified in the Playwright configuration is not being honored during mobile browser automation tests on real devices, defaulting to 30 seconds, whereas it works correctly on desktop browsers. To resolve the issue, add the following line to the `lambdatest-setup.js` file:
+
+```javascript
+context.setDefaultTimeout(120000);  // Set your desired timeout value.
+```
+:::
+
+
 2. Pass the below command to run the test.
 
 ```

sidebars.js

@@ -859,6 +859,7 @@ module.exports = {
             collapsed: true,
             label: "December, 2024",
             items: [
+              'hyperexecute-release-notes-2-6-5',
               'hyperexecute-release-notes-2-6-2',
             ]
           },