tests: Bluetooth: BR: Add test suite RFCOMM_client

IUT works as an RFCOMM Client. The peer device, RFCOMM server, is a PC
running bumble.

In the test suite, there are five test cases:
Case 1, RFCOMM Client with Command Responses. Tests that the client can
establish a DLC, respond to various commands (RLS, RPN, Test), send NSC
responses, and properly handle DLC disconnection and RFCOMM session
shutdown.
Case 2, RFCOMM Client with Credit Based Flow Control. Tests that the
client can establish a DLC, perform information transfer with credit
based flow control, initiate disconnection, and shutdown the RFCOMM
session.
Case 3, RFCOMM Client with BR Connection Disconnection. Tests that the
client correctly handles scenarios where the BR connection is
disconnected during DLC establishment.
Case 4, RFCOMM Client with Aggregate Flow Control. Tests that the client
can establish a DLC, perform information transfer with aggregate flow
control, and properly handle disconnection and session shutdown.
Case 5, RFCOMM Client with Failed PN Response. Tests that the client
correctly handles scenarios where it fails to receive a PN response when
establishing a DLC.

Signed-off-by: Jiawei Yang <jiawei.yang_1@nxp.com>

Author: jerryyang35

tests/bluetooth/classic/rfcomm_c/CMakeLists.txt

@@ -0,0 +1,10 @@
+# SPDX-License-Identifier: Apache-2.0
+
+cmake_minimum_required(VERSION 3.20.0)
+set(NO_QEMU_SERIAL_BT_SERVER 1)
+
+find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
+project(bluetooth)
+
+FILE(GLOB app_sources src/*.c)
+target_sources(app PRIVATE ${app_sources})

tests/bluetooth/classic/rfcomm_c/README.rst

@@ -0,0 +1,74 @@
+.. _bluetooth_classic_rfcomm_client_tests:
+
+Bluetooth Classic rfcomm client Tests
+##################################
+
+Overview
+********
+
+This test suite uses ``bumble`` for testing Bluetooth Classic communication between a host
+PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
+
+Prerequisites
+*************
+
+The test suite has the following prerequisites:
+
+* The ``bumble`` library installed on the host PC.
+The Bluetooth Classic controller on PC side is required. Refer to getting started of `bumble`_
+for details.
+
+The HCI transport for ``bumble`` can be configured as follows:
+
+* A specific configuration context can be provided along with the ``usb_hci`` fixture separated by
+  a ``:`` (i.e. specify fixture ``usb_hci:usb:0`` to use the ``usb:0`` as hci transport for
+  ``bumble``).
+* The configuration context can be overridden using the `hci transport`_ can be provided using the
+  ``--hci-transport`` test suite argument (i.e. run ``twister`` with the
+  ``--pytest-args=--hci-transport=usb:0`` argument to use the ``usb:0`` as hci transport for
+  ``bumble``).
+
+Building and Running
+********************
+
+Running on mimxrt1170_evk@B/mimxrt1176/cm7
+==========================================
+
+Running the test suite on :ref:`mimxrt1170_evk` relies on configuration of ``bumble``.
+
+On the host PC, a HCI transport needs to be required. Refer to `bumble platforms`_ page of
+``bumble`` for details.
+
+For example, on windows, a PTS dongle is used. After `WinUSB driver`_ has been installed,
+the HCI transport would be USB transport interface ``usb:<index>``.
+
+If the HCI transport is ``usb:0`` and debug console port is ``COM4``, the test suite can be
+launched using Twister:
+
+.. code-block:: shell
+
+   west twister -v -p mimxrt1170_evk@B/mimxrt1176/cm7 --device-testing --device-serial COM4 -T tests/bluetooth/classic/rfcomm_c -O rfcomm_c --force-platform --west-flash --west-runner=jlink -X usb_hci:usb:0
+
+Running on Hardware
+===================
+
+Running the test suite on hardware requires a HCI transport connected to the host PC.
+
+The test suite can be launched using Twister. Below is an example for running on the
+:zephyr:board:`mimxrt1170_evk@B/mimxrt1176/cm7`:
+
+.. code-block:: shell
+
+   west twister -v -p mimxrt1170_evk@B/mimxrt1176/cm7 --device-testing --device-serial COM4 -T tests/bluetooth/classic/rfcomm_c -O rfcomm_c --force-platform --west-flash --west-runner=jlink -X usb_hci:usb:0
+
+.. _bumble:
+   https://google.github.io/bumble/getting_started.html
+
+.. _hci transport:
+   https://google.github.io/bumble/transports/index.html
+
+.. _bumble platforms:
+   https://google.github.io/bumble/platforms/index.html
+
+.. _WinUSB driver:
+   https://google.github.io/bumble/platforms/windows.html

tests/bluetooth/classic/rfcomm_c/boards/mimxrt1170_evk_mimxrt1176_cm7_B.conf

@@ -0,0 +1,10 @@
+#select NXP NW612 Chipset
+CONFIG_BT_NXP_NW612=y
+
+CONFIG_BT_SETTINGS=n
+CONFIG_FLASH=n
+CONFIG_FLASH_MAP=n
+CONFIG_NVS=n
+CONFIG_SETTINGS=n
+
+CONFIG_ENTROPY_GENERATOR=y

tests/bluetooth/classic/rfcomm_c/boards/mimxrt1170_evk_mimxrt1176_cm7_B.overlay

@@ -0,0 +1,11 @@
+/*
+ * Copyright 2024 NXP
+ *
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+/ {
+	chosen {
+		zephyr,sram = &dtcm;
+	};
+};

tests/bluetooth/classic/rfcomm_c/prj.conf

@@ -0,0 +1,12 @@
+CONFIG_BT=y
+CONFIG_BT_CLASSIC=y
+CONFIG_BT_SHELL=y
+CONFIG_LOG=y
+CONFIG_ZTEST=y
+
+CONFIG_BT_RFCOMM=y
+
+CONFIG_BT_DEVICE_NAME="rfcomm_c"
+
+CONFIG_BT_CREATE_CONN_TIMEOUT=30
+CONFIG_BT_PAGE_TIMEOUT=0xFFFF

tests/bluetooth/classic/rfcomm_c/pytest/conftest.py

@@ -0,0 +1,55 @@
+# Copyright 2025 NXP
+#
+# SPDX-License-Identifier: Apache-2.0
+
+import logging
+import re
+
+import pytest
+from twister_harness import DeviceAdapter, Shell
+
+logger = logging.getLogger(__name__)
+
+
+def pytest_addoption(parser) -> None:
+    """Add local parser options to pytest."""
+    parser.addoption('--hci-transport', default=None, help='Configuration HCI transport for bumble')
+
+
+@pytest.fixture(name='initialize', scope='session')
+def fixture_initialize(request, shell: Shell, dut: DeviceAdapter):
+    """Session initializtion"""
+    # Get HCI transport for bumble
+    hci = request.config.getoption('--hci-transport')
+
+    if hci is None:
+        for fixture in dut.device_config.fixtures:
+            if fixture.startswith('usb_hci:'):
+                hci = fixture.split(sep=':', maxsplit=1)[1]
+                break
+
+    assert hci is not None
+
+    lines = shell.exec_command("bt init")
+    lines = dut.readlines_until("Bluetooth initialized")
+    regex = r'Identity: *(?P<bd_addr>([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2}) *\((.*?)\))'
+    bd_addr = None
+    for line in lines:
+        logger.info(f"Shell log {line}")
+        m = re.search(regex, line)
+        if m:
+            bd_addr = m.group('bd_addr')
+
+    if bd_addr is None:
+        logger.error('Fail to get IUT BD address')
+        raise AssertionError
+
+    logger.info('initialized')
+    return hci, bd_addr
+
+
+@pytest.fixture
+def device_under_test(initialize):
+    logger.info('Start running testcase')
+    yield initialize
+    logger.info('Done')