connman automated

critical

Image Types:
basesdk-amd64 / minimal-armhf-internal / minimal-armhf / minimal-arm64 / minimal-amd64 / sdk-amd64 / target-armhf-internal / target-amd64
Image Deployment:
APT, OSTree
Type:
functional

Description

Runs some automated tests using the ConnMan D-Bus API. It guarantees most of the basic features are working. Network connection management: ensuring that ConnMan's APIs are accessible is part of strategic network management functionality.


Pre Conditions

  1. Clone the tests repository from another computer (Note that the branch being tested may change depending on the release, please make sure to clone the correct branch for the release in question):
  2. $ git clone --branch apertis/v2020dev0 https://gitlab.apertis.org/tests/connman.git

  3. Copy the test directory connman to the target device:
  4. $ DUT_IP=<device-ip>

    $ scp -r connman user@$DUT_IP:

  5. Log into the target device:
  6. $ ssh user@$DUT_IP


Execution Steps

  1. Enter test directory:
  2. $ cd connman

  3. Execute the following command:
  4. $ common/run-test-in-systemd --timeout=900 --basename bin/connman-test.sh


Expected

An example output is:

user@apertis:~/connman-master$ bin/connman-test.sh

test_manager

test_offlinemode

test_technologies

test_technology_enable /net/connman/technology/ethernet

test_technology_tethering /net/connman/technology/ethernet

test_ethernet

test_service_properties /net/connman/service/ethernet_525400f47dad_cable

test_clock

PASSED

FAILED is displayed in case of failure.

Notes

  • Warning: Connman changes are persistent (over reboot!). After finishing testing, it might be wise to perform the dhcp test to ensure that the network is in a sensible state.
  • For ALL tests the enable step will give an "In progress" error if the device is already enabled. This is to be expected.