RadioSettings

Differences between revisions 6 and 20 (spanning 14 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 1 - 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.

Note 2 - Property ModemTechnologies from org.ofono.RadioSettings has changed its name to AvailableTechnologies in upstream ofono, so this test plan will change when ofono 1.16 lands.

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. The steps below must be adapted to the actual technologies supported by the modem, which can be seen by using list-modems and checking the value of "AvailableTechnologies" property in the RadioSetting interface.

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] lte
12. Run test script get-tech-preference [modem]
13. Check that the current technology is “lte”. 
14. The output of the Technology/Bearer properties must eventually have one of the following values (see note):
       [ org.ofono.NetworkRegistration ]
         Technology = [umts|hspa]
       [ org.ofono.ConnectionManager ]
         Bearer = lte

Note - if the modem supports data-only LTE but not VoLTE, running list-modems makes ConnectionManager.Bearer drop to umts or gsm. This is due to the fact that list-modems will trigger some supplementary services queries, and as these require voice control channels that are not available via data-only LTE, the modem needs to switch to umts or gsm. In that case to verify the result with existing scripts we have to run list-modems twice (SS queries are cached) or execute monitor-ofono on the background. Note also that if VoLTE is not supported (which we do not for any device at the moment), NetworkRegistration.Technology will never show "lte".

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 umts [modem]
- get-tech-preference [modem]
# Check that the current technology is "umts"
- Power off and then on the phone
- get-tech-preference [modem]
# Check that the current technology is "umts"

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 6 as of 2014-09-19 12:02:34 → 
  Size: 4744
  Editor: 192
  Comment:
+   ← Revision 20 as of 2016-07-07 06:07:29 → ⇥
  Size: 5300
  Editor: alfonsosanchezbeato
  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.
+'''Note 1''' - 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.

'''Note 2''' - Property Modem``Technologies from org.ofono.Radio``Settings has changed its name to Available``Technologies in upstream ofono, so this test plan will change when ofono 1.16 lands.
-Line 15:
+Line 17:
-This test case ensures the presence of the org.ofono.RadioSettings interface.
+This test case ensures the presence of the org.ofono.Radio``Settings interface.
-Line 20:
+Line 22:
-. Run script list-modems. Check that listed interfaces include org.ofono.RadioSettings with properties
+. Run script list-modems. 
2. Check that listed interfaces include org.ofono.RadioSettings with properties
-Line 22:
+Line 25:
-   previous usage of the tested card, used operator, contract and network access.
+   previous usage of the tested card, used operator, contract and modem.
-Line 29:
+Line 32:
-== 2. Set Tech Preference: GSM ==
+== 2. Change technology preference ==
-Line 32:
+Line 35:
-Ensure that tech preference can be set to GSM and that this causes the device to re-register voice and data using GSM.
+This test case verifies that we can change the radio technology preference. The steps below must be adapted to the actual technologies supported by the modem, which can be seen by using list-modems and checking the value of "AvailableTechnologies" property in the RadioSetting interface.
-Line 37:
+Line 40:
-# set-tech-preference gsm
+. 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] lte
12. Run test script get-tech-preference [modem]
13. Check that the current technology is “lte”. 
14. The output of the Technology/Bearer properties must eventually have one of the following values (see note):
       [ org.ofono.NetworkRegistration ]
         Technology = [umts|hspa]
       [ org.ofono.ConnectionManager ]
         Bearer = lte
-Line 40:
+Line 72:
-=== 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
}}}
+'''Note''' - if the modem supports data-only LTE but not VoLTE, running list-modems makes ConnectionManager.Bearer drop to umts or gsm. This is due to the fact that list-modems will trigger some supplementary services queries, and as these require voice control channels that are not available via data-only LTE, the modem needs to switch to umts or gsm.  In that case to verify the result with existing scripts we have to run list-modems twice (SS queries are cached) or execute monitor-ofono on the background. Note also that if VoLTE is not supported (which we do not for any device at the moment), NetworkRegistration.Technology will never show "lte".
-Line 67:
+Line 78:
-== 3. Set Tech Preference: UMTS ==
+== 3. Check storage of technology preference ==
-Line 71:
+Line 81:
-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 the modem stores the radio technology preference between restarts.
-Line 73:
+Line 83:
-=== Steps: ===
+=== Steps ===
-Line 76:
+Line 85:
-# set-tech-preference umts
+- 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 umts [modem]
- get-tech-preference [modem]
# Check that the current technology is "umts"
- Power off and then on the phone
- get-tech-preference [modem]
# Check that the current technology is "umts"
-Line 79:
+Line 99:
-=== Verification: ===
+'''Note''' - this is testing the modem itself, not ofono, although it's results are interesting.
-Line 81:
+Line 101:
-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 83:
+Line 103:
-{{{
# 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
}}}

=== Automation Status ===

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


== 4. Set Tech Preference: LTE ==

=== Purpose ===
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.

'''Note''' - this test should only be run on devices supporting LTE.

=== Steps: ===

{{{
# set-tech-preference lte
}}}

=== 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 = 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