Contacts-StoringEntries

Config Control: FL08 Template #: SWF0034 LEVEL: 4 Quality Record Doc. Version: 01.00.00 TITLE: Contacts_Falcon Storing Entries Manual Test Script Doc. Date: 10/05/09 Page: 4 of 87 Title: Contacts_Falcon Storing Entries Manual Test Script Document Information: Document Point of Contact: Prabha Rajagopal Filename: Contacts-StoringEntries.doc New Vob location: /vob/system_test/components/manual_tests/ST_TPS_Doc/ergo/contacts NOTE: In case of any discrepancies/ reference to old product’s matrix, please refer to the “Old Vob Location”. Old Vob Location: /vob/system_test/components/manual_tests/ota/synergy2_ergo/Contacts Template Version: 02.06.00 Document Revision History Doc. Version Tree Version Doc. Date Revised By Ref. # Description 01.01.00 /main/1 12/04/2002 S.Stupar MIRpn51177 Initial Creation 01.02.04 /main/2 5/9/2003 S.Stupar MIRpn51177 NJDts03637 - SRS changes and Largo. update for penang comments MIRpn66837 - Inspection comments 01.03.01 /main/3 7/10/2003 S.Stupar MIRpn75725 Update for errors found during testing. 01.04.01 /main/4 8/11/2003 S.Stupar MIRpn83138 Update for latest changes/errors found during testing. 01.05.01 /main/5 10/9/2003 S.Stupar MIRpn89256 Update for MotoTalk for Conch Plus, Pro 01.05.02 /main/5 10/16/2003 S.Stupar MIRpn89256 Update for latest MOTOtalk feature changes; MIRpn67714 01.06.01 /main/6 09/15/2004 S.Stupar MIRpt68974 Update for Tavernier and minor errors found during testing. 01.07.01 /main/7 03/16/2005 ChaiLing Saw GSGmy01626 Update setup section for test case 37 and Cross Reference Table for test case 25. 01.08.01 /main/8 03/24/2005 S.Stupar MIRpt81664 Update for SDGC feature 01.08.02 /main/8 03/29/2005 S.Stupar MIRpt81664 Add review comments. 01.09.02 /main/9 06/06/2005 S.Stupar MIRpt82679 Update for the Encryption feature 01.10.01 /main/10 10/11/2005 ChaiLing Saw ISGcq00353003 Update new test cases for Marlin. 01.10.03 /main/10 10/23/2005 ChaiLing Saw ISGcq00353003 Add review comments 01.11.01 /main/11 11/21/2005 ChaiLing Saw ISGcq00359319 Update new test cases for Conch Pro, Hub Masking feature. 01.11.02 /main/11 11/29/2005 ChaiLing Saw ISGcq00359319 Add review comments 01.12.01 /main/12 03/27/2006 Prabha ISGcq00389059 Update for iCard prefix for Mango Key R2 01.12.02 /main/12 04/03/2006 Prabha ISGcq00389059 Update review comments 01.13.03 /main/13 09/04/2006 Shruthi ISGcq00411025 Update as per the PR ISGcq00411025 01.14.00 /main/14 11/29/2006 Prabha Rajagopal ISGcq00443671 Update cross reference table for Cobia based on ISGcq00434578 01.15.00 /main/15 03/22/2007 Sheenu S Dev ISGcq00470487 Updated the suite for TAOS 01.16.00 /main/16 04/16/2007 Prabha Rajagopal ISGcq00467331 Update test cases 41.0 & 41.1 01.17.00 /main/17 06/11/2007 Piragash M. Kanneappan ISGcq00497139 Updated TC37 - 40 in cross reference table, adding applicability for Cobia. 01.18.02 /main/18 11/22/2007 Roland Castelino ISGcq00516097 ISGcq00512381 - Updated Product matrix for Bluefin AFU feature 01.19.00 /main/19 03/17/2008 Joy Ong ISGcq00527625 Athens: Updated TPS for Increased Contacts to 1200 entries. SU CR: ISGcq00518944 . 01.20.00 /main/20 05/15/2008 Sheenu S Dev ISGcq00532607 Majua: Update as per s/w PR ISGcq00531507 Modified TC’s: 41, 41.1 Product Matrix Update 01.21.00 /main/21 11/23/2008 Prabha R ISGcq00548659 Blackstone: Made changes for MsgGroup based on ISGcq00540091 New Revision history 01.00.00 /main/1 08/07/2009 Almas M.Gandhi ISGcq00575736 A new element in VOB is created for the TPS in word format. Test suite conversion from .fm to word format and updated product matrix for F/FI/UI, severity,Manual/Automated information 01.00.00 /main/2 10/05/2009 Globina Dabre ISGcq00580596 Brightwater : TC 8 is not applicable hence product matrix is updated as per Test PR ISGcq00580596 1 Design Section 1.1 Description The Contacts allows the user to store names and numbers which are frequently used. These Contacts entries can be sorted by name. By default, entries will be displayed sorted by name. The Speed Number is a unique ID assigned to each phone number that refers to where it is stored in memory. The user can press the ’Cntcs’ softkey on the idle screen (if it is set to be a softkey) or go to Contacts in the Main Menu to view, call, manage existing entries, and store new entries. A single Contact to the end-user will be provided and it will be compatible with GSM and Endeavor. The Contacts data stored on the Condor or its compatible SIM has two separate lists. The first list is GSM/Endeavor area, which consists of phone list, private list and talkgroup list, and it is compatible with GSM and Endeavor subscriber units respectively. The second list is known as the contact list. The end user will only see the contact list (dynamic Contacts) when Condor SIM is used. Falcon SIM only has the contact list. Contacts Storing Entries section is composed of the following: 1. Storing Entries From Another Application 2. Storing Entries Using Contacts Menu 3. Storing Multiple Number Associated with a Single Name. Falcon SIM Capacities: Falcon SIM has the capacity of 600 entries. It is broken down the following way: 1. 200 slots are designated for entries of 64-digit phone numbers and 32-character E-mail IDs. These are considered to be extended slots. 2. 400 slots are designated for entries of normal length. Phone numbers with 20 digits or less and other type of numbers are considered to be normal length numbers. Note for Softkeys in Figures: Unless otherwise indicated, all of the sofkey behavior in the figures in this document apply to a products without 5-way navigation. If there is a conflict, the figures are superseded by requirements. MotoTalk Notes: “MOTOtalk” feature is part of the Main menu of the Falcon Ergonomics. The iDEN MT feature allows simple, direct, simplex two-way, radio-to-radio communication between subscriber units. It is a PTT based feature that operates like most two way radios. The iDEN MT feature is expected to be used in the following scenarios: - “Out” of coverage areas - “In” coverage areas - Inter-iDEN coverage (e.g., satellite repairman inside a building without iDEN signal communi cating to a co-worker on the roof). - Contingency: should the network be down - Personal Emergency MOTOtalk is codeplug settable feature: it will only be available in the handset if it is turned on in the codeplug. Once enabled, MOTOtalk will be the last item in the main menu list. Valid record types for MT feature are all phone types: Mobile,Other, Work1, Work 2, and Home Accessing Contacts Figure 1-1 Accessing the Contacts 1.2 Traceability Requirement Sources Description Location/Version SRS for Contacts /vob/iden_doc/synergy_ergo/Requirements/Contacts_SRS.fm@@/main/213 SRS for MotoTalk /vob/iden_doc/synergy_ergo/Requirements/MotoTalk_Mode_SRS.fm@@/main/70 SRS for Recent Calls /vob/iden_doc/synergy_ergo/Requirements/Recent_Calls_SRS.fm@@/main/185 SRS for MSTG /vob/iden_doc/synergy_ergo/Requirements/MSTG_SRS.fm@@/main/12 References None Requirement toTest Case Mapping Requirement Test Number {CNTCTS_FORM}R[1] 1, 2, 3, 4, 4.1 {CNTCTS_FORM}R[2] 4, 4.2, 5, 5.1, 5.2, 5.3, 5.4, 5.5, 6, 7, 8, 10, 11, 12, 13, 14, {CNTCTS_FORM}R[3] 15, 15.1, 15.2, 15.3, 15.4 {CNTCTS_FORM}R[4] 16, 17, 18 {CNTCTS_FORM}R[5] 16, 16.1, 17, 17.1, 18, 18.1 {CNTCTS_FORM}R[6] 14.1, 14.2, 14.3, 14.4, 26, 26.1, 27, 27.1 {CNTCTS_FORM}R[7] 26, 28 {CNTCTS_FORM}R[8] 29 {CNTCTS_FORM}R[9] This requirement is crossed out in SRS document. {CNTCTS_FORM}R[10] 30, 31 {CNTCTS_FORM}R[11] 32 {CNTCTS_FORM}R[12] 19.1, 19.3 {CNTCTS_FORM}R[13] 19, 19.2, 20, 20.1 {CNTCTS_FORM}R[14] 19, 19.2, 21, 21.1, 21.3, 21.4 {CNTCTS_FORM}R[15] 33 {CNTCTS_FORM}R[16] This requirement is crossed out in SRS document. {CNTCTS_FORM}R[17] 22, 23 {CNTCTS_FORM}R[18] 22, 23 {CNTCTS_FORM}R[19] 24, 24.1, 25, 25.2 {CNTCTS_FORM}R[144] 34 {CNTCTS_FORM}R[145] 35 {CNTCTS_FORM}R[146] 36 {CNTCTS_FORM}R[149] 37, 39 {CNTCTS_FORM}R[150] 38, 40, 40.1 {CNTCTS_FORM}R[175] 21.2 {CNTCTS_FORM}R[211] 41.0, 41.1 {CNTCTS_FORM}R[212] 41.0, 41.1 {RECENT_CALLS}R[228] 41.0, 41.1 {RECENT_CALLS}R[406] 41.0, 41.1 {RECENT_CALLS}R[408] 41.0, 41.1 NRF 25.1 1.3 Acronyms/Terms/Abbreviations/Definitions Refer to: http:/compass.mot.com/go/iDR -> Software -> SWP0005 iDEN Standard Terminology Table1 Terminology Term Definition Aliased Entry Entry in the Contacts that has a name associated. In Contacts List View, a name will be displayed for such entry. Unaliased Entry Entry in the Contacts that does not have a name associated. In Contacts List View, a number will be displayed for such entry. Condor SIM (i3000, 32K) A new iDEN SIM which provides extra storage space for 250 dynamic Contacts entries besides the storage space provided by Endeavor SIM. When it is used by Condor subscriber, only 250 dynamic Contacts entries are accessible. CSM Context Sensitive Menu. It is presented when the user presses the Menu key. The menu item varies with the different state of the different feature. Detailed View The Detailed View in the Contacts shows all of the details of each entry including the Name (which appears as the title if entry is aliased), Number (appears as title if entry is not aliased), Speed Dial Number, Type Icon, and Voice Icon Entry Usually means all the information associated with one number. It may include a name, a type, a number, a speed number and a voice name. But in this document, sometimes it also means a record if there is no ambiguity in context External Display LCD display on the outside of the flip of some clamshell products. Falcon SIM (64K) An iDEN SIM which provides extra storage space for dynamic Contacts entries. The total number of dynamic Contacts entries ranges from 1 to 600. Extended Slots In Falcon SIM, the slots which can extend consolidated entries to store 64 digits for phone number fields or 32 characters for E-mail ID fields. The maximum number of Extended Slots is 200 and actual total number of Extended Slots also should be less than or equal to total number of Contact entries depending on actually used SIM. Suppose total number of Contacts entries is 300, actual total number of Extended Slots should be 200 or less. Suppose total number of Contacts entries is 100, actual total number of Extended Slots should be 100 or less.The maximum number of Extended Slots is 400. If the Contact Entry is long phone number, 2 extended slots will be used, regardless of the long number’s length. If the Contact Entry is Email ID, allocation of extended slots refer to Table 1-1. GSM SIM A standard SIM used by all GSM phones. It can have 0 to 255 phone entries, and the condor will only read the first 100 if there are more than 100 entries. The alias length can vary from 0 to 241, and the condor only read the first 11 characters. Internal Display Multi-line LCD display on inside of flip of clamshell products. For non-clamshell products, this refers to the main display by default. Endeavor SIM (i2000) An iDEN SIM which provides storage space for 100 phone number entries, 100 private IDs and 30 talkgroup IDs. Keypad Disable To the Contacts, this state means that the user is prohibited to add, modify or delete Contacts entry. List View The Contacts List View p resents a list of entries stored. LSK Left Softkey Contacts Capacity The maximum number of entries which the Contacts can store. Phone Memory The storage space locates in the SIM, in which the consolidated entry is stored. The consolidated entry is the entry that be associated with multi-type of numbers. It is allowed to attach a voice tag on a specific number within the entries stored in the Phone Memory Idle Screen Display state of phone when it is powered on. Record All the information associated with one person/name. RCL Recent Calls List RSK Right Softkey SIM Memory The storage space locates in the SIM which is apart from Phone Memory. The GSM 100 entries and the Endeavor compatible 100 Private ID, 30 Talkgroup ID are stored in this space. Each entry only has one number and no voice tag attached on it. Smart Key Key on clamshell products which is only usable while the clam is closed. Speed No The Speed Number is a unique ID assigned to each phone entry that refers to where it is stored in memory. Voice Name A piece of voice sample of the user used for voice recognition. KD Ctrl A flag in the codeplug to control the Keypad Disable behavior. There are two Keypad Disable settings in the codeplug--one is for Dispatch Service and the other one is for Interconnect Service. If KD Ctrl is turned on (the default setting), Keypad is considered locked when either the dispatch or the interconnect keypad is disabled in the codeplug. If KD Ctrl is turned off, dispatch and interconnect service will be controlled separately by the two Keypad Disable settings MMS MMS-Lite Multimedia Messaging Service A text-only version of MMS MT MOTOtalk is a feature that allows simple,direct,simplex two-way radio-to- radio,communications between subscriber units. iDEN MT mode When the phone is in iDEN MOTOtalk mode, it will not receive/transmit any iDEN signals. Phone Type The following are considered Phone Types: Mobile, Home, Work1, Work2, Other, Pager, and Fax SDG Selective Dynamic Group “Hub Masking” functionality This feature allows user to make legacy talkgroup calls in an AFU enabled handset , if “Hub Masking” feature is enabled. ( Refer MSTG SRS[39] ) Non-masked Hub A hub for which the Hub Id is outside of the Codeplug defined range for hub masking. ( Refer MSTG SRS[39] ) Masked Hub A hub for which the Hub Id is within the Codeplug defined range for hub masking. ( Refer MSTG SRS [39] ) Phoenix SIM An iDEN SIM which provides extra storage space for dynamic Contacts entries. The total number of dynamic Contacts entries ranges from 1 to 1200. The total number of Extended Slots is 800. Table 1-1 Allocation Table of Extended Slots Length of Email address Number of Extended Slots Used <=32 characters 2 extended slots used >32 characters and <=43 characters 3 extended slots used >43 characters and <=54 characters 4 extended slots used >54 characters and <=64 characters 5 extended slots used 1.4 Test Design List View Screen Elements List View will enable user to view brief information about Contacts Entries stored, sorted by Name. Figure1-2 List View Screen Element List View Sorted by Name Figure1-3 Contacts List View sorted by Name Detailed View Screen Element Figure1-4 Detailed View Screen Elements Detail View Sorting Rules Figure1-5 Detailed View Sorted by Name Storing Entries From Another Application Figure1-6 Memory Full Notices Matrix 1: Storing Entries From Another Application Test Case Setup Action1 Result1 Action2 Result2 1.0 None. From Idle Mode, enter a valid phone number and press MENU key. Verify unit enters the Dialing Menu screen. Select “Store” option. Verify unit enters “Store To”screen and user can store the number to New Contact. See Figure1-10 below. 2.0 Unit is in In-Call state with a non-stored number. Have at least one single phone entry stored. From In-Call screen, press MENU key. Verify unit enters the Call Menu. Select “Store” option. Verify unit enters “Store To” screen and user can store the number to an already existing entry. See Figure1-10 below. 3.0 Receive an SMS message with a valid phone number embedded. Read the message, press MENU key, and select “Store Number” from the options list. Verify unit enters “Store To” screen and user can store the number to New Contact See Figure1-10. N/A N/A 4.0 Have a non-stored private number in the Recent Calls List. Enter RCL, highlight number from setup, press MENU key and select “Store” option. Unit should enter “Store To” screen with “[New Contact]” highlighted. Select to store the number to “[New Contact]” Verify unit enters the New Entry Form, with private number to be stored displayed and type field set to Private. 4.1 Receive an MMS message from user whose phone number is not stored in Contacts. Read the message, press Menu key and select “Store” option. Verify user is taken to “Store To” screen, with [New Contact] highlighted. Select New Contact to store the number to. User should be able to store the number from MMS to Contacts. 4.2 Have two non-stored secure private numbers in the Recent Calls List. Contacts has at least one phone entry stored. 1. Enter RCL, highlight the first number from setup, press MENU key and select “Store” option. 2. Select to store the number to “[New Contact]” 1. Unit should enter “Store To” screen with “[New Contact]” highlighted. 2. Verify unit enters the New Entry Form, with Secure Private number to be stored displayed and type field set to Secure Private. 1. Assign a name and press “Done” softkey. 2. Exit to Idle, enter RCL, highlight the second entry from setup, press the MENU key, and select “Store” option. 3. Highlight and select the phone entry from Contacts, and from the Entry Form, press “Done” softkey. 1. Verify entry was properly stored in Contacts. 2. Unit should enter “Store To” screen again. 3. Verify user can store the secure private entry to already existing entry in Contacts. 5.0 Have a non-stored talkgroup number in the Recent Calls List. Enter RCL, highlight number from setup, press MENU key, and select “Store”. Unit should enter “Store To” screen with “[New Contact]” highlighted. Select to store the number to “[New Contact]” Verify unit enters the New Entry Form, with talkgroup number to be stored displayed and type field set to Talkgroup. 5.1 Have a non-stored Hub and a private type number in RCL. 1. Enter RCL, highlight the HUB type from setup, and press the “Store” softkey. (“Save” for Marlin) 2. Assign a name and press “Done” softkey. 1. Verify unit transitions directly to New Entry Form, with the type field set to Hub, and the number to be stored displayed in the number field. 2. Verify entry was properly stored in Contacts. 1. Exit to Idle. Ener RCL, highlight the private type from setup, press the MENU key, and select “Store”. 2. Select [New Contact], assign a name, and press “Done” softkey. 3. Press “No”. 4. Repeat steps and select “Yes” in the prompt. 1. Unit should enter “Store To” screen. 2. Verify unit displays “Copy to Secure Private?” screen, with “Yes” and “No” as LSK and RSK respectively. 3. Verify entry was stored to Contacts without copying the number to secure private type. 4. Verify entry was stored to Contacts, and the private number was copied to secure private type. 5.2 Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codelug (hub_masking_start_range set to 01) and set the talkgroup ending range to 200 in codeplug (hub_masking_end_range set to C8). Have a non-stored Talkgroup entry with TG ID 3 in the Recent Calls List. Enter RCL, highlight the Talkgroup entry from setup, press MENU key, and select “Store” (For Bluefin: select “Save”)option. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Talkgroup. Assign a name and press “Done” softkey. Verify entry is stored in Contacts. 5.3 Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 200 in codeplug (hub_masking_end_range set to C8). Receive an SMS message with a non-stored Talkgroup number (TG ID 4) embedded. Read the message, press MENU key, and select “Store Number”. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Talkgroup. Assign a name and press “Done” softkey. Verify entry is stored in Contacts. 5.4 Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 8 in codeplug (hub_masking_end_range set to 08). Have a non-stored Hub entry with TG ID 9 in the Recent Calls List. Enter RCL, highlight the Hub entry from setup, press MENU key, and select “Store” (For Bluefin: select “Save”) option. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Hub. Assign a name and press “Done” softkey. Verify entry is stored in Contacts. 5.5 Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 8 in codeplug (hub_masking_end_range set to 08). Receive an SMS message with a non-stored Hub number (Hub ID 9) embedded. Read the message, press MENU key, and select “Store Number”. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Hub. Assign a name and press “Done” softkey. Verify entry is stored in Contacts. 6.0 Have a non-stored phone number in the Recent Calls List. Enter RCL, highlight number from setup and press “Store” softkey. (“Save” for Marlin) Unit should enter “Store To” screen with “[New Contact]” highlighted. Select to store the number to “[New Contact]”. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type in the Type List (Mobile). 7.0 Have a non-stored phone number in the Recent Calls List. Have a multitype entry stored in Contacts. Enter RCL, highlight number from setup and press “Store” softkey. (“Save” for Marlin) Unit should enter “Store To” screen with “[New Contact]” highlighted. 1. Select to store the number to a multitype entry from setup. 2. Enter Type Editor. 1. Verify unit enters the Entry Form for multitype entry, with currently stored information present, the number to be stored displayed, and the type set to next available type from the Type List. 2. Already used types in multitype entry will not be shown in the Type Editor List. 8.0 Receive an SMS message with a valid IP address embedded. Read the message, press MENU key, and select the option to store the IP address. Verify unit enters “Store To” screen, with “[New Contact]” and currently stored entries displayed. Select to store it to New Contact. Verify New Entry Form is displayed, with IP address displayed in the IP field, and IP type in type field. 9.0 TBD; This cases was supposed to cover portion of R2, which is going to be addressed in the MMS Test Suite. 10.0 Have a non-stored phone number in the RCL. Enter RCL, highlight number from setup and press “Store” softkey. Unit should enter “Store To” screen with “[New Contact]” highlighted. 1. Select to store the number to “[New Contact]”. 2. Highlight type field, press “Change” softkey, and select the Private type. 1. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type from the Type List (Mobile). 2. Verify error message “Invalid Private ID” is displayed. 11.0 Have a non-stored phone number in the RCL. Enter RCL, highlight number from setup and press “Store” softkey. Unit should enter “Store To” screen with “[New Contact]” highlighted. 1. Select to store the number to “[New Contact]”. 2. Highlight type field, press “Change” softkey, and select the Talkgroup type. 1. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type from the Type List (Mobile). 2. Verify error message “Invalid Talkgroup ID” is displayed. 12.0 Have a non-stored phone number in the RCL. Enter RCL, highlight number from setup and press “Store” softkey. Unit should enter “Store To” screen with “[New Contact]” highlighted. 1. Select to store the number to “[New Contact]”. 2. Highlight type field, press “Change” softkey, and select the IP type. 1. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type from the Type List (Mobile). 2. Verify error message “Invalid IP Address” is displayed. 13.0 Have a non-stored phone number in the RCL. Enter RCL, highlight number from setup and press “Store” softkey. Unit should enter “Store To” screen with “[New Contact]” highlighted. 1. Select to store the number to “[New Contact]”. 2. Highlight type field, press “Change” softkey, and select the E-mail type. 1. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type from the Type List (Mobile). 2. Verify error message “Invalid E-mail ID” is displayed. 14.0 Receive an SMS message with an embedded IP address Read the message, press Menu key, and select option to Store IP address received. Unit should enter “Store To” record browser screen. 1. Select [New Contact] to store the IP address to. 2. Highlight type field, press “Change” softkey, and select any phone type. 1. Unit should enter New Entry Form. 2. Verify error message “Invalid Phone Number” is displayed. 14.1 Have a non-stored Talkgroup number in RCL. Use Condor/Falcon/(DS)Phoenix sim Enter RCL, highlight number from setup, and select Store from RCL Menu screen. Verify unit transitions to New Entry Form, with the number and Talkgroup type displayed. N/A N/A 14.2 Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 7 in codeplug (hub_masking_end_range set to 07). From Idle Dialer, enter #7, press MENU key, and select “Store Number” option. Verify unit transitions to New Entry Form screen, with number and Talkgroup type populating their respective fields. N/A N/A 14.3 Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 7 in codeplug (hub_masking_end_range set to 07). From Idle Dialer, enter #8, press MENU key, and select “Store Number” option. Verify unit transitions to New Entry Form screen, with number and Hub type populating their respective fields. N/A N/A 14.4 Use Phoenix SIM. Have a non-stored Talkgroup number in RCL. Enter RCL, highlight number from setup, and select Store from RCL Menu screen. Verify unit transitions to New Entry Form, with the number and Talkgroup type displayed. N/A N/A 15.0 N/A Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store” option. Unit should enter “Store To” screen with “[New Contact]” highlighted. Select “[New Contact]” to enter New Entry form for the number to be stored. Verify the type field is set to first available type from the Type List (Mobile). 15.1 Enter an invalid phone number, (like “P”or a 21-digit long number with no “P” and “W” characters) in the Idle Dialer Press MENU key, and select “Store” option. Unit should enter “Store To” screen with “[New Contact]” highlighted. Select “[New Contact]” to enter New Entry Form. Verify error message “Invalid Number” will be displayed 15.2 Use Phoenix SIM. Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store” option. Unit should enter “Store To” screen with “[New Contact]” highlighted. Select “[New Contact]” to enter New Entry form for the number to be stored. Verify the type field is set to first available type from the Type List (Mobile). 15.3 Use Phoenix SIM. Enter an invalid phone number, (like “P”or a 21-digit long number with no “P” and “W” characters) in the Idle Dialer Press MENU key, and select “Store” option. Unit should enter “Store To” screen with “[New Contact]” highlighted. Select “[New Contact]” to enter New Entry Form. Verify error message “Invalid Number” will be displayed 15.4 Use Falcon/Phoenix sim Have some TG, SDG, Msg Group & any other type of entries stored Enter a valid number in Idle, press CSM & select “Store Number” Unit should enter “Store To” screen with “[New Contact]” highlighted. Verify no TG, SDG & Msg Group entries listed Select “[New Contact]” to enter New Entry form for the number to be stored. Verify the type field is set to first available type from the Type List (Mobile). 16.0 Have a non-stored phone number in the RCL. Use Condor/Falcon/(DS)Phoenix sim Enter RCL, highlight number from setup and press “Store” softkey. (“Save” for Marlin) Unit should enter “Store To” Record Browser screen with “[New Contact]” highlighted. Store this number to a New Contact. Verify after the number is stored, unit will return to RCL. 16.1 Use Phoenix SIM. Have a non-stored phone number in the RCL. Enter RCL, highlight number from setup and press “Save”. Unit should enter “Store To” Record Browser screen with “[New Contact]” highlighted. Store this number to a New Contact. Verify after the number is stored, unit will return to RCL. 17.0 Use Condor/Falcon/(DS)Phoenix sim Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store” option. Unit should enter “Store To” Record Browser screen with “[New Contact]” highlighted. Store this number to a New Contact. Verify after the number is stored, unit will return to Idle Dialer, with the number still displayed. 17.1 Use Phoenix SIM. Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store” option. Unit should enter “Store To” Record Browser screen with “[New Contact]” highlighted. Store this number to a New Contact. Verify after the number is stored, unit will return to Idle Dialer, with the number still displayed. 18.0 Receive an SMS message with a valid phone number embedded. Use Condor/Falcon/(DS)Phoenix sim Read the message, press MENU key, and select “Store Number” opton. Verify unit enters “Store To” Record Browser screen, with “[New Contact]” displayed. Store this number to a New Contact. Verify after the number is stored, unit will return to the message screen. 18.1 Use Phoenix SIM. Receive an SMS message with a valid phone number embedded. Read the message, press MENU key, and select “Store Number” opton. Verify unit enters “Store To” Record Browser screen, with “[New Contact]” displayed. Store this number to a New Contact. Verify after the number is stored, unit will return to the message screen. 19.0 Empty contacts of all entries. Store 100 phone numbers with 64 digits in length and 100 E-mail IDs with 32 characters in length. Attempt to store one more phone number entry with 64 digits in length. Verify user will not be able to store another entry of this length, and error message will post. Attempt to store one more E-mail ID entry with 32 characters in length. Verify user will not be able to store another entry of this length, and error message will post. 19.1 Exhaust the SIM memory by storing maximum number of entries to Contacts. Have a non-stored phone number in RCL. From RCL, highlight the number from setup, and press “Store” softkey. (“Save” for Marlin) Verify transient notice “Contacts Full” is displayed, which times out to RCL. N/A N/A 19.2 Use Phoenix SIM. Empty contacts of all entries. Store 200 phone numbers with 64 digits in length and 200 E-mail IDs with 32 characters in length. Attempt to store one more phone number entry with 64 digits in length. Verify user will not be able to store another entry of this length, and error message will post. Attempt to store one more E-mail ID entry with 32 characters in length. Verify user will not be able to store another entry of this length, and error message will post. 19.3 Use Phoenix SIM. Exhaust the SIM memory by storing 1200 of entries to Contacts. Have a non-stored phone number in RCL. From RCL, highlight the number from setup, and press “Save” Verify transient notice “Contacts Full” is displayed, which times out to RCL. N/A N/A 20.0 Have 400 entries of normal length (20 digits or less) stored. Attempt to store another entry of normal length to Contacts. Verify user is allowed to store this entry. Note: this entry will utilize the space of the extended slots designated for 64-digit and 32-character entries. N/A 20.1 Use Phoenix SIM. Have 400 entries of normal length (20 digits or less) stored. Attempt to store another entry of normal length to Contacts. Verify user is allowed to store this entry. Note: this entry will utilize the space of the extended slots designated for 64-digit and 32-character entries. N/A 21.0 Have 200 phone entries of 64 digits in length stored in Contacts to exhaust the Extended Slots space. Attempt to store one more phone number entry with 64 digits in length. Verify “Long Number Memory Full” transient message is displayed, which times out back to previous screen. N/A N/A 21.1 Have 200 E-mail ID entries with 32 characters in length stored in Contacts to exhaust the Extended Slots space. Attempt to store one more entry of 21 digits in length Verify “Long Number Memory Full” transient message is displayed, which times out back to previous screen. N/A N/A 21.2 MS1 (non test unit) has two aliased SDG entries stored; one of them has 3 private id numbers. MS2’s SDG capacity is not exhausted. 1.From MS1, send an iCard with first SDG type entry to MS2 (test unit) 2. Select to store this iCard on MS2. 1. MS2 should receive the SDG iCard, and it should appear in RCL. 2. Verify unit transitions straight to SDG Storing Form, with the correct data from iCard populated. 1.Exit to Idle. On MS2, exhaust the SDG capacity (there are 25 SDG entries with 20 members in each). From MS1, send an iCard with the second SDG type entry that contains 3 private id numbers. 2. On MS2, enter RCL and select to store this iCard. (“Save” for Marlin) 1. MS2 should receive the second iCard, and it should be stored in RCL. 2. Verify transient notice posts: the first line will have “Unable to Store:” and the second line will have “Space Exceeded”. Transient notice shoud time out back to RCL. 21.3 Use Phoenix SIM. Have 400 phone entries of 64 digits in length stored in Contacts to exhaust the Extended Slots space. Attempt to store one more phone number entry with 64 digits in length. Verify “Long Number Memory Full” transient message is displayed, which times out back to previous screen. N/A N/A 21.4 Use Phoenix SIM. Have 400 E-mail ID entries with 32 characters in length stored in Contacts to exhaust the Extended Slots space. Attempt to store one more entry of 21 digits in length Verify “Long Number Memory Full” transient message is displayed, which times out back to previous screen. N/A N/A Matrix 1 Notes: None. Storing Entries Using the Contacts Menu Figure1-7 Storing Entries Using the Contacts Menu Matrix 2: Storing Entries Using the Contacts Menu Test Case Setup Action1 Result1 Action2 Result2 22.0 N/A From Idle Mode, enter Contacts List View, press MENU key and select “New” Verify unit enters the New Entry Form. See Figure1-7. Enter Name, Number, and Type for this entry and press “Done” softkey. Verify unit returns to List View with the newly stored entry highlighted. See Figure1-7. 23.0 Have at least one entry stored in Contacts. Enter Detailed View for entry from setup, press MENU key, and select “New”. Verify unit enters the New Entry Form. Enter Name, Number, and Type for this entry and press “Done” softkey. Verify unit returns to Detailed View for the newly stored entry. Matrix 2 Notes: None. Storing Multiple Numbers Associated with a Single Name Matrix 3: Storing Multiple Numbers Associated with a Single Name Test Case Setup Action1 Result1 Action2 Result2 24.0 N/A Enter Contacts List View, press MENU key, and select “New”. Verify unit enters the New Entry Form. See Figure1-7. Enter the Name, and for all of the available types, enter Number and Type in their respective fields, and press “Done” softkey. Verify unit returns to List View with newly stored multitype entry highlighted. Verify all of the types are stored by scrolling Left/Right. See Figure1-8 for details. 24.1 Use Phoenix SIM. Enter Contacts List View, press MENU key, and select “New”. Verify unit enters the New Entry Form. See Figure1-7. Enter the Name, and for all of the available types, enter Number and Type in their respective fields, and press “Done” softkey. Verify unit returns to List View with newly stored multitype entry highlighted. Verify all of the types are stored by scrolling Left/Right. See Figure1-8 for details. 25.0 Have at least one entry stored in Contacts. Enter Contacts Detailed View for entry from setup, press MENU key, and select “New”. Verify unit enters the New Entry Form. Enter the Name, and for all of the available types enter Number and Type in their respective fields, and press “Done” softkey. Verify unit returns to Detailed View with first record of newly stored multitype entry displayed (Mobile). Verify all of the types are stored by scrolling Up/Down. 25.1 Using RSS, enable the Direct Connect Display bit. Have at least one DC type of entry stored in Contacts. 1. Enter Contacts New Entry Form, highlight the Type field and enter Type Editor List. 2. Exit to Idle, and enter the Entry Form for specified DC type of entry from setup. 1. Verify DC (Direct Connect) is displayed in the list. 2. Verify DC is displayed in the Type field. Use RSS to disable the Direct Connect Display bit, and repeat the test. Verify the string “Private” has replaced “DC” in the type field and Type Editor List. 25.2 Use Phoenix SIM. Have at least one entry stored in Contacts. Enter Contacts Detailed View for entry from setup, press MENU key, and select “New”. Verify unit enters the New Entry Form. Enter the Name, and for all of the available types enter Number and Type in their respective fields, and press “Done” softkey. Verify unit returns to Detailed View with first record of newly stored multitype entry displayed (Mobile). Verify all of the types are stored by scrolling Up/Down. Matrix 3 Notes: None. Figure1-8 Storing Multiple Number Record Condor (i3000), GSM, and Endeavor (i2000) SIM Cases Matrix 4: Condor, GSM, and Endeavor (i2000) SIM Cases Test Case SIM Used/Setup Action1 Result1 Action2 Result2 26.0 GSM/Endeavor SIM. Have a non-stored phone number in RCL. From RCL, highlight the number from setup, and press “Store” softkey (“Save” for Marlin) Verify unit transitions to New Entry Form, with number and Main type populating their respective fields. Replace the GSM SIM with Endeavor SIM and repeat the test. Verify the same results. 26.1 Phoenix SIM. Have a non-stored phone number in RCL. From RCL, highlight the number from setup, and press “Save”. Verify unit transitions to New Entry Form, with number and Main type populating their respective fields. N/A N/A 27.0 Endeavor SIM. Have non-stored Private ID number and a Talkgroup number in RCL. From RCL, highlight the Private number from setup, enter RCL Menu, and select Store option. Verify unit transitions to New Entry Form, with number and Private/DC type populating their respective fields. Return to RCL, highlight the Talkgroup number from setup, enter RCL Menu, and select Store option Verify unit transitions to New Entry Form, with number and Talkgroup type populating their respective fields. 27.1 Phoenix SIM. Have non-stored Private ID number and a Talkgroup number in RCL. From RCL, highlight the Private number from setup, enter RCL Menu, and select Store option. Verify unit transitions to New Entry Form, with number and Private/DC type populating their respective fields. Return to RCL, highlight the Talkgroup number from setup, enter RCL Menu, and select Store option Verify unit transitions to New Entry Form, with number and Talkgroup type populating their respective fields. 28.0 GSM SIM. Exhaust the SIM memory by storing maximum number of entries to Contacts. Have a non-stored phone number in RCL. From RCL, highlight the number from setup, and press “Store” softkey (“Save” for Marlin) Verify transient notice “Contacts Full” is displayed, which times out back to RCL. N/A N/A 29.0 GSM/Endeavor SIM. Receive an SMS message with embedded IP address, and proceed to store this IP address to Contacts. Verify transient notice “Can’t store IP Address” is displayed. Replace the GSM SIM with Endeavor SIM and repeat the test. Verify the same results. 30.0 Endeavor SIM. Completely fill Private and Talkgroup lists of the SIM. Have non-stored Private and Talkgroup numbers in RCL. From RCL, highlight Private number from setup, enter RCL Menu, and select Store option. Verify transient notice “Private/DC List Full” is displayed. Return to RCL, highlight Talkgroup number from setup, enter RCL Menu, and select Store option. Verify transient notice “Talkgroup List Full” is displayed. 31.0 Endeavor SIM. Completely fill Phone list of the SIM. Have a non-stored phone number in RCL. From RCL, highlight Phone number from setup, and press “Store” softkey. (“Save” for Marlin) Verify transient notice “Phone List Full” is displayed. N/A N/A 32.0 Endeavor SIM. Exhaust the SIM memory by storing maximum number of entries to Contacts for all three types. Have a non-stored phone number in RCL. From RCL, highlight Phone number from setup, and press “Store” softkey. (“Save” for Marlin) Verify transient notice “Contacts Full” is displayed, which times out back to RCL. N/A N/A 33.0 GSM/Endeavor/Condor SIM. Have a non-stored phone number in RCL that exceeds 20 digits in length. From RCL, highlight number from setup, and press “Store” softkey. (“Save” for Marlin) Verify transient notice “Can’t Store Long Number” is displayed, which times out back to RCL. 1. Replace the GSM SIM with Endeavor SIM and repeat the test. 2. Replace the Endeavor SIM with Condor SIM and repeat the test. 1. Verify same results. 2. Verify same results. Matrix 4 Notes: None. MOTOtalk “MOTOtalk” feature is part of the Main menu of the Falcon Ergonomics. It is a PTT based feature that operates like most two way radios. MOTOtalk is codeplug settable feature: it will only be available in the handset if it is turned on in the codeplug. Once enabled, MOTOtalk will be the last item in the main menu list. Valid record types for MT feature are all phone types: Mobile, Other, Work1, Work 2, and Home. This order is also the priority order for assigning numbers. Preconditions: Unit is in MT mode at the beginning of each test. To place the unit in MT mode, MOTOtalk bit must be enabled in the codeplug. Once enabled, user will be able to select MT from the Main Menu. Matrix 5: MOTOtalk Test Cases Test Case Setup Action 1 Result 1 Action 2 Result 2 34.0 Use GSM/Endeavor SIM. Enter a valid phone number in Idle Dialer, press MENU key and select “Store Number” option. Verify unit enters the new entry form, with the number filled in the number field, and type field set to “Main”. N/A N/A 35.0 Have at least one phone number in RCL. Store one entry that has all MT types occupied and one “Other” type of entry. From RCL, highlight # from setup, press Store softkey, and select the full entry from setup. Verify transient notice “All types full” displays and unit returns to RCL. Press Store softkey again, and select the “Other” type entry to store the number to. Verify unit enters the entry form, with number filled in, and its type set to “Mobile”. 36.0 Have at least one Private ID number in RCL. From RCL, highlight the private number, press MENU key, and select “Store” option. Verify unit enters the entry form with the number populating the corresponding field, and type set by default. N/A N/A 37.0 Store one two “Home” type of entries to contacts. Have a non-stored phone number in RCL. Use Condor/Falcon/(DS)Phoenix sim Enter RCL and select to store the number from setup to an existing the first “Home” type of entry from setup. Verify unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Mobile” by default. Exit to idle. Enter a valid phone number in the Idle Dialer and select to store it to the same second “Home” type of entry from setup. Verify unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Mobile” by default. 38.0 Have one multitype entry with “Mobile” and “Other” types stored. Have one multitype entry with “Mobile, Other, and Work1” stored. Have a non-stored phone number in RCL. Use Condor/Falcon/(DS)Phoenix sim Enter RCL and select to store the number from setup to existing, multitype entry. Verify “Cannot store number in Mobile” trans. notice shows, and unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Work1” by default. Exit to idle. Enter a valid phone number in the Idle Dialer and select to store it to the second multitype entry from setup. Verify “Cannot store number in Mobile” trans. notice shows, and unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Work2” by default. 39.0 Store one “Work1” type of entry to contacts. Have a non-stored phone number in RCL, with phone type. Use Condor/Falcon/(DS)Phoenix sim Enter RCL and select to store the number from setup to an existing, “Work1” type of entry. Verify unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Mobile” by default. N/A N/A 40.0 Have one multitype entry with “Mobile, Work1, and Home” types stored. Have a non-stored phone number in RCL, with phone type. Use Condor/Falcon/(DS)Phoenix sim Enter RCL and select to store the number from setup to existing, multitype entry. Verify “Cannot store number in Mobile” trans. notice shows, and unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Other” by default. N/A N/A 40.1 Have one multitype entry with “Mobile, Work1, Work2 and Home” types stored. Have a non-stored phone number in RCL, with phone type. Use Condor/Falcon/(DS)Phoenix sim Phone in MT mode Enter RCL and select to store the number from setup to existing, multitype entry. Verify “All types full” notice & times out to RCL N/A N/A Matrix 5 Notes: Figure1-9 describes accessing and activating MOTOtalk feature. The type priority when assigning numbers is: Mobile, Other, Work1, Work2, and Home. If Mobile is already existing, Other will be displayed in the form by default. If both Other and Mobile are existing, Work1 will be the default, etc. Figure1-9 Accessing MOTOtalk feature Prefix Cases Matrix 6: Prefix Cases Test Case SIM Used/Setup Action1 Result1 Action2 Result2 41.0 On MS1, enter “Store Received Info” feature from Main Menu -> Settings -> 2-Way Radio. Set “Add Prefix” to “Ask Me” and make sure “Prefix” is not empty. MS2 is number is not stored in Contacts of MS1. MS2 uses Alt line SIM to have both Line1 and Line2 info. 1. From MS2, enter My Info from Main Menu and press Menu key. Highlight “Send My Info via PTT” “Send via PTT” and press Ok key. 2.Enter MS1 private id and press Ok key.Press PTT key once to send MyInfo iCard to MS1. 3.On MS1, highlight the received MyInfo iCard in RCL and press Menu key. Select “Store” by pressing Ok key. LSK “Save” 4.Press Yes softkey. Select [New Contact]. 1.Verify MS2 enters “Send To:” text editor. 2.Verify unit enters RCL after MyInfo iCard is sent over to MS1. 3.Verify confirmation notice “Add Phone Number Prefix?” as Line 1 and “xxx” as Line 2 is displayed. 4.Verify that prefix will be added automatically to the interconnect numbers of Line1 and Line2 when the New Contact form is popped up. 1.Enter an alias in the Name: field. Press Save softkey. 2. Delete the entry that was saved in step1 Action2. Repeat step 1-3 in Action1 column. 3.Press No softkey.Select [New Contact]. 4.Press Save(Marlin, Mango Key2, Majua) or Done(Cobia) softkey. 1.Verify MS1 returns to RCL highlighting the contact that is just stored. 2. Verify the same outcome. 3.Verify that prefix will not be added to the interconnect numbers when the New Contact form is popped up 4.Verify MS1 returns to RCL highlighting the contact that is just stored. 41.1 Have at least 2 entries stored in Contacts. On MS1, enter “Store Received Info” feature from Main Menu -> Settings ->2-Way Radio. Set “Add Prefix” to “Ask Me” and make sure “Prefix” is not empty. 1.Place a private call from MS2 to MS1. When MS2 is in an active private call, press PTT once to send MyInfo iCard to MS1. 2.On MS1, highlight the received MyInfo iCard in RCL and press Menu key. Select “Store” by pressing Ok key. LSK “Save” 3.Press Yes softkey.Select a contact. 1.Verify unit enters RCL after private call is ended. 2.Verify confirmation notice “Add Phone Number Prefix?” as Line 1 and “xxx” as Line 2 is displayed. 3.Verify that prefix will be added automatically to the interconnect numbers when the New Contact form is popped up 1.Press Save softkey. 2. Repeat step 1-3 in Action1 column. 3.Press No softkey.Select another contact. 4.Press Save(Marlin, Mango Key2, Majua) or Done(Cobia) softkey. 1.Verify MS1 returns to RCL highlighting the contact that is just stored 2. Verify the same outcome. 3.Verify that prefix will not be added to the interconnect numbers when the Contact form is popped up. 4.Verify MS1 returns to RCL highlighting the contact that is just stored Matrix 6 Notes: None. Figure1-10 Storing Entries from the Dial Screen 2 Procedure Section 2.1 Description This section provides a step-by-step test execution of Detailed View related features for Contacts. Receiving an SMS message: 1. Access http://plnt813.comm.mot.com/testsys/request/index.html 2. Select Send SMS Message option to open iDEN SMS Message Form. 3. If option Phone is selected in the Type filed, enter 10 digits phone number in the The Number field. If option PvtID is selected in the Type field, enter private ID number in The Number the field. 4. Type the text message in the field Message: 5. Click the Send after the message is ready to send. Falcon SIM Capacities: Falcon SIM has the capacity of 600 entries. It is broken down the following way: 1. 200 slots are designated for entries of 64-digit phone numbers and 32-character E-mail IDs. These are considered to be extended slots. 2. 400 slots are designated for entries of normal length. Phone numbers with 20 digits or less and other type of numbers are considered to be normal length numbers. 2.2 Acronyms/Terms/Abbreviations/Definitions Refer to:http://compass.mot.com/go/iDR -> Software -> SWP0005 iDEN Standard Terminology 2.3 Initial Conditions/Setup - Individual Test Setup is described, as necessary, within the test cases. - By default, Contacts will be sorted by Name. - All of the test cases are written for Marathon and Largo platforms. If certain test case is applicable only to one platform, it will be indicated in the title of the test case. - All of the test cases are written to support the 64K Falcon SIM. If test case is exclusively applicable to Condor (i3000), GSM, or Endeavor (i2000) SIM, it will be indicated in the title of the test case. - If DC (Direct Connect) display bit is turned ON in the codeplug, Private type will be displayed as “DC”. If DC bit is turned OFF, Private type will be displayed as “Private”. - For Largo features like Speakerphone, Voice Notes, and Voice Recognition are optional. They can be enabled/disabled in the codeplug using RSS. Test Cases will specify in the setup section whether a feature needs to be enabled for Largo. Table of Icons Table2 below shows available icons for Contacts Feature. Table2 Contacts Icons 2.4 Test Procedures Storing Entries From Another Application __1.0 This test verifies selecting “Store” from Dialing Menu will display “Store To” record __1.0 browser screen and will store the number to Contacts. SETUP: None. 1. From Idle Mode, enter a valid phone number and press MENU key. 2. Verify unit enters the Dialing Menu screen. 3. Select “Store Number” option. 4. Verify unit enters “Store To” record browser screen. 5. LSK should be blank (Marathon step only). 6. Press LSK and verify a dead keypress results; nothing should change (Marathon step only.) 7. Choose “[New Contact]” to store the number to. 8. Verify New Entry Form is displayed, with the number to be stored displayed. 9. Pick any type, assign alias to this entry, and press “Done” / ”Save” softkey. 10. Enter Contacts List View and verify entry was stored to Contacts. __2.0 This test verifies selecting “Store” from Call Menu will display “Store To” record browser screen and will store the number to Contacts. SETUP: Unit is in the In-Call state with a number that is not stored in Contacts. Have at least one single type of entry stored. 1. From In-Call screen, press MENU key. 2. Verify unit enters In Call Menu. 3. LSK should be blank (Marathon only step). 4. Press LSK and verify a dead keypress results; nothing should change (Marathon only step). 5. Select “Store” option. 6. Verify unit enters “Store To” record browser screen. 7. Choose an already existing single entry from contacts to store the number to. 8. Verify Entry Form is displayed with the number to be stored displayed, along with already existing information for the entry. 9. Pick any type and press “Done” / ”Save” softkey. 10. Verify entry is stored in Contacts and unit returns to In Call screen with the Name of the entry displayed. __3.0 This test verifies user can store the number from SMS message. SETUP: Receive an SMS message with a valid phone number embedded. 1. Read the message, press MENU key, and select “Store Number” from the options list. 2. Verify unit enters “Store To” record browser screen. 3. Choose “[New Contact]” to store the number to. 4. Verify New Entry Form is displayed, with the number to be stored displayed. 5. Pick any type, assign a name, and press “Done” / ”Save” softkey. 6. Verify entry is stored in Contacts. __4.0 This test verifies when storing a private number to Contacts, Private type will default to type field in the New Entry Form. SETUP: Have a non-stored private id number in the Recent Calls List. 1. Enter Recent Calls List screen. 2. Highlight number from setup, press MENU key and select “Store” option. 3. Unit should enter “Store To” record browser screen, with “[New Contact]” highlighted. 4. Select to store the number to “[New Contact]”. 5. Verify unit enters the New Entry Form, with private number to be stored displayed and type field set to Private (or DC if DC bit is set to ON). 6. Enter a Name in the name field and press “Done” / ”Save” softkey. 7. Verify entry is stored in Contacts. __4.1 This test verifies user can store the number from MMS message. SETUP: Receive an MMS message from a user whose number is not stored in Contacts. 1. Read the message, press MENU key, and select “Save Number” from the options list. 2. Verify unit enters “Store To” record browser screen. 3. Choose “[New Contact]” to store the number to. 4. Verify New Entry Form is displayed, with the number to be stored displayed. 5. Pick any type, assign a name, and press “Done” / ”Save” softkey. 6. Verify entry is stored in Contacts, and unit returns back to message screen. __4.2 This test verifies when storing a Secure Private number to Contacts, the type field will default to Secure Private type. SETUP: Have two non-stored Secure Private type number in Recent Calls List. Contacts has at least one aliased phone entry stored. 1. Enter RCL, highlight the first number from setup, press the MENU key, and select “Store” option. 2. Verify unit transitions to the Store To screen, with “[New Contact]” highlighted. 3. Select to store the number to “[New Contact]”. 4. Verify unit enters the New Entry Form, with Secure Private number to be stored displayed and the type field set to Secure Private. 5. Assign a name and press “Done” softkey. 6. Verify entry was properly stored in Contacts. 7. Exit to Idle. Enter RCL again, highlight the second entry from setup, press the MENU key, and select “Store” option. 8. Unit should enter “Store To” screen. 9. Highlight and select the phone entry from Contacts. 10. Unit should enter the Entry Form with all stored data displayed. 11. Press “Done” softkey. 12. Verify user can store a secure private entry to already existing entry in Contacts. Verify the secure private type icon is now displayed for this entry. __5.0 This test verifies when storing Talkgroup number to Contacts, type field will default to Talkgroup. SETUP: Have a non-stored talkgroup number in the Recent Calls List. 1. Enter RCL, highlight number from setup, press MENU key, and select “Store” option. 2. Verify unit enters the New Entry Form, with talkgroup number to be stored displayed and the type field set to Talkgroup 3. Assign a name and press “Done” / ”Save” softkey 4. Verify entry is stored in Contacts. __5.1 This test verifies when storing Hub number to Contacts, type field will default to Hub type. SETUP: Have a non-stored Hub and two non-stored Private type numbers in the Recent Calls List. 1. Enter RCL, highlight the HUB number from setup, press MENU key, and select “Store” option. 2. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Hub. 3. Assign a name and press “Done” softkey. 4. Verify entry is stored in Contacts. NOTE: Continue with steps below if testing with the unit that supports Encryption. 5. Exit to Idle. Enter RCL, highlight the first private type from setup, press the MENU key, and select “Store”. 6. Unit should enter “Store To” screen. 7. Select [New Contact], assign a name, and press “Done” softkey. 8. Verify unit displays “Copy to Secure Private?” screen, with “Yes” and “No” as LSK and RSK respectively. 9. Press “No”. 10. Verify entry was stored to Contacts without copying the number to secure private type; entry should not have the secure private type stored. 11. Repeat steps 5 - 8. 12. Press “Yes”. 13. Verify entry was stored to Contacts, and the private number was copied to secure private type; entry should now have private and secure private types stored. __5.2 This test verifies when storing Talkgroup number from RCL to Contacts, type field will default to Talkgroup type. SETUP: Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 200 in codeplug (hub_masking_end_range set to C8). Have a non-stored Talkgroup entry with TG ID 3 in the Recent Calls List. 1. Enter RCL, highlight the Talkgroup entry from setup, press MENU key, and select “Store” (For Bluefin: select “Save”) option. 2. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Talkgroup. 3. Assign a name and press “Done” softkey. 4. Verify entry is stored in Contacts. __5.3 This test verifies when storing Talkgroup number from SMS Message to Contacts, type field will default to Talkgroup type. SETUP: Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 200 in codeplug (hub_masking_end_range set to C8). Receive an SMS message with a non-stored Talkgroup number (TG ID 4) embedded. 1. Read the message, press MENU key, and select “Store Number”. 2. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Talkgroup. 3. Assign a name and press “Done” softkey. 4. Verify entry is stored in Contacts. __5.4 This test verifies when storing Hub number from RCL to Contacts, type field will default to Hub type. SETUP: Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 8 in codeplug (hub_masking_end_range set to 08). Have a non-stored Hub entry with TG ID 9 in the Recent Calls List. 1. Enter RCL, highlight the Hub entry from setup, press MENU key, and select “Store” (For Bluefin: select “Save”) option. 2. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Hub. 3. Assign a name and press “Done” softkey. 4. Verify entry is stored in Contacts. __5.5 This test verifies when storing Hub number from SMS Message to Contacts, type field will default to Hub type. SETUP: Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 8 in codeplug (hub_masking_end_range set to 08). Receive an SMS message with a non-stored Hub number (Hub ID 9) embedded. 1. Read the message, press MENU key, and select “Store Number”. 2. Verify unit enters the New Entry Form, with the number to be stored displayed in the number field, and the type field set to Hub. 3. Assign a name and press “Done” softkey. 4. Verify entry is stored in Contacts. __6.0 This test verifies when storing a phone number to Contacts, type field will default to first available type in the list and that it will not be blank. It also verifies user can select the __6.0 type from the Type editor. SETUP: Have a non-stored phone number in the RCL. 1. Enter RCL, highlight number from setup, and press “Store” softkey.(“Save” for Marlin) 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the number to New Contact. 4. Verify unit enters the New Entry Form, with the phone number to be stored displayed and the type field set to first available type in the Type Editor List (Mobile). __7.0 This test verifies user can store a number to an existing multitype record. It also verifies user can select the next available type in the Type Editor list, and that used types will not be displayed in the list. SETUP: Have a non-stored phone number in the RCL. Have a multitype entry stored in the Contacts. Multitype entry is not completely filled. 1. Enter RCL, highlight number from setup, and press “Store” softkey. (“Save” for Marlin) 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the number to a multitype entry from setup. 4. Verify unit enters the Entry Form for multitype entry, with currently stored information present, the phone number to be stored displayed, and the type field set to the next available type in the Type Editor List. 5. Enter Type Editor. 6. Already used types in the multitype entry will not be shown in the Type Editor List. 7. Return to Entry Form. 8. Press “Done” / ”Save” softkey. 9. Verify new record has been added to multitype entry. Note: The type hierarchy in the Type Editor list is as follows: • Mobile • DC (Direct Connect) if DC bit is enabled; Private if DC bit is not enabled • Work1 • Work2 • Home • E-mail (shall be removed if a Condor SIM is inserted) • Fax • Pager • Talkgroup (will not be shown for multitype entry) • IP • Other __8.0 This test verifies when storing an IP address from SMS message, type field will default to IP. SETUP: Receive an SMS message with embedded valid IP address. 1. Read the message, press MENU key, and select the option to store the IP address. 2. Verify unit enters “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the IP Address to New Contact. 4. Verify New Entry Form is displayed, with IP address displayed in the IP field, and IP type in the type field. 5. Assign a name and press “Done” / ”Save” softkey. 6. Verify IP entry is stored in Contacts. __9.0 This test was supposed to cover storing an E-mail ID from another application to Contacts, and it cannot be addressed here. This part of requirement {CNTCTS_FORM} R[2] is going to be covered in MMS Test Suite. __10.0 This test verifies an error message “Invalid Private ID” will post when attempting to store a phone number to a private type. SETUP: Have a non-stored phone number in the RCL. 1. Enter RCL, highlight number from setup, and press “Store” softkey. 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the number to New Contact. 4. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type in the Type Editor List. 5. Highlight type field, press “Change” softkey, and select the Private type. 6. Verify error message “Invalid Private ID” is displayed. __11.0 This test verifies an error message “Invalid Talkgroup ID” will post when attempting to store a phone number to a Talkgroup type. SETUP: Have a non-stored phone number in the RCL. 1. Enter RCL, highlight number from setup, and press “Store” softkey. 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the number to New Contact. 4. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type in the Type Editor List. 5. Highlight type field, press “Change” softkey, and select the Talkgroup type. 6. Verify error message “Invalid Talkgroup ID” is displayed. __12.0 This test verifies an error message “Invalid IP Address” will post when attempting to store a phone number to an IP type. SETUP: Have a non-stored phone number in the RCL. 1. Enter RCL, highlight number from setup, and press “Store” softkey. 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the number to New Contact. 4. Verify unit enters the New Entry Form, with phone number to be stored displayed and type field set to first available type in the Type Editor List. 5. Highlight type field, press “Change” softkey, and select the IP type. 6. Verify error message “Invalid IP Address” is displayed. __13.0 This test verifies an error message “Invalid E-mail ID” will post when attempting to store a phone number to an Email ID type. SETUP: Have a non-stored phone number in the RCL. 1. Enter RCL, highlight number from setup, and press “Store” softkey. 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select to store the number to New Contact. 4. Verify unit enters the New Entry Form, with phone number to be stored displayed and 4. type field set to first available type in the Type Editor List. 5. Highlight type field, press “Change” softkey, and select the E-mail type. 6. Verify error message “Invalid E-mail ID” is displayed. __14.0 This test verifies an error message “Invalid Phone Number” will post when attempting to store an invalid phone number to a Phone type. SETUP: Receive an SMS message with an embedded valid IP address 1. Read the message, press Menu key to enter Inbox Menu screen, and select option to Store IP address received. 2. Unit should enter the “Store To” record browser screen. Select New Contact to enter the New Entry Form. 3. Highlight type field, press “Change” softkey, and select any phone type. 4. Verify error message “Invalid Phone Number” is displayed. __14.1 This test verifies number and type will be automatically entered into Entry Form when quickstoring a Talkgroup number. SETUP: None.Use Condor/Falcon/(DS)Phoenix sim 1. From Idle Dialer, enter a valid Talkgroup number, press MENU key, and select “Store Number” option. 2. Verify unit transitions to New Entry Form screen, with number and Talkgroup type populating their respective fields. __14.2 This test verifies when “Hub Masking” feature is enabled, number and type will be automatically entered into Entry Form when quickstoring a Talkgroup number. SETUP: Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 7 in codeplug (hub_masking_end_range set to 07). 1. From Idle Dialer, enter #7, press MENU key, and select “Store Number” option. 2. Verify unit transitions to New Entry Form screen, with number and Talkgroup type populating their respective fields. __14.3 This test verifies when “Hub Masking” feature is enabled, number and type will be automatically entered into Entry Form when quickstoring a Hub number. SETUP: Using CPedit, set afu_enable and hub_masking_enable fields to 1 in codeplug to enable “Hub Masking”. Also, set the talkgroup starting range to 1 in codeplug (hub_masking_start_range set to 01) and set the talkgroup ending range to 7 in codeplug (hub_masking_end_range set to 07). 1. From Idle Dialer, enter #8, press MENU key, and select “Store Number” option. 2. Verify unit transitions to New Entry Form screen, with number and Hub type populating their respective fields. __14.4 This test verifies number and type will be automatically entered into Entry Form when quickstoring a Talkgroup number. SETUP: Use Phoenix SIM. 1. From Idle Dialer, enter a valid Talkgroup number, press MENU key, and select “Store Number” option. 2. Verify unit transitions to New Entry Form screen, with number and Talkgroup type populating their respective fields. __15.0 This test verifies number can be stored from Idle Dialer and user can specify the type for the number. SETUP: None. 1. Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store Number” option. 2. Unit should enter “Store To” screen with “[New Contact]” highlighted. 3. Select “[New Contact]” to enter New Entry Form for the number to be stored. 4. Verify the type field is set to first available type in the Type Editor List, excluding Talkgroup type. 5. Assign a name and press “Done” / ”Save” softkey after selecting the type. 6. Verify entry is stored to Contacts. __15.1 This test verifies “Invalid Number” message will post when attempting to store an invalid phone number. SETUP: Enter an invalid phone number (like “P” or a 21-digit number with no “P” or “W” characters) in the Idle Dialer. 1. Press MENU key, and select “Store Number” option. 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select “[New Contact]” to enter Entry Form. 4. Verify error message “Invalid Number” will be displayed. __15.2 This test verifies number can be stored from Idle Dialer and user can specify the type for the number. SETUP: Use Phoenix SIM. 1. Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store Number” option. 2. Unit should enter “Store To” screen with “[New Contact]” highlighted. 3. Select “[New Contact]” to enter New Entry Form for the number to be stored. 4. Verify the type field is set to first available type in the Type Editor List, excluding Talkgroup type. 5. Assign a name and press “Done” / ”Save” softkey after selecting the type. 6. Verify entry is stored to Contacts. __15.3 This test verifies “Invalid Number” message will post when attempting to store an invalid phone number. SETUP: Use Phoenix SIM. Enter an invalid phone number (like “P” or a 21-digit number with no “P” or “W” characters) in the Idle Dialer. 1. Press MENU key, and select “Store Number” option. 2. Unit should enter “Store To” screen, with “[New Contact]” highlighted. 3. Select “[New Contact]” to enter Entry Form. 4. Verify error message “Invalid Number” will be displayed. __15.4 This test verifies talkgroup, SDG and Msg Group doesnt display in Store To screen SETUP: Use Falcon/Phoenix sim. Have some TG, SDG, Msg Group and any other type of entries stored 1. From Idle dialer, enter a valid phone number. 2. Press CSM and select “Store Number”. 3. Unit should enter “Store To” screen with “[New Contact]” highlighted. 4. Verify Talkgroup, SDG and Msg Group entries are not listed. 5. Select “[New Contact]” to enter New Entry Form for the number to be stored. 6. Verify the type field is set to first available type in the Type Editor List, excluding Talkgroup, SDG and Msg Group type. 7. Assign a name and press “Save” softkey after selecting the type. 8. Verify entry is stored to Contacts. __16.0 This test verifies if new entry has been stored from RCL, unit will return to RCL. SETUP: Have a non-stored phone number in RCL. Use Condor/Falcon/(DS)Phoenix sim 1. Enter RCL, highlight number from setup and press “Store” softkey.(“Save” for Marlin) 2. Unit should enter “Store To” record browser with “[New Contact]” highlighted. 3. Store this number to New Contact 4. Verify after the number is stored, unit will return to RCL, with the name or number of entry just stored highlighted. __16.1 This test verifies if new entry has been stored from RCL, unit will return to RCL. SETUP: Use Phoenix SIM. Have a non-stored phone number in RCL. 1. Enter RCL, highlight number from setup and press “Save”. 2. Unit should enter “Store To” record browser with “[New Contact]” highlighted. 3. Store this number to New Contact 4. Verify after the number is stored, unit will return to RCL, with the name or number of entry just stored highlighted. __17.0 This test verifies if new entry has been stored from Idle Dialer, unit will return to Idle Dialer and entered number will still be displayed. SETUP: None.Use Condor/Falcon/(DS)Phoenix sim 1. Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store Number” option. 2. Unit should enter “Store To” record browser screen with “[New Contact]” highlighted. 3. Store this number to New Contact. 4. Verify after the number is stored, unit will return to Idle Dialer, with the number still displayed. __17.1 This test verifies if new entry has been stored from Idle Dialer, unit will return to Idle Dialer and entered number will still be displayed. SETUP: Use Phoenix SIM. 1. Enter a valid phone number in the Idle Dialer, press MENU key, and select “Store Number” option. 2. Unit should enter “Store To” record browser screen with “[New Contact]” highlighted. 3. Store this number to New Contact. 4. Verify after the number is stored, unit will return to Idle Dialer, with the number still displayed. __18.0 This test verifies if new entry has been stored from SMS message screen, unit will return to message screen. SETUP: Receive an SMS message with a valid phone number embedded. Use Condor/Falcon/(DS)Phoenix sim 1. Read the message, press MENU key, and select “Store Number”. 2. Verify unit enters “Store To” record browser screen, with “[New Contact]” highlighted. 3. Store this number to New Contact. 4. Verify after the number is stored, unit will return to the message screen. __18.1 This test verifies if new entry has been stored from SMS message screen, unit will return to message screen. SETUP: Use Phoenix SIM. Receive an SMS message with a valid phone number embedded. 1. Read the message, press MENU key, and select “Store Number”. 2. Verify unit enters “Store To” record browser screen, with “[New Contact]” highlighted. 3. Store this number to New Contact. 4. Verify after the number is stored, unit will return to the message screen. __19.0 This test verifies user will not be able to store another entry of 64 digits or 32 characters in length if the extended slots in SIM memory are exhausted. SETUP: Empty Contacts of all entries. Store 100 phone numbers with 64 digits in length and 100 E-mail IDs with 32 characters in length. Use RSS to read the SIM and to add these entries. 1. Attempt to store one more phone number entry with 64 digits in length. 2. Verify user will not be able to store another entry of this length, and an error message “Long Number Memory Full” will post. 3. Attempt to store one more E-mail ID of 32 characters in length. 4. Verify user will not be able to store another entry of this length, and an error message “Email Memory Full” will post. __19.1 This test verifies “Contacts Full” will display when attempting to store a number to full Contacts List. SETUP: Exhaust the SIM memory by storing the maximum number of entries to Contacts. Have at least one non-store phone number in RCL. Use RSS to read the SIM and to add these entries. 1. From RCL, highlight the number from setup and press “Store” softkey.(“Save” for Marlin) 2. Verify transient notice “Contacts Full” is displayed, which times out to RCL. __19.2 This test verifies user will not be able to store another entry of 64 digits or 32 characters in length if the extended slots in SIM memory are exhausted. SETUP: Use Phoenix SIM.Empty Contacts of all entries. Store 200 phone numbers with 64 digits in length and 200 E-mail IDs with 32 characters in length. Use RSS to read the SIM and to add these entries. 1. Attempt to store one more phone number entry with 64 digits in length. 2. Verify user will not be able to store another entry of this length, and an error message “Long Number Memory Full” will post. 3. Attempt to store one more E-mail ID of 32 characters in length. 4. Verify user will not be able to store another entry of this length, and an error message “Email Memory Full” will post. __19.3 This test verifies “Contacts Full” will display when attempting to store a number to full Contacts List. SETUP: Use Phoenix SIM. Exhaust the SIM memory by storing the 1200 entries to Contacts. Have at least one non-store phone number in RCL. Use RSS to read the SIM and to add these entries. 1. From RCL, highlight the number from setup and press “Save” softkey. 2. Verify transient notice “Contacts Full” is displayed, which times out to RCL. __20.0 This test verifies user can store another entry of normal length when all 400 slots designated for normal length entries are exhausted, utilizing the extended slots in SIM memory. SETUP: Have 400 entries of normal length (20 digits or less) stored. Use RSS to read the SIM and to add these entries. 1. Attempt to store another entry of normal length to Contacts. 2. Verify user is allowed to store this entry. NOTE: This entry will utilize the space of the extended slots designated for 64-digit and 32-character entries, so the user will be allowed to store it. __20.1 This test verifies user can store another entry of normal length when all 400 slots designated for normal length entries are exhausted, utilizing the extended slots in SIM memory. SETUP: Use Phoenix SIM. Have 400 entries of normal length (20 digits or less) stored. Use RSS to read the SIM and to add these entries. 1. Attempt to store another entry of normal length to Contacts. 2. Verify user is allowed to store this entry. NOTE: This entry will utilize the space of the extended slots designated for 64-digit and 32-character entries, so the user will be allowed to store it. __21.0 This test verifies “Long Number Memory Full” message will post when extended slots in the SIM are exhausted. SETUP: Have 200 phone entries of 64 digits in length stored in Contacts to exhaust the Extended Slots space. Use RSS to read the SIM and to add these entries. 1. Attempt to store one more phone number entry with 64 digits in length. 2. Verify “Long Number Memory Full” transient message will be displayed, which times out to the previous screen. __21.1 This test verifies “Long Number Memory Full” message will post when extended slots in the SIM are exhausted. SETUP: Have 200 E-mail ID entries of 32 characters in length stored in Contacts to exhaust the Extended Slots space. Use RSS to read the SIM and to add these entries. 1. In Idle Dialer, enter a 21-digit long number, press Menu key and select option to store this number. 2. Verify “Long Number Memory Full” transient message will be displayed, which times out back to Idle Dialer. __21.2 This test verifies storing an iCard with SDG type entry to Contacts. SETUP: MS1 (non-test unit) has two aliased SDG type entries stored, of which the socond one has 3 private id numbers. MS2’s (the test unit) SDG capacity is not exhausted. 1. From MS1, send an iCard with first SDG type entry to MS2. 2. MS2 should receive the SDG iCard, and it should be stored in RCL. 3. Enter RCL, highlight the iCard received, and press the “Store” softkey.(“Save” for Marlin) 4. Verify unit transitions straight to SDG Storing form, with the correct data from iCard filled in. 5. Exit to Idle. 6. On MS2, exhaust the SDG capacity by storing 25 SDG entries with 20 members in each. 7. From MS1, send an iCard with the second SDG type entry from setup (the one with 3 private id’s). 8. MS2 should receive the SDG iCard, and it should be stored in RCL. 9. On MS2, enter RCL, highlight the iCard received and press the “Select” softkey. 10. Verify transient notice is displaye: the first line will have “Unable to Store:” and the scond line will have “Space Exceeded”. 11. Verify transient notice times out back to RCL. __21.3 This test verifies “Long Number Memory Full” message will post when extended slots in the SIM are exhausted. SETUP: Use Phoenix SIM. Have 400 phone entries of 64 digits in length stored in Contacts to exhaust the Extended Slots space. Use RSS to read the SIM and to add these entries. 1. Attempt to store one more phone number entry with 64 digits in length. 2. Verify “Long Number Memory Full” transient message will be displayed, which times out to the previous screen. __21.4 This test verifies “Long Number Memory Full” message will post when extended slots in the SIM are exhausted. SETUP: Use Phoenix SIM. Have 400 E-mail ID entries of 32 characters in length stored in Contacts to exhaust the Extended Slots space. Use RSS to read the SIM and to add these entries. 1. In Idle Dialer, enter a 21-digit long number, press Menu key and select option to store this number. 2. Verify “Long Number Memory Full” transient message will be displayed, which times out back to Idle Dialer. Storing Entries Using the Contacts Menu __22.0 This test verifies entry can be stored by selecting “New” from Contacts Menu while in List View. SETUP: None. 1. From Idle Mode, enter Contacts List View, press MENU key and select “New”. 2. Verify unit enters the New Entry Form. See Figre1-7. 3. Enter Name, Number, and Type for this entry and press “Done” / ”Save” softkey. 4. Verify unit returns to List View with newly created entry highlighted. See Figure1-7. __23.0 This test verifies entry can be stored by selecting “New” from Contacts Menu while in Detailed View. SETUP: Have at least one entry stored in Contacts. 1. Enter Contacts Detailed View for entry from setup, press MENU key and select “New”. 2. Verify unit enters the New Entry Form. 3. Enter Name, Number, and Type for this entry and press “Done” / ”Save” softkey. 4. Verify unit returns to Detailed View for the newly created entry. Storing Multiple Numbers Associated with a Single Name __24.0 This test verifies user can store multiple numbers for an entry in Contacts. SETUP: None. 1. Enter Contacts List View, press MENU key, and select “New”. 2. Verify unit enters the New Entry Form. See Figure1-7. 3. Enter Name, and for all of the available types displayed enter the number in the number field and press “Done” / ”Save” softkey at the end. NOTE: Talkgroup is not going to be available in the type list, since it cannot be added to a multitype entry. 4. Verify unit returns to List View with newly stored multitype entry highlighted. 5. Verify all of the types are stored by scrolling Left/Right. See Figure1-8 for details. __24.1 This test verifies user can store multiple numbers for an entry in Contacts. SETUP: Use Phoenix SIM. 1. Enter Contacts List View, press MENU key, and select “New”. 2. Verify unit enters the New Entry Form. See Figure1-7. 3. Enter Name, and for all of the available types displayed enter the number in the number field and press “Done” / ”Save” softkey at the end. NOTE: Talkgroup is not going to be available in the type list, since it cannot be added to a multitype entry. 4. Verify unit returns to List View with newly stored multitype entry highlighted. 5. Verify all of the types are stored by scrolling Left/Right. See Figure1-8 for details. __25.0 This test verifies user can store multiple numbers for an entry in Contacts. SETUP: Have at least one entry stored in Contacts. 1. Enter Contacts Detailed View for entry from setup, press MENU key, and select “New”. 2. Verify unit enters the New Entry Form. 3. Enter Name, and for all of the available types enter Number and Type in their respective fields and press “Done” / ”Save” softkey at the end. 4. Verify unit returns to Detailed View with the first record of newly stored multitype entry displayed (Mobile). 5. Verify all of the types are stored by scrolling Up/Down. __25.1 This test verifies the display of Private/DC type when Direct Connect Display bit is disabled/enabled in the codeplug. SETUP: Using RSS, enable the Direct Connect Display bit in the codeplug (“static_ErgoBlock (ER 1 of 13)” “Tiering_flag5” - field 42, count from left to right for bit #14 and change it from 0 to 1). Have at least one DC type of entry stored in Contacts. NOTE: For Marathon, when DC bit is ON, string “Private” will show as “Direct Connect” 1. Enter Contact New Entry Form, highlight the Type field and enter Type Editor List. 2. Verify DC is displayed in the list. 3. Exit to Idle, and enter the Entry Form for specified DC type of entry from setup. 4. Verify DC is displayed in the Type field. 5. Exit to Idle and enter Contacts New Entry Form. 6. Verify DC is displayed as the second type in the list, after the Mobile type. 7. Use RSS to disable the Direct Connect Display bit, and repeat the test. 8. Verify the string “Private” has replaced “DC” string in the type field and Type Editor List. 9. Verify all of the types are stored by scrolling Left/Right. See Figure1-8 for details. __25.2 This test verifies user can store multiple numbers for an entry in Contacts. SETUP: Use Phoenix SIM. Have at least one entry stored in Contacts. 1. Enter Contacts Detailed View for entry from setup, press MENU key, and select “New”. 2. Verify unit enters the New Entry Form. 3. Enter Name, and for all of the available types enter Number and Type in their respective fields and press “Done” / ”Save” softkey at the end. 4. Verify unit returns to Detailed View with the first record of newly stored multitype entry displayed (Mobile). 5. Verify all of the types are stored by scrolling Up/Down. Condor (i3000), GSM, and Endeavor (i2000) SIM Cases __26.0 This test verifies when storing a phone number to Contacts, type and number fields will automatically be populated with relevant data upon accessing New Entry Form. GSM/Endeavor SIM case. SETUP: GSM SIM is inserted first. Have a non-stored phone number in RCL. 1. From RCL, highlight the number from setup, and press “Store” softkey.(“Save” for 1. Marlin) 2. Verify unit transitions to New Entry Form, with number and Main type populating their respective fields. 3. Replace the GSM SIM with Endeavor SIM and repeat the test. 4. Verify the same results as in step 2. __26.1 This test verifies when storing a phone number to Contacts, type and number fields will automatically be populated with relevant data upon accessing New Entry Form. SETUP: Phoenix SIM is inserted first. Have a non-stored phone number in RCL. 1. From RCL, highlight the number from setup, and press “Store” softkey.(“Save” for Marlin) 2. Verify unit transitions to New Entry Form, with number and Main type populating their respective fields. __27.0 This test verifies when storing a private or a talkgroup number to Contacts, type and number fields will automatically be populated with relevant data upon accessing New Entry Form. Endeavor SIM case. SETUP: Have a non-stored Private and Talkgroup numbers in RCL. 1. From RCL, highlight the Private number from setup, enter RCL Menu, and select Store option. 2. Verify unit transitions to New Entry Form, with number and Private/DC type populating their respective fields. 3. Return to RCL, highlight the Talkgroup number from setup, enter RCL Menu, and select Store option again. 4. Verify unit transitions to New Entry Form, with number and Talkgroup type populating their respective fields. __27.1 This test verifies when storing a private or a talkgroup number to Contacts, type and number fields will automatically be populated with relevant data upon accessing New Entry Form. SETUP: Use Phoenix SIM. Have a non-stored Private and Talkgroup numbers in RCL. 1. From RCL, highlight the Private number from setup, enter RCL Menu, and select Store option. 2. Verify unit transitions to New Entry Form, with number and Private/DC type populating their respective fields. 3. Return to RCL, highlight the Talkgroup number from setup, enter RCL Menu, and select Store option again. 4. Verify unit transitions to New Entry Form, with number and Talkgroup type populating their respective fields. __28.0 This test verifies “Contacts Full” transient notice will be displayed when attempting to store a number to full Contacts list. GSM SIM case. SETUP: Exhaust the SIM memory by storing maximum number of entries to Contacts. Have a non-stored phone number in RCL. Use RSS to read the SIM and to add these entries. 1. From RCL, highlight the number from setup, and press “Store” softkey.(“Save” for Marlin) 2. Verify transient notice “Contacts Full” is displayed, which times out back to RCL. __29.0 This test verifies a transient notice will post when attempting to store an IP address to GSM/Endeavor SIM. GSM/Endeavor SIM case. SETUP: None. 1. Receive an SMS message with embedded IP Address, and attempt to store this IP address to Contacts. 2. Verify transient notice “Can’t Store IP Address” is displayed. 3. Replace the GSM SIM with Endeavor SIM, and repeat the test. 4. Verify the same results as in step 2. __30.0 This test verifies transient notice will post when attempting to store a Private or Talkgroup numbers to Contacts, when Private and Talkgroup Lists are full. Endeavor SIM case. SETUP: Completely fill Private and Talkgroup lists of the SIM. Have non-stored Private and Talkgroup numbers in RCL. Use RSS to read the SIM and to add these entries. 1. From RCL, highlight Private number from setup, enter RCL Menu, and select Store option. 2. Verify transient notice “Private/DC List Full” is displayed. 3. Return to RCL, highlight Talkgroup number from setup, enter RCL Menu, and select Store option. 4. Verify transient notice “Talkgroup List Full” is displayed. __31.0 This test verifies transient notice will post when attempting to store a Phone number to Contacts, when Phone List is full. Endeavor SIM case. SETUP: Completely fill the Phone list of the SIM. Have a non-stored phone number in RCL. Use RSS to read the SIM and to add these entries. 1. From RCL, highlight Phone number from setup, and press “Store” softkey.(“Save” for Marlin) 2. Verify transient notice “Phone List Full” is displayed. __32.0 This test verifies transient notice “Contacts Full” will post when attempting to store a number to Contacts, when all three type lists are full. Endeavor SIM case. SETUP: Exhaust the SIM memory by storing maximum number of entries to Contacts for all three types. Have a non-stored phone number in RCL. 1. From RCL, highlight the phone number from setup, and press “Store” softkey.(“Save” for Marlin) 2. Verify transient notice “Contacts Full” is displayed, which times out back to RCL. __33.0 This test verifies a transient message “Can’t Store Long Number” is displayed when attempting to store a number of more than 20 digits in length to Contacts. Condor, GSM, and Endeavor SIM case. SETUP: Insert GSM SIM first. Have a non-stored phone number in RCL that exceeds 20 digits in length, like 1234567890P1234P123456P99 1. From RCL, highlight number from setup, and press “Store” softkey.(“Save” for Marlin) 2. Verify transient notice “Can’t Store Long Number” is displayed, which times out back to RCL. 3. Replace the GSM SIM with Endeavor SIM and repeat the test. 4. Verify the same result as in step 2. 5. Replace the Endeavor SIM with Condor SIM and repeat the test. 6. Verify the same result as in step 2. MOTOtalk Test Cases Preconditions: Unit is in MT mode at the beginning of each test. To place the unit in MT mode, MOTOtalk bit must be enabled in the codeplug. Once enabled, user will be able to select MT from the Main Menu. The type priority when assigning numbers is: Mobile, Other, Work1, Work2, and Home. If Mobile is already existing, Other will be displayed in the form by default. If both Other and Mobile are existing, Work1 will be the default, etc __34.0 This test verifies when quickstoring a number while in MT mode, using GSM/Endeavor SIM, type will default to “Main”. GSM/Endeavor SIM test case. SETUP: Use GSM/Endeavor SIM. 1. Enter a valid phone number in Idle Dialer, press MENU key and select “Store Number” option. 2. Verify unit enters the new entry form, with the number filled in the number field, and type field set to “Main”. __35.0 This test verifies quickstoring a number from RCL to existing entries in Contacts, while in MT mode. SETUP: Have at least one non-stored phone number in RCL. Store one entry that has all MT types occupied and one “Other” type of entry. 1. From RCL, highlight the number from setup, press “Store” softkey, and select the entry that has all MT types occupied. 2. Verify transient notice “All types full” displays, and unit returns to RCL. 3. Press “Store” softkey again, and select the “Other” type entry to store the number to. 4. Verify unit enters the entry form, with number filled in, and type set by default to “Mobile”. __36.0 This test verifies quickstoring a private type number from RCL while in MT mode. SETUP: Have at least one non-stored Private ID number in RCL. 1. From RCL, highlight the private number, press MENU key, and select “Store” option. 2. Verify unit enters the entry form with the number populating the number field, and the type set by default. __37.0 This test verifies type will be set to Mobile by default, when storing numbers to existing contacts. SETUP: Store one two “Home” type of entries to Contacts. Have a non-stored phone num ber in RCL.Use Condor/Falcon/(DS)Phoenix sim 1. Enter RCL and select to store the number from setup to an existing the first “Home” type of entry from setup. 2. Verify unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Mobile” by default. 3. Press “Done”/ ”Save” softkey, and verify entry was stored to Contacts. 4. Exit to idle. 5. Enter a valid phone number in the Idle Dialer, and select to store it to the same second “Home” type of entry from setup. 6. Verify unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Mobile” by default. 7. Press “Done”/ ”Save” softkey, and verify entry was stored to Contacts. __38.0 This test verifies a transient notice will be displayed when Mobile type is used, when user is attempting to store the number to existing contact. It also verifies the storing order priority while in MT mode. SETUP: Have two multitype entries stored: the first one has “Mobile” and “Other” types; the second one has “Mobile, Other, and Work1” types. Also, have a non-stored phone number in RCL. Use Condor/Falcon/(DS)Phoenix sim 1. Enter RCL and select to store the number from setup to first multitype entry. 2. Verify “Can’t store to Mobile” transient notice is shown. 3. Verify after the notice times out, unit will enter the Entry Form, with the number to be stored displayed in the number field, and type field set to “Work1” by default. 4. Press “Done”/ ”Save” softkey, and verify entry was stored to Contacts. 5. Exit to Idle. 6. Enter a valid phone number in the Idle Dialer, and select to store it to the second multitype entry from setup. 7. Verify “Can’t store to Mobile” transient notice is shown. 8. Verify after the notice times out, unit will enter the Entry Form, with the number to be stored displayed in the number field, and type field set to “Work2” by default. 9. Press “Done”/ ”Save” softkey, and verify entry was stored to Contacts. __39.0 This test verifies type will be set to Mobile by default, when storing number with specified type from RCL. SETUP: Store one “Work1” type of entry to Contacts. Have a non-stored, Work2 phone number inRCL. To make this number available in RCL, do the following: - Store a “Work2” phone number to Contacts and initiate a call to it after storing. - End the call and delete the contact from Contacts. RCL will now have a number with “Work2” type, but without alias. Use Condor/Falcon/(DS)Phoenix sim 1. Enter RCL and select to store the number from setup to an existing “Work1” type of entry. 2. Verify unit enters the Entry Form, with the number to be stored displayed in the number field, and type field set to “Mobile” by default. 3. Save this number and verify entry was properly stored to Contacts. __40.0 This test verifies a transient notice will be displayed when Mobile type is used, when user is attempting to store the number with specified type from RCL to existing contact. It also verifies the storing order priority while in MT mode. SETUP: Have one multitype entry with “Mobile, Work1, and Home” types stored. Have a non-stored, Work2 phone number inRCL. To make this number available in RCL, do the following: - Store a “Work2” phone number to Contacts and initiate a call to it after storing. - End the call and delete the contact from Contacts. RCL will now have a number with “Work2” type, but without alias. Use Condor/Falcon/(DS)Phoenix sim 1. Enter RCL and select to store the number from setup to existing multitype entry. 2. Verify “Can’t store to Mobile” transient notice will be shown. 3. Verify after the notice times out, unit will enter the Entry Form, with the number to be stored displayed in the number field, and type field set to “Other” by default. 4. Press “Done”/ ”Save” softkey, and verify entry was stored to Contacts. __40.1 This test verifies SETUP: Have one multitype entry with “Mobile, Work1, Work2 and Home” types stored. Have a non-stored phone number in RCL. 1. In MT mode, enter RCL and highlight the non stored phone number. 2. Press Save softkey. 3. Select the multitype entry in Contacts to store the number. 4. Verify transient notice “All types full” is shown and it times out to RCL. Prefix Test Cases __41.0 This test verifies storing a MyInfo iCard to a new contact when the user chooses to add prefix will automatically add prefix to the interconnect numbers when the Contacts form is popped up. SETUP: On MS1, enter “Store Received Info”/”Store Rcvd Info” feature from Main Menu -> Settings -> 2-Way Radio. Set “Add Prefix” to “Ask Me” and make sure “Prefix” is not empty. MS2 is number is not stored in Contacts of MS1. MS2 uses Alt line SIM to have both Line1 and Line2 info. 1. From MS2, enter My Info from Main Menu and press Menu key. 2. Select “Send My Info via PTT” “Send via PTT” by pressing Ok key while highlighting this item. 3. Verify MS2 enters “Send To:” text editor. 4. Enter MS1 private id and press Ok key. MS1 will enter “Ready To Send” screen. 5. Press PTT key to send MyInfo iCard to MS1. 6. Verify unit enters RCL after MyInfo iCard is sent over to MS1 and when private call is ended. 7. On MS1, highlight the received MyInfo iCard in RCL and press Menu key. 8. Select “Store”by pressing Ok key.LSK “Save” 9. Verify confirmation notice “Add Prefix?” as Line 1 and “xxx” as Line 2 (xxx is the current default prefix value) is displayed. 10. Press Yes softkey. 11. When MS1 is in Store To screen, select [New Contact]. 12. Verify that prefix will be added automatically to the interconnect numbers of Line1 and Line2 when the New Contact form is popped up. The number format after adding the prefix will be “default prefix” + “received interconnect number”. Enter an alias in the Name: field. 13. Press Save(Marlin, Mango Key2, Majua) or Done(Cobia) softkey. 14. Verify MS1 returns to RCL highlighting the contact that is just stored. 15. Exit to idle and enter Contacts. Delete the entry that was saved at step13. 16. Repeat step 1-9. 17. Press No softkey. 18. Select [New Contact]. 19. Verify that prefix will not be added to the interconnect numbers when the New Contact form is popped up. 20. Press Save(Marlin, Mango Key2, Majua) or Done(Cobia) softkey. 21. Verify MS1 returns to RCL highlighting the contact that is just stored. __41.1 This test verifies storing a MyInfo iCard to an existing contact when the user chooses to add prefix will automatically add prefix to the interconnect numbers when the Contact form is popped up. SETUP: Have at least 2 entries stored in Contacts. On MS1, enter “Store Received Info” feature from Main Menu -> Settings -> 2-Way Radio. Set “Add Prefix” to “Ask Me” and make sure “Prefix” is not empty. 1. Place a private call from MS2 to MS1. When MS2 is in an active private call, press PTT once to send MyInfo iCard to MS1. 2. Verify unit enters RCL after private call is ended. 3. On MS1, highlight the received MyInfo iCard in RCL and press Menu key. 4. Select “Store” by pressing Ok key.LSK “Save” 5. Verify confirmation notice “Add Prefix?” as Line 1 and “xxx” (xxx is the current default prefix value) as Line 2 is displayed. 6. Press Yes softkey. 7. Select a contact. 8. Verify that prefix will be added automatically to the interconnect numbers when the New Contact form is popped up. The number format after adding the prefix will be “default prefix” + “received interconnect number”. 9. Press Save(Marlin, Mango Key2, Majua) or Done(Cobia) softkey. 10. Verify MS1 returns to RCL highlighting the contact that is just stored. 11. Repeat step 1-5. 12. Press No softkey. 13. Select another contact. 14. Verify that prefix will not be added to the interconnect numbers when the Contact form is popped up. 15. Press Save(Marlin, Mango Key2, Majua) or Done(Cobia) softkey. 16. Verify MS1 returns to RCL highlighting the contact that is just stored. UIS Version Product / Test Case Cross Reference Table NOTE: F/FI/UI/S/SI/API/O (Feature/Feature Interaction/User Interface/Stress/Strings & Icons/API for Java/Others based test case) Test Case Manual(M)/Auto(A) F/FI/UI/S/SI/API/O Severity(H/L) Taos Bluefin Athens Majua Blackstone Brightwater 1 A UI L X X X X X X 2 A FI H X X X X X X 3 A FI H X X X X X X 4 A UI L X X X X X X 4.1 A FI H X X X X X X 4.2 A FI H 5 A UI L X X X X X X 5.1 A FI H 5.2 X 5.3 X 5.4 X 5.5 X 6 A UI L X X X X X X 7 A UI L X X X X X X 8 A FI H X X X X X 9 10 11 12 13 14 14.1 A UI L X X X X X 14.2 X 14.3 X 14.4 M UI L X X 15 A UI L X X X X X 15.1 A UI L X X X X X X 15.2 M UI L X X 15.3 M UI L X X 15.4 M X 16 A UI L X X X X X X 16.1 M FI L X X 17 A UI L X X X X X X 17.1 M FI L X X 18 A FI H X X X X X X 18.1 M FI L X X 19 A UI L X X X X X X 19.1 A UI L X X X X X X 19.2 M FI L X X X 19.3 M UI L X X X 20 A X X X 20.1 M X 21 A UI L X X X X X X 21.1 A UI L X X X X X X 21.2 X X X X X 21.3 M UI L X X X 21.4 M UI L X X X 22 A S L X X X X X X 23 A S L X X X X X X 24 M S L X X X X X X 24.1 M S L X X 25 A S L X X X X X X 25.1 A FI H 25.2 M S L X X 26 M X X X X X 26.1 M FI L X X X 27 M X X X X X 27.1 M FI L X X X 28 M UI L X X X X X 29 M X X X X X 30 M X X X X X 31 M X X X X X 32 M X X X X X 33 M X X X X X 34 35 36 37 X X X 38 X X X 39 X X X 40 X X X 40.1 X 41 M FI H X X X X X X 41.1 M FI H X X X X X X Total 35 44 48 38 45 38 Contacts Full Private List Full Talkgroup List Full Phone List Full Direct Connect List Full The direct connect display bit of the codeplug is turned off. The direct connect display bit of the codeplug is turned on. MOTOROLA CONFIDENTIAL PROPRIETARY Copyright Motorola, Inc. 2008-2009 This document is controlled electronically. All paper copies of this document are uncontrolled. _1315379853.doc Icon Description Revision History Icon Design Bitmap File Name Comments Fax 1/17/03 Ext_Fax_15_15_1bit.bmp Home 1/17/03 Ext_Home_15_15_1bit.bmp IP 1/17/03 Ext_IP_15_15_1bit.bmp Email 3/4/03 Ext_Email_15_15_1bit.bmp Mobile 3/4/03 Ext_Mobile_15_15_1bit.bmp Pager 1/17/03 Ext_Pager_15_15_1bit.bmp Private ID 3/4/03 Ext_Private_15_15_1bit.bmp Talkgroup 3/4/03 Ext_Talkgroup_15_15_1bit.bmp Work 1 2/20/03 Ext_Work1_15_15_1bit.bmp Work 2 2/20/03 Ext_Work2_15_15_1bit.bmp User may now set 2 different work numbers Other 1/17/03 Ext_Main_15_15_1bit.bmp Multiple Types Unknown Type 1/17/03 Ext_UnkownType_15_15_1bit.bmp This is a contact type (i.e. work/home/etc) which is not recognized by the handset. VoiceTag 2/20/03 Ext_Voicetag_15_15_1bit.bmp Hub 11/29/05 Ext_Hub_15_15_1bit.bmp _1315379759.doc