Adding Bluetooth validation test case

This test validates the Bluetooth controller by checking for the presence of
bluetoothctl, ensuring bluetoothd is running, and toggling the controller power
state using bluetoothctl.

- Compliant with qcom-linux-testkit structure
- Generates .res file for CI/CD
- Uses functestlib logging and dependency checks

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

Author: qcom-anilyada

Runner/suites/Connectivity/Bluetooth/README.md

@@ -0,0 +1,50 @@
+# Bluetooth Validation Test
+
+## 📌 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
+
+
+
+## How to Run
+
+```sh
+source init_env
+cd suites/Connectivity/Bluetooth
+./run.sh
+```
+
+## Prerequisites
+- bluez package must be installed (provides bluetoothctl)
+- bluetoothd daemon must be running
+- Root access may be required for complete validation
+
+## Result Format
+
+Test result will be saved in Bluetooth.res as:  
+✅ Pass Criteria  
+- bluetoothctl is available
+- bluetoothd is running
+- Power on command returns success
+- Bluetooth controller powered on successfully. – if all validations pass  
+<!-- -->
+❌ Fail Criteria  
+- bluetoothctl not found
+- bluetoothd not running
+- Power on command fails
+- Failed to power on Bluetooth controller. – if any check fails
+
+
+## 📄 Output
+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

@@ -0,0 +1,80 @@
+#!/bin/sh
+
+# Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+# SPDX-License-Identifier: BSD-3-Clause-Clear
+
+# Source init_env and functestlib.sh
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+INIT_ENV=""
+SEARCH="$SCRIPT_DIR"
+while [ "$SEARCH" != "/" ]; do
+    if [ -f "$SEARCH/init_env" ]; then
+        INIT_ENV="$SEARCH/init_env"
+        break
+    fi
+    SEARCH=$(dirname "$SEARCH")
+done
+
+if [ -z "$INIT_ENV" ]; then
+    echo "[ERROR] Could not find init_env (starting at $SCRIPT_DIR)" >&2
+    exit 1
+fi
+
+# shellcheck disable=SC1090
+. "$INIT_ENV"
+
+# shellcheck disable=SC1090,SC1091
+. "$TOOLS/functestlib.sh"
+
+TESTNAME="Bluetooth"
+test_path=$(find_test_case_by_name "$TESTNAME") || {
+    log_fail "$TESTNAME : Test directory not found."
+    echo "FAIL $TESTNAME" > "./$TESTNAME.res"
+    exit 1
+}
+
+cd "$test_path" || exit 1
+res_file="./$TESTNAME.res"
+rm -f "$res_file"
+
+log_info "--------------------------------------------------------------------------"
+log_info "-------------------Starting $TESTNAME Testcase----------------------------"
+
+log_info "Checking if dependency: bluez is available"
+check_dependencies bluez
+
+log_info "Starting Bluetooth Test..."
+
+# Check if bluetoothctl is available
+if ! command -v bluetoothctl >/dev/null 2>&1; then
+    log_fail "bluetoothctl not found. Please install bluez."
+    echo "FAIL $TESTNAME" > "$res_file"
+    exit 1
+fi
+
+# Check if bluetoothd is running
+if ! pgrep bluetoothd >/dev/null; then
+    log_fail "bluetoothd is not running. Please start the Bluetooth daemon."
+    echo "FAIL $TESTNAME" > "$res_file"
+    exit 1
+fi
+
+# Power off Bluetooth controller
+log_info "Powering off Bluetooth controller..."
+bluetoothctl power off
+
+# Power on Bluetooth controller
+log_info "Powering on Bluetooth controller..."
+output=$(bluetoothctl power on)
+
+# Check for success message
+if echo "$output" | grep -q "Changing power on succeeded"; then
+    log_pass "Bluetooth controller powered on successfully."
+    echo "PASS $TESTNAME" > "$res_file"
+else
+    log_fail "Failed to power on Bluetooth controller."
+    echo "FAIL $TESTNAME" > "$res_file"
+fi
+
+log_info "-------------------Completed $TESTNAME Testcase----------------------------"
+