zephyr/tests/boot/with_mcumgr
Grzegorz Chwierut 095d3186e6 tests: fix: limit platforms in boot.with_mcumgr.test_upgrade_ble
Missed in #91596 that more platforms are added in common part.
Excluded nrf9160dk/nrf9160 and nucleo_wba55cg from
configuration with BLE.

Signed-off-by: Grzegorz Chwierut <grzegorz.chwierut@nordicsemi.no>
2025-07-04 16:41:01 -10:00
..
pytest
CMakeLists.txt
overlay-bt.conf
prj.conf
README.rst
sysbuild.conf
testcase.yaml tests: fix: limit platforms in boot.with_mcumgr.test_upgrade_ble 2025-07-04 16:41:01 -10:00

Upgrade testing with MCUmgr
###########################

This application is based on :ref:`smp_svr_sample`. It is built
using **sysbuild**. Tests are automated with pytest, a new harness of Twister
(more information can be found :ref:`here <integration_with_pytest>`)

.. note::
   Pytest uses the MCUmgr fixture which requires the ``mcumgr`` available
   in the system PATH.
   More information about MCUmgr can be found here :ref:`mcu_mgr`.

To run tests with Twister on ``nrf52840dk/nrf52840`` platform,
use following command:

.. code-block:: console

    ./zephyr/scripts/twister -vv --west-flash --enable-slow -T zephyr/tests/boot/with_mcumgr \
    -p nrf52840dk/nrf52840 --device-testing --device-serial /dev/ttyACM0

.. note::
   Twister requires ``--west-flash`` flag enabled to use sysbuild.

To test with ``mcumgr`` with Bluetooth, one must add ``usb_hci:hciX`` fixture
where ``hciX`` is the Bluetooth HCI device (e.g. ``hci1``).
Fixture can be added to Twister command: ``-X usb_hci:hci1``,
or added to the hardware map

.. code-block:: yaml

      - connected: true
        fixtures:
          - usb_hci:hci1

Test scripts can be found in ``pytest`` directory. To list available
scenarios with described procedures, one can use a pytest command:

.. code-block:: console

    pytest zephyr/tests/boot/with_mcumgr/pytest --collect-only -v