Updated documentation

docs/appium-lambdaHooks.md

@@ -158,8 +158,7 @@ Any command logs executed between `lambda-testCase-start` and `lambda-testCase-e
 
 You can also filter the command logs based on these labels.A screenshot has been provided below, demonstrating the use of labels and how to filter command logs based on them.
 
-<img loading="lazy" src={require('../assets/images/appium-lambdaHooks/02.webp').default} alt="Test Case Filter" width="1200" height="550" className="doc_img"/>
-
+![Test Cases](../assets/images/real-device-app-testing/Test-Cases.png)
 
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">
@@ -179,4 +178,37 @@ You can also filter the command logs based on these labels.A screenshot has been
       </span>
     </li>
   </ul>
-</nav>
+</nav>
+
+---
+
+## Command Annotations 
+
+Command Annotations allow you to add metadata and debugging information to your test scripts. They work similarly to LambdaHooks by providing structured logs on the **LambdaTest Automation Dashboard**, making it easier to track test execution, debug failures, and navigate specific test sections.
+
+![Command Annotation](../assets/images/real-device-app-testing/command-annotation.png)
+
+### Using Command Annotations
+
+#### Annotation Start
+```java
+driver.execute_script("lambdatest_executor: {\"action\": \"stepcontext\", \"arguments\": {\"data\": \"youtube\", \"level\": \"debug\"}}");
+```
+
+**Arguments:**
+
+| Argument | Description |
+|----------|-------------|
+| `data` | String value representing the information you want to log. |
+| `level` | Log severity level. Acceptable values: `info` (default), `debug`, `warn`, `error`. |
+
+#### Annotation End
+To close the executor at the end of your script, pass `data` as an empty string:
+
+```java
+driver.execute_script("lambdatest_executor: {\"action\": \"stepcontext\", \"arguments\": {\"data\": \"\"}}");
+```
+
+:::info
+**Mutual exclusivity:** Test case and Command Annotations cannot be used together in the same script. You can only use **one** of them per session.
+:::

docs/apple-pay-auto.md

@@ -54,8 +54,7 @@ Currently, the Device Passcode feature in App Automation is enabled on the follo
 | Capability                  | Type       | Default | Required / Optional | Description                                                                                 |
 |----------------------------|------------|---------|---------------------|---------------------------------------------------------------------------------------------|
 | **applePay**                | Boolean    | true    | Mandatory           | Enables Apple Pay provisioning including Wallet, Sandbox card, AssistiveTouch, and Passcode on supported real iOS devices. |
-| **applePayCardType**        | Array      | None    | Optional           | Specify preferred payment networks. Currently, you can choose from four supported cards: ["American Express", "Visa", "MasterCard", "Discover Global Network"].
- |
+| **applePayCardType**        | Array      | None    | Optional           | Specify preferred payment networks. Currently, you can choose from four supported cards: ["American Express", "Visa", "MasterCard", "Discover Global Network"].|
 
 ---
 

docs/espresso-supported-capabilities.md

@@ -68,6 +68,7 @@ This document provide details about the features and capabilities supported for
 | 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` |
 | testRemarks <br /> <br /> | Boolean | Set to `true` to surface failure remarks at the top of the dashboard when a test fails. Has no effect on passing tests. **Default**: `false`. |
+| retries <br /> <br /> | Integer |Defines the number of times a test should automatically retry if it fails. Maximum allowed value: 5.|
 
 :::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."

docs/install-apps-from-firebase.md

@@ -79,7 +79,7 @@ Login to your LambdaTest account. Visit **Real Device** from the left panel and
 When you click on Add Project, you can integrate your Firebase account with LambdaTest either by uploading a **config file** or connecting **using credentials**. You should have these credentials from the prerequisite step.
 
 **Upload a Config file -**  
-<img loading="lazy" src={require('../assets/images/mobile-app-testing/firebase/2photo.png').default} alt="Real "  className="doc_img" width="1366" height="629"/>
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/firebase-application-upload-steps.png').default} alt="Real "  className="doc_img" width="1366" height="629"/>
 
 **Connect with credentials -** 
 <img loading="lazy" src={require('../assets/images/mobile-app-testing/firebase/Animeshrox.png').default} alt="Real "  className="doc_img" width="1366" height="629"/>

docs/xcui-supported-capibilities.md

@@ -65,6 +65,7 @@ This document provide details about the features and capabilities supported for
 | 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. |
 | testRemarks <br /> <br />| Boolean | Set to `true` to surface failure remarks at the top of the dashboard when a test fails. Has no effect on passing tests. **Default**: `false`. |
+| retries <br /> <br /> | Integer |Defines the number of times a test should automatically retry if it fails. Maximum allowed value: 5.|
 
 :::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."