testim integration update

docs/accessibility-update-devtools-extension.md

@@ -43,6 +43,12 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
 
 Keeping your LambdaTest Accessibility DevTools Chrome extension updated ensures you have the latest features, improvements, and security patches. Follow the detailed steps below to update your extension.
 
+<div className="ytframe"> 
+<div className="youtube" data-embed="7CuoCS7dX70" data-loading-attribute="eager">
+  <div className="play-button"></div>
+</div>
+</div>
+
 ## Step-by-Step Guide to Update the LambdaTest Accessibility DevTools Chrome Extension
 
 ### Step 1: Open the Extensions Page

docs/app-automation-on-emulators-simulators.md

@@ -39,6 +39,14 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
     }}
 ></script>
 
+LambdaTest enables developers and testers to automate mobile app testing using cloud-based emulators and simulators. This eliminates the need for physical devices, streamlining the process of validating app functionality across a wide range of configurations. 
+
+<div className="ytframe"> 
+<div className="youtube" data-embed="ZcgYzi60Nmo" data-loading-attribute="eager">
+  <div className="play-button"></div>
+</div>
+</div>
+
 ---
 
 In this documеntation, learn how to run app automated tests on Emulators and Simulators using LambdaTest virtual testing cloud. 

docs/app-testing-on-real-devices.md

@@ -40,6 +40,12 @@ slug: app-testing-on-real-devices/
 
 Real device app testing is the process of testing a mobile application to ensure that their functionality and usability is not comprised when installed across multiple Android and iOS devices. With LambdaTest, you can test mobile applications manually to ensure they perform seamlessly across 3000 + real mobile devices.
 
+<div className="ytframe"> 
+<div className="youtube" data-embed="k-DgcPraWns" data-loading-attribute="eager">
+  <div className="play-button"></div>
+</div>
+</div>
+
 ***
 
 **Step 1:** Login to your LambdaTest account. Go to **App Testing** under **Real Device** from the left sidebar.

docs/browser-testing-with-real-devices.md

@@ -41,7 +41,13 @@ slug: browser-testing-on-real-devices/
 
 Real device browser testing refers to the process of testing web applications and websites on real devices such as smartphones, tablets, and computers to ensure that the user interface and user experience are optimal across various device types, operating systems, and browser combinations. With LambdaTest’s real device cloud, you can test websites and web applications to ensure they perform seamlessly across 3000 + real mobile devices.
 
-Below are the steps to run your first browser test on LambdaTest's Real Device Cloud:
+<div className="ytframe"> 
+<div className="youtube" data-embed="zzjTXzJkLtA" data-loading-attribute="eager">
+  <div className="play-button"></div>
+</div>
+</div>
+
+***
 
 **Step 1:** Login to your LambdaTest account. From the left sidebar, head to Real Device and select **Browser Testing**.
 

docs/getting-started-with-desktop-browser-real-time-testing.md

@@ -44,7 +44,15 @@ slug: getting-started-with-desktop-browser-real-time-testing/
       })
     }}
 ></script>
-Real-Time Desktop Web Browser Testing allows you to test your websites and web applications directly on live desktop browsers. This approach allows developers, testers, and QA professionals to interact with their web applications across various browser environments, operating systems, and versions without the need to configure complex infrastructure on local machines. Whether you want to verify cross-browser compatibility, perform functional testing, or check responsive design, this process provides a seamless way to carry out testing efficiently.
+Real-Time Desktop Web Browser Testing on LambdaTest allows you to test your websites and web applications directly on live desktop browsers. This approach allows developers, testers, and QA professionals to interact with their web applications across various browser environments, operating systems, and versions without the need to configure complex infrastructure on local machines. 
+
+<div className="ytframe"> 
+<div className="youtube" data-embed="a6s9oaBxEBM" data-loading-attribute="eager">
+  <div className="play-button"></div>
+</div>
+</div>
+
+
 
 ## Launch the Virtual Machine
 

docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md

@@ -76,12 +76,15 @@ The various flags that are supported are listed below.
 |-------|------|------------|
 | [analyze](#analyze) | NA | Analyzes the language and environment supported in your project.| 
 | [completion](#completion) | NA | Generates the autocompletion script for HyperExecute for the specified shell. |
+| [serve](#serve) | NA | Starts a server for HyperExecute info APIs |
+| [update](#update) | NA | Update the HyperExecute Binary Version |
 | [--concurrency](#--concurrency) | Numerical | Indicates the number of concurrent sessions on HyperExecute. | 
 | [--config](#--config) | string | Custom location for hyperexecute.yaml. |
+| [--disable-updates](#--disable-updates) | NA | Disable auto update |
 | [--download-artifacts](#--download-artifacts) | NA | Download the artifacts for a job. |
 | [--download-artifacts-path](#--download-artifacts-path) | string | Path of the directory to download artifacts for a job |
 | [--download-artifacts-zip](#--download-artifacts-zip) | NA | Download the artifacts for a job as a zip. |
-| [--download-logs](#--download-logs) | NA | Downloads console logs of your every tests of a job. |
+| [--download-logs](#--download-logs) | NA | Downloads console logs of your every tests of a job. | 
 | [--download-report](#--download-report) | NA | Whether reports have to be downloaded or not. |
 | [--force-clean-artifacts](#--force-clean-artifacts) | NA | Download the updated artifacts of your job. |
 | [-h, --help](#-h---help) | NA | Help for hyperexecute. |
@@ -124,6 +127,24 @@ hyperexecute completion
 
 ***
 
+### `serve`
+This flag starts a server for HyperExecute info APIs.
+
+```bash
+hyperexecute --user USER_NAME --key ACCESS_KEY serve
+```
+
+***
+
+### `update`
+This flag updates the hyperexecute binary version.
+
+```bash
+hyperexecute update
+```
+
+***
+
 ### `--concurrency`
 This flag allows you to define the number of concurrent sessions running on HyperExecute. For more information on concurrency, go to [this page](/support/docs/hyperexecute-auto-split-strategy/).
 ```bash
@@ -139,6 +160,11 @@ This flag allows you to enter a custom location where you can download the Hyper
 ```
 ***
 
+### `--disable-updates`
+This flag allows you to disable the auto updation of your HyperExecute binary.
+
+***
+
 ### `--download-artifacts`
 This flag allows you to download all the test related results that are generated by your testing framework. You can use this key if you want to download the artifacts.
 
@@ -152,6 +178,8 @@ This flag allows you to download all the test related results that are generated
 - For Espresso with private devices HyperExecute can download user generated artefacts.
 :::
 
+***
+
 ### `--download-artifacts-path`
 In case you want the artifacts to be downloaded to a specific directory, please provide the exact path followed by the flag as shown in the example below.
 
@@ -161,6 +189,8 @@ In case you want the artifacts to be downloaded to a specific directory, please
   </CodeBlock>
 </div>
 
+***
+
 ### `--download-artifacts-zip`
 If you want to download the zip file of the artifacts for a job.
 

docs/hyperexecute-testim-integration.md

@@ -116,7 +116,7 @@ testDiscovery:
  mode: static
  command: echo "HYP with Testim"
 
-testRunnerCommand:  testim --token "YOUR_TESTIM_TOKEN" --project "YOUR_PROJECT_NAME" --grid "YOUR_GRID_NAME"
+testRunnerCommand: ./.hyperexecute/snooper --frameWork testim --testimProject YOUR_PROJECT_ID --testimToken YOUR_TESTIM_TOKEN --testimProjectBranch YOUR_BRANCH_NAME
 ```
 
 ## Step 5: Setup the CLI