Merge pull request #1497 from surishubham/main

Merge pull request #1494 from shreybansal-lambdatest/stage

Author: surishubham

docs/desired-capabilities-in-appium.md

@@ -116,6 +116,7 @@ By setting these parameters, QAs can ensure that the Appium server accurately ta
 | geoLocation | TYPE: String <br/>`geoLocation=US`<br/>`geoLocation=FR` | Used to change the geolocation of the device to the location provided. <br/> If this capability is not passed, the device will auto update the Geo Location based on the physical location of the device.|
 | enableImageInjection | TYPE: Boolean<br/> DEFAULT: false <br/>`enableImageInjection: true` | Used to enable the Image Injection for the app. <br/>Must send "media" capability along with this capability.|
 | media | TYPE: STRING <br/>`media: Path to the image`|Used to provide the media to upload the file to the app for Image Injection. If this capability is not passed, then the no media will be sent to the device. <br/>Must send "enableImageInjection" capability along with this capability.|
+| enableBluetooth | TYPE: Boolean<br/> DEFAULT: false <br/>`enableBluetooth: true` | Used to enable the bluetooth functionality during the session.|
 location | TYPE: HashMap <br/> <br/> Python example: <br/> `location: {"lat": "28.6235192", "long": "77.3662948"}` <br/> <br/> For examples in other languages, please head over to [Capability Generator](https://www.lambdatest.com/capabilities-generator/)  | Used to change the GPS Geolocation of the device to the location provided. <br/> If this capability is not passed, the device will auto update the Geo Location based on the physical location of the device. <br/> It needs to be passed in a HashMap structure with `lat` & `long` being passed separately. |
 
 

docs/espresso-supported-capabilities.md

@@ -46,6 +46,8 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
 
 This document provide details about the features and capabilities supported for Espresso Framework on LambdaTest.
 
+> The capabilities listed in this document are also supported for [Virtual Devices](/support/docs/app-automation-on-emulators-simulators/)
+
 | Capability Name | Data Type | Description |
 |------|-----------|-------------|
 | app | String | Enter the app id generated while uploading the app to the platform. Example:`lt://APP123456789123456789` |
@@ -59,11 +61,19 @@ This document provide details about the features and capabilities supported for
 | network.har | Boolean | To generate the network logs in .har format, pass the value as `network.har: true` only works with `network:true` |
 | build | String | To set the Espresso build name. Example: `build: My Espresso Build`. |
 | geoLocation | String | Set the geolocation country code if you want to enable the same in your test. Example - `geoLocation: FR`|
+| gpsLocation | Decimal | The capability should be defined to override the device’s default GPS coordinates and should be provided as a comma-separated string. Example: `"location": {"lat": "-50","long": "150.028333"}`|
+| enableBluetooth | Boolean | Used to enable the bluetooth functionality during the session. Example: `enableBluetooth: true`|
 | tunnel, tunnelName | Boolean | To activate the tunnel mode, pass the value as `tunnel: true` and provide the name of your tunnel as `tunnelName: NewTunnel` |
 | disableAnimation | Boolean | Set this to `true` if you want to disable animations for espresso tests. **Default:** `false` |
 | clearPackageData | Boolean | Set this to `true` if you want to clear the app data after each test has completed running. **Default**: `false` |
 | singleRunnerInvocation | Boolean | Set this to `true` if you want to execute test cases together with a `single test runner invocation`.This can help significantly speed up the test execution time. By default, each test case is invoked separately. **Default:** `false` |
 
+:::note
+Ensure that the latitude is between -90 and 90, and the longitude is between -180 and 180. Otherwise, an error will occur like "Invalid GPS location: Latitude must be between -90 and +90, Longitude must be between -180 and +180."
+:::
+
+
+<!-- | env | Map | This feature allows users to pass and retrieve environment variables (like STAGE, PROD, or DEV) during automated Android tests. That is, users can dynamically switch configurations between environments without changing the test code, enabling seamless testing across multiple setups. Learn more about [Environment Variables](https://www.lambdatest.com/support/docs/espresso-env-variables-settings/) | -->
 :::caution Important
 You can either use **GeoLocation** or **Tunnel** in single execute command. They both are mutually exclusive.
 :::

docs/getting-started-with-flutter-dart-android-automation.md

@@ -283,7 +283,12 @@ The following capabilities are supported:
 7. **deviceLog:** Boolean value to generate device logs. Example: `true`. 
 8. **build:** Set the name of your Flutter test build. Example: `My Flutter Build`.
 9. **autoGrantPermissions:**  Boolean value to automatically grant the required permissions based on the [Android manifest](https://developer.android.com/guide/topics/manifest/manifest-intro) in the app’s **.apk** Example: `true`. 
+10. **gpsLocation:** This capability should be defined to override the device’s default GPS coordinates and should be provided as a comma-separated string. Example: `"location": {"lat": "-50","long": "150.028333"}`.
+11. **enableBluetooth:** This capability is used to enable the bluetooth functionality during the session. Example: `enableBluetooth: true`
 
+:::note
+Ensure that the latitude is between -90 and 90, and the longitude is between -180 and 180. Otherwise, an error will occur like "Invalid GPS location: Latitude must be between -90 and +90, Longitude must be between -180 and +180."
+:::
 
 
 ## Running Tests in Parallel
@@ -351,4 +356,4 @@ curl --location --request POST 'https://mobile-api.lambdatest.com/framework/v1/f
       </span>
     </li>
   </ul>
-</nav>
+</nav>

docs/getting-started-with-flutter-dart-ios-automation.md

@@ -165,7 +165,7 @@ curl --location --request POST "https://mobile-api.lambdatest.com/framework/v1/f
 </TabItem>
 </Tabs>
 
-### Step 4: View Test Execution
+### Step 3: View Test Execution
 
 Once you have run your tests, you can view the test execution along with logs. You will be able to see the test cases passing or failing. You can view the same at [LambdaTest Automation](https://appautomation.lambdatest.com/builds).
 
@@ -183,6 +183,12 @@ The following capabilities are supported:
 8. **tunnel:** Boolean value to run build via Tunnel. Example: `true`.  
 9. **tunnelName:** Name of the tunnel to be used in conjunction with `tunnel` capability.  
 10. **region:** String to device the region from which device will be allocated. Example - `eu`,`us`,`ap`.
+11. **gpsLocation:** This capability should be defined to override the device’s default GPS coordinates and should be provided as a comma-separated string. Example: `"location": {"lat": "-50","long": "150.028333"}`.
+12. **enableBluetooth:** This capability is used to enable the bluetooth functionality during the session. Example: `enableBluetooth: true`
+
+:::note
+Ensure that the latitude is between -90 and 90, and the longitude is between -180 and 180. Otherwise, an error will occur like "Invalid GPS location: Latitude must be between -90 and +90, Longitude must be between -180 and +180."
+:::
 
 
 ## Running Tests in Parallel
@@ -229,4 +235,4 @@ Do note that Flutter builds when run in parallel, result in separate builds bein
       </span>
     </li>
   </ul>
-</nav>
+</nav>

docs/xcui-supported-capibilities.md

@@ -46,6 +46,8 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
 
 This document provide details about the features and capabilities supported for XCUI Framework on LambdaTest.
 
+> The capabilities listed in this document are also supported for [Virtual Devices](/support/docs/app-automation-on-emulators-simulators/)
+
 | Capability Name | Data Type | Description |
 |------|-----------|-------------|
 | app | String | Enter the app id generated while uploading the app to the platform. Example:`lt://APP123456789123456789` |
@@ -57,9 +59,15 @@ This document provide details about the features and capabilities supported for
 | deviceLog | Boolean | To generate the device logs, pass the value as `deviceLog: true` |
 | network | String | To generate the network logs, pass the value as `network: true`. |
 | build | String | To set the Espresso build name. Example: `build: My Espresso Build`. |
-| geoLocation | String | Set the geolocation country code if you want to enable the same in your test. Example - `geoLocation: FR`|
+| geoLocation | String | Set the geolocation country code if you want to enable the same in your test. Example: `geoLocation: FR`|
+| gpsLocation | Decimal | The capability should be defined to override the device’s default GPS coordinates and should be provided as a comma-separated string. Example: `"location": {"lat": "-50","long": "150.028333"}`.|
 | tunnel, tunnelName | Boolean | To activate the tunnel mode, pass the value as `tunnel: true` and provide the name of your tunnel as `tunnelName: NewTunnel` |
-| resignApp | Boolean | Set this to `false` if you want to to prevent the apps from being re-signed. The app should be built for enterprise distribution. |
+| enableBluetooth | Boolean | Used to enable the bluetooth functionality during the session. Example: `enableBluetooth: true`|
+| resignApp <br /> <br />Not supported in **Virtual Devices** | Boolean | Set this to `false` if you want to to prevent the apps from being re-signed. The app should be built for enterprise distribution. |
+
+:::note
+Ensure that the latitude is between -90 and 90, and the longitude is between -180 and 180. Otherwise, an error will occur like "Invalid GPS location: Latitude must be between -90 and +90, Longitude must be between -180 and +180."
+:::
 
 :::caution Important
 You can either use **GeoLocation** or **Tunnel** in single execute command. They both are mutually exclusive.