Aman's PR 1084, 85, 88,92,95

docs/app-auto-network-throttling.md

@@ -1,7 +1,7 @@
 ---
 id: app-auto-network-throttling
 title: Network Throttling 
-hide_title: true
+hide_title: false
 sidebar_label: Network Throttling
 description: Now validate your mobile applications over low latency networks (2G/3G/LTE) or in offline mode with varying upload and download speeds. LambdaTest empowers you to simulate these mobile network conditions through its desired capabilities, ensuring comprehensive testing of your mobile applications.
 keywords:
@@ -50,25 +50,11 @@ import TabItem from '@theme/TabItem';
       })
     }}
 ></script>
-
-# Network Throttling
-
-***
 In Appium testing, assessing your app's performance under diverse network conditions (2G/3G/LTE) and offline scenarios, is crucial. Fluctuating upload and download speeds can significantly impact your app's behavior across different devices.
 
 LambdaTest simplifies testing by enabling simulation of diverse network conditions. Whether starting with defaults or custom profiles, these features replicate real-world scenarios, proving invaluable for Appium tests. The device maintains uninterrupted internet connectivity throughout, ensuring a reliable testing experience for your mobile applications.
 
-## Objectives
-----
-
-By the end of this guide, you will learn how to:
-- Initialize a test session with predefined network profiles.
-- Dynamically change network profiles during test execution using LambdaHooks.
-- Define and implement custom network profiles.
-- Reset the network profile to default settings.
-
 ## Workflow
-----
 ### Initialization
 
 - **Capability:** Initiate a test session with predefined network profiles using the `networkProfile` capability. Example:
@@ -137,12 +123,13 @@ To utilize the **networkProfile** capability, ensure that you include `network:
 
 #### iOS
 
-
 - **LambdaHook:** You can also switch to offline mode during the test execution with the following command:
     ```python
     driver.execute_script("updateNetworkProfile=offline")
     ```
 
+## Toggle Offline/Online Mode via API
+
 - For both iOS and android devices you can use the offline/online mode API as well within the running test session:
 
     ```bash
@@ -152,7 +139,6 @@ To utilize the **networkProfile** capability, ensure that you include `network:
     --data '{"mode": "offline"}'
     ```
 
-
 :::note
 - **Network throttling** results may vary sometimes based on multiple factors including network conditions and device performance.
 

docs/katalon-integration-with-hyperexecute.md

@@ -58,7 +58,7 @@ It also comes with a built-in interface for codeless automation testing and vali
 
 -   Ensure that you have integrated Katalon Studio with LambdaTest. Follow the steps on this [page](https://www.lambdatest.com/support/docs/katalon-integration-with-lambdatest/) to do so.
 
--   Ensure that you have the necessary licenses required to use Katalon Studio. You need the [Katalon Runtime License](https://docs.katalon.com/docs/legacy/products-and-licenses/katalon-studio-enterprise-and-runtime-engine-licenses/katalon-runtime-engine-floating-license) to integrate Katalon with HyperExecute. To learn more about these licenses, read this [page](https://docs.katalon.com/docs/legacy/products-and-licenses/katalon-studio-enterprise-and-runtime-engine-licenses/license-overview).
+-   Ensure that you have the necessary licenses required to use Katalon Studio. You need the Katalon Runtime License to integrate Katalon with HyperExecute.
 
 ## Integrating Katalon Studio with HyperExecute
 
@@ -80,36 +80,38 @@ It also comes with a built-in interface for codeless automation testing and vali
 
 4. Create the hyperexecute.yaml file in the root directory of your Katalon project with the given parameters:
 
-```yaml
-version: 0.1
-globalTimeout: 90
-testSuiteTimeout: 90
-testSuiteStep: 90
-
-autosplit: true
-
-runson: win
-
-tunnel: true
-tunnelOpts:
-  global: true
-concurrency: 2
-
-pre: 
-  - pip install requests # To install pip request
-  - python installer.py # To install the certs in the Machine 
-runtime: katalon
-
-testDiscovery:
-  type: raw
-  mode: dynamic
-  command: grep -lr 'testSuiteGuid' */*.ts | sed 's/:.*//' | sed 's/.ts//g'
+  ```yaml
+  version: 0.1
+  globalTimeout: 90
+  testSuiteTimeout: 90
+  testSuiteStep: 90
+
+  autosplit: true
+
+  runson: win
+
+  tunnel: true
+  tunnelOpts:
+    global: true
 
-testRunnerCommand:  katalonc `-noSplash `-runMode=console `-projectPath="G:\foreman\Hyperexecute_Sample\Hyperexecute_Sample.prj" `-retry=0 `-testSuitePath="$test" `-browserType="firefox" `-executionProfile="default" `-apiKey="aaa9402b-6a2e-4621-a4c3-05fe356f5aad" `-`-config `-webui.autoUpdateDrivers=true
+  concurrency: 2
+
+  pre: 
+    - pip install requests # To install pip request
+    - python installer.py # To install the certs in the Machine 
 
-retryOnFailure: false
-maxRetries: 1
-```
+  runtime: katalon
+
+  testDiscovery:
+    type: raw
+    mode: dynamic
+    command: grep -lr 'testSuiteGuid' */*.ts | sed 's/:.*//' | sed 's/.ts//g'
+
+  testRunnerCommand:  katalonc `-noSplash `-runMode=console `-projectPath="G:\foreman\Hyperexecute_Sample\Hyperexecute_Sample.prj" `-retry=0 `-testSuitePath="$test" `-browserType="firefox" `-executionProfile="default" `-apiKey="aaa9402b-6a2e-4621-a4c3-05fe356f5aad" `-`-config `-webui.autoUpdateDrivers=true
+
+  retryOnFailure: false
+  maxRetries: 1
+  ```
 
 Paste the command that you generated from the Katalon UI to fill the **testRunnerCommand** field in the _hyperexecute.yaml_ file.
 

docs/private-device-allocation-to-teams.md

@@ -0,0 +1,112 @@
+---
+id: private-device-allocation-to-teams
+title: Private Device Allocation to Teams
+hide_title: false
+sidebar_label: Private Device Allocation to Teams
+description: Learn real device app testing with LambdaTest across Android and iOS devices. Start testing effortlessly today!
+keywords:
+- private device
+- private decive allocation to teams
+- real device
+- virtual device
+url: https://www.lambdatest.com/support/docs/private-device-allocation-to-teams/
+site_name: LambdaTest
+slug: private-device-allocation-to-teams/
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "LambdaTest",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Private Device Allocation to Teams",
+          "item": "https://www.lambdatest.com/support/docs/private-device-allocation-to-teams/"
+        }]
+      })
+    }}
+></script>
+The Teams feature for Private Cloud Devices enables organization admins to divide and allocate private cloud devices among teams within their organization which ensures effective resource management. Team members then gain exclusive access to the allocated devices, ensuring efficient and secure testing workflows.
+
+> To enable it for your organization, please contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
+
+## Steps to Allocate Devices to Teams
+
+> Only the organization's Admins have the authority to allocate or deallocate devices.
+
+### Step 1:  Create or Select a Team
+- Go to the Teams section under the Organization Settings
+- Create your [Organization](/support/docs/team-management/#create-an-organization) 
+- Then, create your [Team](/support/docs/team-management/#create-your-first-team) and assign members by selecting users from your organization.
+
+### Step 2: Allocate Devices to the Team
+In the **Private Cloud Devices** tab section, distribute your devices amongst your teams for restricted access via:
+
+<Tabs className="docs__val">
+
+<TabItem value="bulk" label="Bulk Distribute" default>
+    - Click on the **Bulk Distribute** button and select all the devices that you want to allocate to the teams.
+    - Click on the **Distribute** button. In the popup, choose the teams from the dropdown list.
+    - Click on the **Allocate** button.
+The devices will now appear in the selected team’s device pool, accessible only to its members.
+
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/teams/bulk-distribute.gif').default} alt="Image" className="doc_img img_center"/>
+
+</TabItem>
+
+<TabItem value="single" label="Uni Distribute" default>
+    - Click on the **Allocate** button from the right side of your desired device.
+    - In the popup, choose the teams from the dropdown list.
+    - Click on the **Allocate** button.
+The selected device will now appear in the team’s device pool, accessible only to its members.
+
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/teams/uni-distribute.gif').default} alt="Image" className="doc_img img_center"/>
+</TabItem>
+
+</Tabs>
+
+> You can also see tags of all those teams to which those devices are allocated.
+
+## Deallocate any Device from Teams
+- Click on the **Deallocate** button from the right side of your desired device.
+
+The selected device will no longer appear in all those allocated team’s device pool.
+
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/teams/deallocate-device.gif').default} alt="Image" className="doc_img img_center"/>
+
+## Edit Allocation of any Device
+To edit allocation of any device, or simply if you want to add/remove any team allocation for any particular device then:
+
+- Click on the **Edit Allocation** button from the right side of your desired device.
+- Select or Deselect your required teams.
+- Click on the **Allocate** button.
+
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/teams/edit-allocation.gif').default} alt="Image" className="doc_img img_center"/>
+
+:::info
+A device in a busy state will not be allocated or deallocated.
+:::
+
+## Filter your Devices
+In the topbar, you have plenty of options to filter your devices based on:
+
+- You can select from the drop down whether you want to see **All Devices**, **Allocated Devices**, or all the **Available Devices** in the table.
+- You can also search for a particular device based on the **device name**, or its **UDID**.
+- **OS :** Select which OS devices you want to allocate or deallocate.
+- **Teams :** Select from which team you want to filter your device and perform allocation or deallocation of devices.
+
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/teams/filters.png').default} alt="Image" className="doc_img img_center"/>

docs/public-cloud-vs-private-cloud.md

@@ -1,7 +1,7 @@
 ---
 id: public-cloud-vs-private-cloud
 title: Public Cloud VS Private Cloud
-hide_title: true
+hide_title: false
 sidebar_label: Public Cloud VS Private Cloud
 description: Discover how LambdaTest's private real device cloud ensures seamless app and website functionality across devices with tailored, robust testing solutions for accuracy and flexibility.
 keywords:
@@ -38,22 +38,18 @@ slug: public-cloud-vs-private-cloud/
       })
     }}
 ></script>
-
-# Public Cloud vs Private Cloud
-***
 In mobile app development, thorough testing on real devices is essential for performance and seamless user experience. Platforms like Public and Private Device Clouds offer access to a variety of real devices for testing, each with differences in accessibility, security, and features. Understanding these nuances is crucial for organizations to choose the right option.
 
 Our detailed document compares Public Device Cloud and Private Device Cloud, focusing on their benefits for real device testing. It considers factors such as device access, session duration, settings control, and testing capabilities allowing organizations to make informed decisions about their testing strategies based on their needs and goals.
 
 <img loading="lazy" src={require('../assets/images/real-device-browser-testing/private-cloud-vs-public-cloud.webp').default} alt="add" width="1346" height="647" className="doc_img"/>
 
 ## Why Choose Private Cloud
-***
 
 Here is the detailed comparison of Public Cloud and Private Cloud:
 
 | Features | Public Device Cloud | Private Device Cloud |
-| -------- | ------- | ------ |
+| -------- | ------------------- | -------------------- |
 | Device Access | Accessible by only a single user during session, but shared for different test sessions.| Only accessible by the specific organization and no access to anyone else. | 
 | Session Duration | Maximum session duration is 6 hours.| Maximum session duration is 12 hours.|     
 | Session Retention  | Devices undergo a factory reset after each session.| Users have the option to retain the session or reset as per their need. |

docs/select-pre-installed-apps.md

@@ -0,0 +1,77 @@
+---
+id: select-pre-installed-apps
+title: Select Pre-Installed App in Session
+hide_title: false
+sidebar_label: Select Pre-Installed Apps
+description: Learn real device app testing with LambdaTest across Android and iOS devices. Start testing effortlessly today!
+keywords:
+- select pre installed apps
+- select pre installed apps in session
+url: https://www.lambdatest.com/support/docs/select-pre-installed-apps/
+site_name: LambdaTest
+slug: select-pre-installed-apps/
+---
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "LambdaTest",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Select Pre-Installed App in Session",
+          "item": "https://www.lambdatest.com/support/docs/select-pre-installed-apps/"
+        }]
+      })
+    }}
+></script>
+
+LambdaTest empowers developers with a comprehensive testing environment, enabling thorough examination of mobile applications and websites across real devices and browsers. One standout feature is the ability to start testing sessions with pre-installed applications, enhancing efficiency, and reducing test start time,  in **private cloud** setups where data retention and reusability are paramount.
+
+Let's delve into the streamlined steps to initiate a testing session with pre-installed applications:
+
+**Step 1.** Login to your LambdaTest account. Go to **App Testing** under **Real Device** from the left sidebar. 
+
+**Step 2.** Enable the toggle to enter into your **Private Cloud**.
+
+**Step 3.** Select your preferred operating system version from the private device pool.
+
+<img loading="lazy" src={require('../assets/images/mobile-app-testing/os-version-from-private-device-pool.webp').default} alt="Real "  className="doc_img" width="1366" height="629"/>
+
+**Step 4.** Within the **App Testing** section, locate and select the option to start a session with pre-installed applications.
+
+**Step 5.** Upon initiating the session, gain instant access to the pre-installed applications on the designated device. This seamless integration accelerates testing scenarios, significantly reducing start time.
+
+By adhering to the above steps, you can seamlessly commence testing sessions with pre-installed applications on LambdaTest. This feature not only expedites the testing process but also enhances efficiency, making it particularly advantageous for private cloud environments. With data retained within the private cloud devices, LambdaTest ensures enhanced flexibility and productivity in testing workflows.
+
+> **Note:** To access the pre-installed apps, you need to have a private cloud plan.
+
+<nav aria-label="breadcrumbs">
+  <ul className="breadcrumbs">
+    <li className="breadcrumbs__item">
+      <a className="breadcrumbs__link" href="https://www.lambdatest.com">
+        Home
+      </a>
+    </li>
+    <li className="breadcrumbs__item">
+      <a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com/support/docs/">
+        Support
+      </a>
+    </li>
+    <li className="breadcrumbs__item breadcrumbs__item--active">
+      <span className="breadcrumbs__link">
+        Real Device App Testing
+      </span>
+    </li>
+  </ul>
+</nav>

sidebars.js

@@ -1800,9 +1800,7 @@ module.exports = {
         type: "category",
         collapsed: true,
         label: "Private Cloud",
-        items: [
-          "public-cloud-vs-private-cloud",
-        ],
+        items: ["public-cloud-vs-private-cloud", "select-pre-installed-apps", "private-device-allocation-to-teams"],
       },
     ],
   ],