Skip to content

Latest commit

 

History

History

mwts-ofono

        mwts-ofono
        ---------------

INTRODUCTION

The mwts-ofono test package aimed for testtin basic functionalities of libofono-qt API. Currently the tests are designed to address:
	- sim manager 
    - voice call (forwarding, waiting, barring)

The ofono-qt api is available here: http://meego.gitorious.org/meego-cellular/ofono-qt.

Test scenarios include:
	- enable (lock) pin, disable (unlock) pin
	- verification of valid, invalid pin code
	- change pin code

SOURCE CODE AND COMPILING

  mwts-ofono compiles on MeeGo by executing 'sh buildrpm.sh' if you have missing dependencies,
  add them with 'zypper install <package>', if you need to search after a package you can do that
  with 'zypper search <package>' and get more info with 'zypper info <package>'.

  mwts-ofono builds a package on Debian distributions by executing 'dpkg-buildpackage -rfakeroot'
  , if you have missing dependencies add them with 'apt-get install <package>'.

   In case of pure compile/install on linux system you can compile and install by  'qmake', 'make',
  'make install' (as root).

   Doxygen API documentation can be generated by running 'doxygen' in mwts-gcamera root directory.

ENVIRONMENT REQUIREMENTS

  Modem name (later other settings might come) /usr/lib/tests/OfonoTest.conf, is set
  here. If the modem path in the .conf file is not found on the device, then another
  modem path is going to be chosen automaticily (if available)
  This test asset has been developed usaging phonesim simulator or ncdk (when it worked)
  on netbook meego image.

  Beside mwts log, you might want to use '/usr/lib/ofono/test/monitor-ofono' to monitor the steps.


EXECUTING TESTS

  mwts-ofono test execution is performed normally. Check the "General MWTS testing guide".



TEST RESULTS

  Test results can be found from device in directory /var/log/tests/
  Results are named as test cases, test_case_name.result file contains overall information
  about test run and measured values.


MIN SCRIPTER INTERFACE

  #sim manager
  ChangePin <pin type> <old pin code> <new pin code>
	Changes the pin given by string type.

  EnablePin <pin type> <pin code>
    Activates the lock for the particular pin type. The device will ask for a PIN automatically next time the
    device is turned on or the SIM is removed and re-inserter. The current PIN is required for the operation to succeed.

  DisablePin <pin type> <pin code>
    Deactivates the lock for the particular pin type. The current PIN is required for the operation to succeed.

  VerifyPin <pin type> <pin code>
    Verifies the pin by enabling or disabling with the valid pin code and verifies whether the device realizes its correctness

  VerifyInvalidPin <pin type> <pin code>
    Verifies the pin by enabling or disabling with the invalid pin code and verifies whether the device realizes its correctness

  VerifyPuk <puk code>
    Verifies the valid puk by resetting a new pin code (hard-coded) and verifies whether the device realizes its correctness.
    Currently the resetPin does not work, so neither this. http://bugs.meego.com/show_bug.cgi?id=12337

  VerifyInvalidPuk <puk code>
    Verifies the invalid puk by resetting a new pin code (hard-coded) and verifies whether the device realizes its correctness
    Currently the resetPin does not work, so neither this. http://bugs.meego.com/show_bug.cgi?id=12337

  ResetPin <puk type> <puk type> <new pin code>
    Provides the unblock key to the modem and if correct
    resets the pin to the new value of newpin.
    http://bugs.meego.com/show_bug.cgi?id=12337

  EnterPin <pin type> <pin code>
	Enters the currently pending pin. The type value must match the
    pin type being asked in the "pin required" (SimInfo) property. This 
    method is implicitly called from the test asset if needed. It is remained
    here only for special cases. 

  SimInfo 
	Prints info about the sim card (locked pin names, pin required)

  #voice call forwarding
  EnableVoiceCallBusy [telephone number]
    Enables the value of the voice "Busy" call forwarding rule

  DisableVoiceCallBusy
    Disables the voice "Busy" call forwarding rule, by setting to the value to empty

  EnableVoiceCallNoReply [telephone number]
    Enables the value of the voice "No Reply" call forwarding rule.

  DisableVoiceCallNoReply
    Disables the voice "NoReply" call forwarding rule, by setting to the value to empty

  EnableVoiceCallNotReachable [telephone number]
    Enables the value of the voice "Not Reachable" callforwarding rule.

  DisableVoiceCallNotReachable
    Disables the voice "NotReachable" call forwarding rule, by setting to the value to empty

  EnableVoiceCallUnconditional [telephone number]
    Enables the value of the voice unconditional call forwarding property

  DisableVoiceCallUnconditional
    Disables the voice "Unconditional" call forwarding rule, by setting to the value to empty

  #voice call waiting (settings)
  EnableVoiceCallWaiting
    Enables the call voice call waiting
  DisableVoiceCallWaiting
    Disables the call voice call waiting

  #voice call barring
  EnableVoiceCallOutgoing [all|international|internationalnothome] [pin code]
    Enables the voice call barring to outgoing calls

  DisableVoiceCallOutgoing [pin code]
    Disables the barring to outgoing voice calls

  EnableVoiceCallIncoming [always|whenroaming] [pin code]
    Enables the barring to incoming voice calls

  DisableVoiceCallIncoming [pin code]
    Disables the barring to incoming voice calls


KNOWN ISSUES

Sim manager:
- resetPin throws invalid argument dbus error
  http://bugs.meego.com/show_bug.cgi?id=12337

Voice call (forwarding, waiting, barring):
This part of the test asset (classes, test cases) are NOT SUPPORTED.
- signal 'voice..Complete' signals do not get emitted,
  bug report should be issued at ofono-qt api

- currently high FORWARDING_TIMEOUT (5 sec) is set
  for waiting for DBUS reply from the modem

- barring incoming, outgoing calls fail on
  phonesim
  http://bugs.meego.com/show_bug.cgi?id=12863

- until ofono-qt api does not have coverage on
  http://bugs.meego.com/show_bug.cgi?id=12858, you
  might want to use directly ofono api to have
  dialing and call answering