RadioSettings
Size: 3435
Comment:
|
Size: 4743
Comment: update comment re: LTE and list-modems
|
Deletions are marked like this. | Additions are marked like this. |
Line 10: | 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. | '''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 38: | Line 40: |
1. Run script set-tech-preference umts 2. Run script get-tech-preference 4. Check that the current technology is “umts”. 5. Run script list-modems 6. 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. 7. Run script set-tech-preference gsm 8. Run script get-tech-preference 9. Check that the current technology is “gsm” 10. Run test script list-modems 11. The output of the Technology/Bearer properties must be one of the following values: |
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: |
Line 60: | Line 51: |
12. Run test script set-tech-preference any 13. Run test script get-tech-preference 14. Check that the current technology is “any”. Note that with "any" preference values given by NetworkRegistration and ConnectionManager interfaces depend about modem and available network support. Note that if 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. |
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 68: | Line 66: |
'''Note''' - if the modem supports data-only LTE, running list-modems makes the device 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 aren't available via data-only LTE, the modem needs to switch 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 72: | Line 72: |
== 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. |
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.
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 - if the modem supports data-only LTE, running list-modems makes the device 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 aren't available via data-only LTE, the modem needs to switch 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)