RadioSettings

Differences between revisions 4 and 13 (spanning 9 versions)

Test plan for component: https://wiki.ubuntu.com/Process/Merges/TestPlans/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

Radio Settings Tests

Note - Supported radio settings are modem dependant. Response to setting attempt of unsupported technology preference varies between different modems. Modem can either respond with error code or subtly change the setting to value it considers to be close of the requested setting. Also storing responsability of preference may vary between modems. This means that value might be different than what was set with certain modems after bootup. These tests assume that test setup supports edge, hspa, umts and gsm.

1. Verify Interface Availablility / Tech Preference

Purpose

This test case ensures the presence of the org.ofono.RadioSettings interface.

Steps:

1. Run script list-modems. 
2. Check that listed interfaces include org.ofono.RadioSettings with properties 
   TechnologyPreference, ModemTechnologies and FastDormancy. Exact values of properties depend about the 
   previous usage of the tested card, used operator, contract and modem.

Automation Status

Automation of the RadioSettings tests is currently blocked on improvements to the emulator's telephony support.

2. Change technology preference

Purpose

This test case verifies that we can change the radio technology preference.

Steps:

1. Run script set-tech-preference [modem] gsm
2. Run script get-tech-preference [modem]
3. Check that the current technology is “gsm”
4. Run test script list-modems
5. The output of the Technology/Bearer properties must be one of the following values:
       [ org.ofono.NetworkRegistration ]
         Technology = [gsm|edge]
       [ org.ofono.ConnectionManager ]
         Bearer = [gsm|edge]
    Also here note that technology change is not immediate. It takes some time to drop out 
    of old network and connect to another. 
6. Run script set-tech-preference [modem] umts
7. Run script get-tech-preference [modem]
8. Check that the current technology is “umts”. 
9. Run script list-modems
10. The output of the Technology/Bearer properties must eventually have one of the following values:
       [ org.ofono.NetworkRegistration ]
         Technology = [umts|hspa]
       [ org.ofono.ConnectionManager ]
         Bearer = [umts|hsdpa|hsupa|hspa]
   Note that technology change is not immediate. It takes some time to drop out of old
   network and connect to another. 
11. Run test script set-tech-preference [modem] any
12. Run test script get-tech-preference [modem]
13. Check that the current technology is fastest technology supported by the modem ( eg. "gsm", “umts”, ... ).

Note 1 - with "any" preference values given by NetworkRegistration and ConnectionManager interfaces depend about modem and available network support.

Note 2 - if the modem supports data-only LTE running the list-modems makes it to drop to umts or gsm. In that case only way to verify the result with existing scripts is to run monitor-ofono on the background.

Automation Status

Automation of the RadioSettings tests is currently blocked on improvements to the emulator's telephony support.

3. Check storage of technology preference

Purpose

This test case verifies that the modem stores the radio technology preference between restarts.

Steps

- set-tech-preference [modem] gsm
- get-tech-preference [modem]
# Check that the current technology is “gsm”
- Power off and then on the phone
- get-tech-preference [modem]
# Check that the current technology is “gsm”
- set-tech-preference any [modem]
- get-tech-preference [modem]
# Check that the current technology is the fastest tech supported by the modem
- Power off and then on the phone
- get-tech-preference [modem]
# Check that the current technology is the fastest tech supported by the modenm

Note - this is testing the modem itself, not ofono, although it's results are interesting.

Automation

This test case requires real hardware and is difficult to automate as it requires multiple reboots of the phone.

Process/Merges/TestPlans/ofono/RadioSettings (last edited 2016-07-07 06:07:29 by alfonsosanchezbeato)

-  ⇤ ← Revision 4 as of 2014-08-01 08:55:54 → 
  Size: 4717
  Editor: alfonsosanchezbeato
  Comment:
+   ← Revision 13 as of 2014-11-21 23:18:05 → ⇥
  Size: 4485
  Editor: 209-6-88-107
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 10:
+'''Note''' - Supported radio settings are modem dependant. Response to setting attempt of unsupported technology preference varies between different modems. Modem can either respond with error code or subtly change the setting to value it considers to be close of the requested setting. Also storing responsability of preference may vary between modems. This means that value might be different than what was set with certain modems after bootup. These tests assume that test setup supports edge, hspa, umts and gsm.
-Line 13:
+Line 15:
-Ensure the presence of the Radio``Setting interface and that Technology``Preference is set to a sensible value.
+This test case ensures the presence of the org.ofono.RadioSettings interface.
-Line 18:
+Line 20:
-# list-modems
}}}

=== Verification: ===

 * verify the presence of Radio``Settings in the top-level modem properties:
{{{
    Features includes 'rat'
    Interfaces includes ''org.ofono.VoiceCallManager''
}}}
 * verify that Radio``Settings exposes the property ''Technology``Preference'' and that it's set to one of the following values: ''umts'', ''lte'', ''gsm'', or ''any'' ( '''TODO''': ''any'' is deprecated and should not appear when system settings is upgraded to use ''Modem``Technologies'' property ).
 * verify that Radio``Settings exposes the property ''Modem``Technologies'', which contains an array of strings that must be a subset of ''umts'', ''lte'', and ''gsm''.

=== Automation Status ===

Automation of the Radio``Settings tests is currently blocked on improvements to the emulator's telephony support.

== 2. Set Tech Preference: GSM ==

=== Purpose ===
Ensure that tech preference can be set to GSM and that this causes the device to re-register voice and data using GSM.

=== Steps: ===

{{{
# set-tech-preference gsm
}}}

=== Verification: ===

Changing the technology preference may result in the device re-registering to the network so it may be necessary to re-run ''list-modems'' a few times until you see it properly registered ( ie. the Network``Registration ''Status'' property is set to ''registered'' ).

{{{
# list-modems
}}}

 * verify that the Radio``Settings preference took effect:
{{{
    TechnologyPreference = gsm
}}} 

 * verify the new Network``Registration technology:
{{{
    Technology = gsm
}}}

 * if the Connection``Manager is ''Attached'', verify that the ''Bearer'' property is correct: 
{{{
    Bearer = edge | gprs
+. Run script list-modems. 
2. Check that listed interfaces include org.ofono.RadioSettings with properties 
   TechnologyPreference, ModemTechnologies and FastDormancy. Exact values of properties depend about the 
   previous usage of the tested card, used operator, contract and modem.
-Line 73:
+Line 30:
-== 3. Set Tech Preference: UMTS ==
+== 2. Change technology preference ==
-Line 77:
+Line 33:
-Ensure that tech preference can be set to UMTS and that this causes the device to re-register voice and data using UMTS or GSM ( depending upon network availability ).
+This test case verifies that we can change the radio technology preference.
-Line 82:
+Line 38:
-# set-tech-preference umts
+. Run script set-tech-preference [modem] gsm
2. Run script get-tech-preference [modem]
3. Check that the current technology is “gsm”
4. Run test script list-modems
5. The output of the Technology/Bearer properties must be one of the following values:
       [ org.ofono.NetworkRegistration ]
         Technology = [gsm|edge]
       [ org.ofono.ConnectionManager ]
         Bearer = [gsm|edge]
    Also here note that technology change is not immediate. It takes some time to drop out 
    of old network and connect to another. 
6. Run script set-tech-preference [modem] umts
7. Run script get-tech-preference [modem]
8. Check that the current technology is “umts”. 
9. Run script list-modems
10. The output of the Technology/Bearer properties must eventually have one of the following values:
       [ org.ofono.NetworkRegistration ]
         Technology = [umts|hspa]
       [ org.ofono.ConnectionManager ]
         Bearer = [umts|hsdpa|hsupa|hspa]
   Note that technology change is not immediate. It takes some time to drop out of old
   network and connect to another. 
11. Run test script set-tech-preference [modem] any
12. Run test script get-tech-preference [modem]
13. Check that the current technology is fastest technology supported by the modem ( eg. "gsm", “umts”, ... ).
-Line 85:
+Line 65:
-=== Verification: ===
+'''Note 1''' - with "any" preference values given by NetworkRegistration and ConnectionManager interfaces depend about modem and available network support.
-Line 87:
+Line 67:
-Changing the technology preference may result in the device re-registering to the network so it may be necessary to re-run ''list-modems'' a few times until you see it properly registered ( ie. the Network``Registration ''Status'' property is set to ''registered'' ).

{{{
# list-modems
}}}

 * verify that the Radio``Settings preference took effect:
{{{
    TechnologyPreference = umts
}}} 

 * verify the new Network``Registration technology:
{{{
    Technology = umts | gsm
}}}

 * if the Connection``Manager is ''Attached'', verify that the ''Bearer'' property is correct: 
{{{
    Bearer = umts | hsupa | hsdap | hspa | edge | gsm
}}}
+'''Note 2''' - if the modem supports data-only LTE running the list-modems makes it to drop to umts or gsm. In that case only way to verify the result with existing scripts is to run monitor-ofono on the background.
-Line 112:
+Line 73:
-== 4. Set Tech Preference: LTE ==
+== 3. Check storage of technology preference ==
-Line 116:
+Line 76:
-Ensure that tech preference can be set to GSM and that this causes the device to re-register voice and data using LTE, UMTS, or GSM.
+This test case verifies that the modem stores the radio technology preference between restarts.
-Line 118:
+Line 78:
-'''Note''' - this test should only be run on devices supporting LTE.

=== Steps: ===
+=== Steps ===
-Line 123:
+Line 80:
-# set-tech-preference lte
+- set-tech-preference [modem] gsm
- get-tech-preference [modem]
# Check that the current technology is “gsm”
- Power off and then on the phone
- get-tech-preference [modem]
# Check that the current technology is “gsm”
- set-tech-preference any [modem]
- get-tech-preference [modem]
# Check that the current technology is the fastest tech supported by the modem
- Power off and then on the phone
- get-tech-preference [modem]
# Check that the current technology is the fastest tech supported by the modenm
-Line 126:
+Line 94:
-=== Verification: ===
+'''Note''' - this is testing the modem itself, not ofono, although it's results are interesting.
-Line 128:
+Line 96:
-Changing the technology preference may result in the device re-registering to the network so it may be necessary to re-run ''list-modems'' a few times until you see it properly registered ( ie. the Network``Registration ''Status'' property is set to ''registered'' ).
+=== Automation ===
-Line 130:
+Line 98:
-{{{
# list-modems
}}}

 * verify that the Radio``Settings preference took effect:
{{{
    TechnologyPreference = lte
}}} 

 * verify the new Network``Registration technology:
{{{
    Technology = lte | umts | gsm
}}}

 * if the Connection``Manager is ''Attached'', verify that the ''Bearer'' property is correct: 
{{{
    Bearer = lte | umts | hsupa | hsdap | hspa | edge | gsm
}}}

=== Automation Status ===

Automation of the Radio``Settings tests is currently blocked on improvements to the emulator's telephony support.
+This test case requires real hardware and is difficult to automate as it requires multiple reboots of the phone.

Ubuntu Wiki

RadioSettings

Radio Settings Tests

1. Verify Interface Availablility / Tech Preference

Purpose

Steps:

Automation Status

2. Change technology preference

Purpose

Steps:

Automation Status

3. Check storage of technology preference

Purpose

Steps

Automation