Fixed issues with icon removal, copyright notice, and license identifier.

- Removed icons as per requirement.
- Updated copyright notice to reflect correct ownership and licensing.
- Moved license identifier to the top of the file for clarity.
- Added proper dependency checks to ensure smooth execution.
- Updated steps to push required scripts to target.
- Fixed Shell Check in Bluetooth/run.sh.

Signed-off-by: Anil Yadav <[email protected]>

Author: qcom-anilyada

Runner/suites/Connectivity/Bluetooth/README.md

@@ -1,21 +1,33 @@
+Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+SPDX-License-Identifier: BSD-3-Clause-Clear
+
 # Bluetooth Validation Test
 
-## 📌 Overview
+## Overview
 
 This test case validates the basic functionality of the Bluetooth controller on the device. It checks for:
 
 - Presence of `bluetoothctl`
 - Running status of `bluetoothd`
 - Power state toggling of the Bluetooth controller
 
+## Usage
 
+Instructions:
 
-## How to Run
+1. Copy repo to Target Device: Use scp to transfer the scripts from the host to the target device. The scripts should be copied to any directory on the target device.
+2. Verify Transfer: Ensure that the repo have been successfully copied to any directory on the target device.
+3. Run Scripts: Navigate to the directory where these files are copied on the target device and execute the scripts as needed.
 
-```sh
-source init_env
-cd suites/Connectivity/Bluetooth
-./run.sh
+Run a Connectivity Bluetooth test using:
+---
+#### Quick Example
+```
+git clone <this-repo>
+cd <this-repo>
+scp -r common Runner user@target_device_ip:<Path in device>
+ssh user@target_device_ip
+cd <Path in device>/Runner && ./run-test.sh Bluetooth
 ```
 
 ## Prerequisites
@@ -26,13 +38,13 @@ cd suites/Connectivity/Bluetooth
 ## Result Format
 
 Test result will be saved in Bluetooth.res as:  
-✅ Pass Criteria  
+#### Pass Criteria  
 - bluetoothctl is available
 - bluetoothd is running
 - Power on command returns success
 - Bluetooth controller powered on successfully. – if all validations pass  
 <!-- -->
-❌ Fail Criteria  
+#### Fail Criteria  
 - bluetoothctl not found
 - bluetoothd not running
 - Power on command fails
@@ -44,7 +56,3 @@ A .res file is generated in the same directory:
 
 `PASS Bluetooth`  OR   `FAIL Bluetooth`
 
-## License
-
-SPDX-License-Identifier: BSD-3-Clause-Clear  
-(C) Qualcomm Technologies, Inc. and/or its subsidiaries.

Runner/suites/Connectivity/Bluetooth/run.sh

@@ -53,10 +53,25 @@ if ! command -v bluetoothctl >/dev/null 2>&1; then
 fi
 
 # Check if bluetoothd is running
-if ! pgrep bluetoothd >/dev/null; then
-    log_fail "bluetoothd is not running. Please start the Bluetooth daemon."
+MAX_RETRIES=3
+RETRY_DELAY=10 # seconds
+retry=0
+
+while [ "$retry" -lt "$MAX_RETRIES" ]; do
+    if pgrep bluetoothd >/dev/null; then
+        break
+    fi
+    log_info "Bluetooth daemon not found, retrying in ${RETRY_DELAY} seconds..."
+    sleep "$RETRY_DELAY"
+    retry=$((retry + 1))
+done
+
+if [ "$retry" -eq "$MAX_RETRIES" ]; then
+    log_fail "Failed to start bluetoothd after ${MAX_RETRIES} retries. Aborting test."
     echo "FAIL $TESTNAME" > "$res_file"
     exit 1
+else
+    log_info "Bluetooth daemon started successfully."
 fi
 
 # Power off Bluetooth controller

Runner/suites/Connectivity/Ethernet/README.md

@@ -1,37 +1,49 @@
+Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+SPDX-License-Identifier: BSD-3-Clause-Clear
+
 # Ethernet Validation Test
 
-## 📌 Overview
+## Overview
 
 This test case validates the basic functionality of the Ethernet interface (`eth0`) on the device. It checks for:
 
 - Interface presence
 - Interface status (UP/DOWN)
 - Basic connectivity via ping to `8.8.8.8`
 
+## Usage
+
+Instructions:
 
-## How to Run
+1. Copy repo to Target Device: Use scp to transfer the scripts from the host to the target device. The scripts should be copied to any directory on the target device.
+2. Verify Transfer: Ensure that the repo have been successfully copied to any directory on the target device.
+3. Run Scripts: Navigate to the directory where these files are copied on the target device and execute the scripts as needed.
 
-```sh
-source init_env
-cd suites/Connectivity/Ethernet
-./run.sh
+Run a Connectivity Ethernet test using:
+---
+#### Quick Example
+```
+git clone <this-repo>
+cd <this-repo>
+scp -r common Runner user@target_device_ip:<Path in device>
+ssh user@target_device_ip
+cd <Path in device>/Runner && ./run-test.sh Ethernet
 ```
 
 ## Prerequisites
 
-- `net-tools` must be available
+- `ip` and `ping` must be available
 - Root access may be required for complete validation
 
 ## Result Format
-
 Test result will be saved in `Ethernet.res` as:  
-✅ Pass Criteria  
+#### Pass Criteria  
 - Ethernet interface eth0 is detected
 - Interface is successfully brought up (if down)
 - Ping to 8.8.8.8 succeeds
 - `Ethernet connectivity verified` – if all validations pass  
 <!-- -->
-❌ Fail Criteria  
+#### Fail Criteria  
 - Interface eth0 is not found
 - Interface cannot be brought up
 - Ping test fails
@@ -42,8 +54,3 @@ Test result will be saved in `Ethernet.res` as:
 A .res file is generated in the same directory:
 
 `PASS Ethernet`  OR   `FAIL Ethernet`
-
-## License
-
-SPDX-License-Identifier: BSD-3-Clause-Clear  
-(C) Qualcomm Technologies, Inc. and/or its subsidiaries.

Runner/suites/Connectivity/Ethernet/run.sh

@@ -40,8 +40,8 @@ rm -f "$res_file"
 log_info "--------------------------------------------------------------------------"
 log_info "-------------------Starting $TESTNAME Testcase----------------------------"
 
-log_info "Checking if dependency: net-tools is available"
-check_dependencies net-tools
+log_info "Checking if dependency: ip and ping is available"
+check_dependencies ip ping 
 
 log_info "Starting Ethernet test..."
 

Runner/suites/Kernel/FunctionalArea/baseport/shmbridge/README.md

@@ -1,6 +1,9 @@
+Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+SPDX-License-Identifier: BSD-3-Clause-Clear
+
 # shmbridge Validation Test
 
-## 📌 Overview
+## Overview
 
 This test case validates the encryption and access functionality of the `shmbridge` partition by:
 
@@ -10,29 +13,40 @@ This test case validates the encryption and access functionality of the `shmbrid
 - Setting and verifying an encryption policy
 - Writing and reading a test file to confirm data integrity
 
-## How to Run
+## Usage
+
+Instructions:
+
+1. Copy repo to Target Device: Use scp to transfer the scripts from the host to the target device. The scripts should be copied to any directory on the target device.
+2. Verify Transfer: Ensure that the repo have been successfully copied to any directory on the target device.
+3. Run Scripts: Navigate to the directory where these files are copied on the target device and execute the scripts as needed.
 
-```sh
-source init_env
-cd suites/Kernel/FunctionalArea/baseport/shmbridge
-./run.sh
+Run a Kernel Baseport shmbridge test using:
+---
+#### Quick Example
+```
+git clone <this-repo>
+cd <this-repo>
+scp -r common Runner user@target_device_ip:<Path in device>
+ssh user@target_device_ip
+cd <Path in device>/Runner && ./run-test.sh shmbridge
 ```
 
 ## Prerequisites
-- `fscryptctl` must be available
+- `fscryptctl`, `mkfs.ext4` and `mount` must be available
 - Root access is required
 - Partition /dev/disk/by-partlabel/xbl_ramdump_a must exist and be accessible
 
 ## Result Format
 
 Test result will be saved in shmbridge.res as:  
-✅ Pass Criteria
+#### Pass Criteria
 - Partition is found and formatted
 - Encryption key is added and policy is set
 - Test file is written and read successfully
 - `Test Passed` – if all validations succeed
 <!-- -->
-❌ Fail Criteria
+#### Fail Criteria
 - Partition not found
 - Encryption setup fails
 - Test file cannot be read or content mismatch
@@ -42,8 +56,3 @@ Test result will be saved in shmbridge.res as:
 A .res file is generated in the same directory:
 
 `PASS shmbridge`  OR   `FAIL shmbridge`
-
-## License
-
-SPDX-License-Identifier: BSD-3-Clause-Clear  
-(C) Qualcomm Technologies, Inc. and/or its subsidiaries.

Runner/suites/Kernel/FunctionalArea/baseport/shmbridge/run.sh

@@ -41,7 +41,7 @@ log_info "----------------------------------------------------------------------
 log_info "-------------------Starting $TESTNAME Testcase----------------------------"
 
 log_info "Checking if dependency: fscryptctl is available"
-check_dependencies fscryptctl 
+check_dependencies fscryptctl mkfs.ext4 mount 
 
 MOUNT_POINT="/mnt/overlay"
 PARTITION="/dev/disk/by-partlabel/xbl_ramdump_a"
@@ -70,10 +70,7 @@ log_info "Mounting partition to $MOUNT_POINT with inlinecrypt"
 mount "$PARTITION" -o inlinecrypt "$MOUNT_POINT"
 
 log_info "Generating 64-byte encryption key"
-head -c 64 /dev/urandom > "$KEY_FILE"
-
-log_info "Checking if dependency binary is available"
-check_dependencies fscryptctl
+dd if=/dev/urandom bs=1 count=64 > "$KEY_FILE"
 
 log_info "Adding encryption key using fscryptctl"
 identifier=$(fscryptctl add_key "$MOUNT_POINT" < "$KEY_FILE")