zephyr

History

Jiawei Yang 38a6fc5e6f tests: Bluetooth: BR: Add GAP Server role test suite IUT works as a GAP Server (Peripheral) in the Bluetooth system. The peer device, GAP Client, is a PC running Bumble as a test tool. This test suite implements the following test cases: Case 1, Non-connectable Mode Testing. Verifies DUT can operate in non-connectable mode without allowing connections. Case 2, Connectable Non-discoverable Mode with Active Disconnection. Verifies DUT can accept connections and initiate disconnection. Case 3, Connectable Non-discoverable Mode with Passive Disconnection. Verifies DUT can accept connections and handle passive disconnection. Case 4, Connectable Non-discoverable Mode with Connection Rejection. Verifies DUT can reject connection requests. Case 5, Limited Discoverable Mode with Active Disconnection. Verifies DUT in limited discoverable mode can be discovered, accept connections and initiate disconnection. Case 6, Limited Discoverable Mode with Passive Disconnection. Verifies DUT can be discovered, accept connections and handle passive disconnection. Case 7, Limited Discoverable Mode with Connection Rejection. Verifies DUT can be discovered but reject connection requests. Case 8, General Discoverable Mode with Active Disconnection. Verifies DUT in general discoverable mode can be discovered, accept connections and initiate disconnection. Case 9, General Discoverable Mode with Passive Disconnection. Verifies DUT can be discovered, accept connections and handle passive disconnection. Case 10, General Discoverable Mode with Connection Rejection. Verifies DUT can be discovered but reject connection requests. Signed-off-by: Jiawei Yang <jiawei.yang_1@nxp.com>		2025-05-29 20:21:40 -04:00
..
boards
pytest
src
CMakeLists.txt
prj.conf
README.rst
testcase.yaml

README.rst

.. _bluetooth_classic_gap_server_tests:

Bluetooth Classic gap server 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/gap_s -O gap_s --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/gap_s -O gap_s --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