nuntium

Dependents/Clients

  • telepathy-ofono
  • ofono
  • ubuntu-upload-manager
  • ubuntu-download-manager

Test Plan

These are only integration tests which require too much specialized infrastructure to automate (although they should eventually be worked through the ubuntu emulator).

Definitions

SUT
System Under Test
m-send.req
An MMS originating from a terminal (sent over the cellular data network)
m-retrieve.conf
An MMS downloaded from a message proxy (retrieved over the cellular data network)
m-notification.ind
A push message sent from ofono to nuntium

Prereqs

  • Two devices, one to be the SUT, others to be the originating terminals (Android, iOS)
  • A correct MMS context configured by ofono on the SUT.
  • SIMs on all terminals with a working cellular data connection.

Plan

  • Install image on SUT: ubuntu-device-flash --channel ubuntu-touch/devel-proposed

  • Run citrain device-upgrade [silo]

Receiving

  • Send a m-send.req from an additional phone to the SUT

  • On the SUT, verify that an m-retrieve.conf is correctly parsed and that a MessageAdded is signalled over dbus to telepathy-ofono: dbus-monitor sender=org.ofono.mms

  • Receive again but from a phone that has sent to more numbers that just the SUT.

Sending

  • Send a m-send.req from SUT to a target phone.

  • On the SUT, verify that no TransientError or PermanentError is signalled over dbus to telepathy-ofono: dbus-monitor sender=org.ofono.mms

  • Send again to more than one target device.

Flight mode

  • Set flight mode
  • Unset flight mode
  • Repeat now the "Sending" and "Receiving" tests. Do this for one of krillin or arale, and for mako.

Robustness when ofono aborts

  • Kill ofono (kill -9 pgrep ofonod) and wait for it to re-start and re-establish cellular data

  • Repeat now the "Sending" and "Receiving" tests

Checking for the default context

A default context can be set externally or chosen by nuntium from the first valid context that activates (selection is unit tested, activation isn't)

After a successful send, you can get the list of services

$ dbus-send --session --print-reply --dest=org.ofono.mms /org/ofono/mms org.ofono.mms.Manager.GetServices
method return sender=:1.187 -> dest=:1.230 reply_serial=2
   array [
      struct {
         object path "/org/ofono/mms/123456789012345"
         array [
            dict entry(
               string "Identity"
               variant                   string "123456789012345"
            )
         ]
      }
   ]

The query the properties for the service

dbus-send --session --print-reply --dest=org.ofono.mms /org/ofono/mms/123456789012345 org.ofono.mms.Service.GetProperties
method return sender=:1.187 -> dest=:1.231 reply_serial=2
   array [
      dict entry(
         string "UseDeliveryReports"
         variant             boolean false
      )
      dict entry(
         string "ModemObjectPath"
         variant             object path "/ril_0"
      )
      dict entry(
         string "PreferredContext"
         variant             object path "/ril_0/context2"
      )
   ]

If not run before, the PreferredContext property will be /

To set it externally use something like https://gist.github.com/sergiusens/703f3eb664b05b891b91 which will generate traffic on the bus that looks like

dbus-monitor interface=org.ofono.mms.Service
signal sender=org.freedesktop.DBus -> dest=:1.192 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.192"
method call sender=:1.193 -> dest=org.ofono.mms serial=2 path=/org/ofono/mms/123456789012345; interface=org.ofono.mms.Service; member=SetProperty
   string "PreferredContext"
   variant       object path "/c2"
signal sender=:1.190 -> dest=(null destination) serial=9 path=/org/ofono/mms/123456789012345; interface=org.ofono.mms.Service; member=PropertyChanged
   string "PreferredContext"
   variant       object path "/c2"

Retrieving the properties of the service would reflect this change.

Additional information

Upon running tests it is of good information to provide the wire capture, to do so first you need to verify the interface the MMS would be sent through; you can accomplish that by running:

phablet-shell
/usr/share/ofono/scrips/list-contexts

Locate a type=mms context; if it exists; activate the context and take note of the interface. If there is no type=mms context available what is most likely to be correct, given proper provisioning, is that the MMS would be sent through the type=internet context which by default should be activated (provided that it wasn't disabled manually either through a UI or call to ofono).

The interface has the form of rmnet_usb[X], where X corresponds to the one associated to the MMS context, so to get the capture, run:

phablet-shell
sudo tcpdump -w mms.pcap -i rmnet_usbX

Process/Merges/TestPlans/nuntium (last edited 2015-07-06 14:48:49 by alfonsosanchezbeato)