Navi Bluetooth Test Suite

This is a test suite for Bluetooth on Android devices.

Prerequisites

• Environment

  RF Shielding box is recommended to use. Flakiness rate could be high if the air is not clear.

• DUT devices

  Must be an Android device with SDK>=33 (Android 13). All Pixel devices with SDK>=33(Android 13) are supported.

• REF devices

  Currently, only Pixel 8/8a and later series are officially supported. Other devices may work, but not tested.

  Most USB dongles cannot fully support HFP / LE test cases, especially LE Audio.

• Test host.

  We recommend to use Linux as the test host, but Windows is also supported.

  The test host should have the following libraries installed:

  • Python 3.12 or later

    • Check your Python 3 version number:

    python3 --version

    • If your version is lower than Python 3.12, install the latest version following https://wiki.python.org/moin/BeginnersGuide/Download.
    • You may also use uv to manage the workspace.

    # On Linux & macOS
    curl -LsSf https://astral.sh/uv/install.sh | sh
    # On Windows
    powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
    
    uv python install 3.12

  • ADB

    If you don't already have the adb command-line tool, you may install using package managers

    # Ubuntu
    sudo apt install android-tools-adb
    
    # Windows
    winget install --id=Google.PlatformTools -e

    Or, manually download and install it from Android SDK Platform Tools, and add them to your PATH.

  • FFmpeg

    If you don't already have the ffmpeg command-line tool, you may install using package managers

    # Ubuntu
    sudo apt install ffmpeg
    
    # Windows
    winget install --id=Gyan.FFmpeg  -e

    Or, manually download and install it from

    Some of cases need FFmpeg. Please download them from https://ffmpeg.org/download.html and add the binary to your PATH.

  • Windows

    On Windows, you may also need to enable Global UTF-8 support in Control Panel > Clock and Region > Region > Administrative tab > Change system locale button > enable Beta:Use Unicode UTF-8 for worldwide language support, or some UTF-8 IO will break the test.

Test steps

Follow these steps to prepare and execute tests and review test results.

Prepare the test

Prepare the following materials to be used for the tests.

Get the test repo and install the test environment

git clone https://github.com/google/bt-navi-tests.git
cd bt-navi-tests

python3 -m venv .venv
python3 -m pip install -e .

# Or use uv
uv venv .venv --python 3.12
uv pip install -e .

Configure testbed

NOTE: If you don't care the order, use testbed any, or let mobly_runner generate one.

Modify the test config file config.yml as follows:

• Find device serial numbers:

$ adb devices -l
List of devices attached

localhost:33461        device product:akita model:Pixel_8a device:akita transport_id:5
localhost:40155        device product:caiman model:Pixel_9_Pro device:caiman transport_id:3
localhost:46879        device product:akita model:Pixel_8a device:akita transport_id:4

In this example, the source device is localhost:33461 and the target device is localhost:40155 and localhost:46879.

• Specify the target and source device serial numbers:

AndroidDevice:
- serial: localhost:33461
  label: DUT
- serial: localhost:40155
  label: REF
- serial: localhost:46879
  label: REF

Run the test

This test suite has been integrated with Mobly Android Partner Tools, so it can be run with

# Smoke
mobly_runner smoke -c config.yml -tb default -i [-u]
# Venti (More functionality tests)
mobly_runner venti -c config.yml -tb default -i [-u]
# All (Smoke + Venti)
mobly_runner run_all -c config.yml -tb default -i [-u]

NOTE: If -c and -tb is not specified, Mobly mobly_runner will automatically select all devices with the order present in adb devices. Check mobly_runner -h for more details.

Upload test results

After running the test, Mobly should generate a log directory like:

Artifacts are saved in "/tmp/logs/mobly/..."

If you have partner GCP account, you can upload the test result to GCP with results_uploader:

results_uploader /tmp/logs/mobly/...

Get full logs

To get all dumpsys, snoop, recorded audio, bugreports, add the following test params to config.yml:

  TestParams:
    max_retry_count: 2
    record_full_data: True