• Test plan for component: ofono

• Component Checklist: https://wiki.ubuntu.com/Process/Merges/Checklists/Common

• Trunk URL: https://github.com/rilmodem/ofono

• Ubuntu Package URL (LP): http://launchpad.net/ubuntu/+source/ofono

Description

This is a test plan for ofono as used by Ubuntu Touch. It does not cover scenarios and/or test cases for ofono installed on the desktop.

Dependants/Clients

• connectivity-api
• network-manager
• powerd
• telepathy-ofono
• Dialer / Messaging Apps
• network-indicator
• urfkill
• here-location-service-provider/location connectivity API

SIM Requirements

Unless specified otherwise, these tests should all be run with a valid unlocked SIM, preferably a primary operator SIM, not a MVNO SIM. The SIM should also be activated and proven to work for data, SMS, and voice before being used.

Dual SIM

This test plan was originally written to test a single SIM device. As dual-SIM support has been added to Ubuntu, it should be noted that this is visible to the rest of the system as a second modem instance. Where there's no difference with a single SIM device, the test cases have been left as is. It should be noted however that when verifying the test cases, you may need to take into account which SIM is being utilized and thus verify the correct modem instance ( /ril0 or /ril_1 ).

Most of the ofono scripts have been modified to work with dual-SIM devices, however if problems are encountered, please file a bug against the ofono (Ubuntu) package.

Device Setup

As these tests use oFono’s interfaces directly for testing, it’s sometimes necessary to stop some of the other components of the telephony stack in order to prevent interferrence with the test scripts. With this in mind, it’s best to

As ‘root’:

1. Add ofono-scripts directory to PATH ( export PATH=/usr/share/ofono/scripts:$PATH )

2. Stop NetworkManager ( stop network-manager )

3. Stop urfkill ( stop urfkill )
4. Re-start ofono ( restart ofono )
5. Unless otherwise described, set the modem online ( online-modem )

At this point, run ‘list-modems’ to ensure that the modem has come online properly, and begin testing!

Forcing Screen On

In general, it can be a good idea to force the display to stay on as ofono and the modem's behavior does change slightly when the screen blanks ( for power-saving ). The screen can be forced to stay unlocked/on by running the following command as root on the device:

powerd-cli display on

Test Plan

Test target device: Nexus 4 with active SIM card Secondary/backup device: TBD

Initial set up:

• Install latest image on phone
• Install ofono from the silo PPA
• Reboot the phone

Manual Tests

Most of the tests below use one or more scripts from the ofono-scripts packages. They're installed by default in the directory /usr/share/ofono/scripts.

Basic Tests

These tests should be run for every upload, as they cover the basic functionality that ofono provides.

• Test that the device can make outgoing phone calls, and receive incoming phone calls
• Test that the device can send outgoing MMS messages, and receive incoming MMS messages
• Test that the device can send outgoing text messages, and receive incoming text messages
• Test that incoming phone calls and text messages wake the device when the screen is off
• Test that mobile data connection works by testing Internet connectivity ( launch the browser )
• Test that flight-mode can enabled/disabled and mobile data is properly restored

• Verify that no new crash files of ofono clients are found in /var/crash!

Dialer / Messaging Autopilot

The Dialer and Message Apps are dependent on ofono, although they use the phonesim driver vs. the usual rilmodem driver used on actual Touch devices. If a change is being made to the ofono core, plugins, or the upstart job ( packaged as ofono.override in lxc-android-config, then these autopilot tests should be run on the device. This can be done by running the following steps:

• make the device writable
• apt-get update
• apt-get install dialer-app-autopilot messaging-app-autopilot

• reboot the device, unlock the screen, and pin the screen on using: sudo powerd-cli display on ( on the device )

• On the desktop run the following command to run the tests:

  • phablet-test-run dialer_app; reboot

  • phablet-test-run messaging_app; reboot

When finished, run apt-get purge ofono-phonesim-autostart.

Note - it's also a good idea to run these tests on one or more non-RIL devices such as manta or flow to ensure that core ofono changes have not caused any issues with the ofono-phonesim package.

DBus Changes

If any DBus API changes are made ( ie. adding new interfaces, properties, modifying methods, ... ) then sanity checking network indicator and system settings is recommended.

Note - running some of the test cases defined by the client test plans is also a good idea:

• indicator-network

• system-settings

• dialer-app

• messaging-app

The following is the list of function-specific test plans:

• SIM

• Voicecall

  • Basic Calling

  • Emergency Calling

  • Call Hold / Swap

  • MultiParty

  • Call Barring

  • Call Forwarding

  • Call Waiting

  • Supplementary Services (CLIR, CLIP)

• Network Registration

• GPRS/MMS Provisioning

• MMS Context manipulation

• GPRS

• SMS

• Radio Settings

• Call Settings

• USSD Tests

• Low Power Mode

• Bluetooth

Miscellaneous

Recent Intel-sponsored oFono Test Report ( documents test cases ):

• http://lists.ofono.org/pipermail/ofono/attachments/20131004/aff2cf36/attachment-0001.xlsx