mobiNotice Acceptance Test LinkedIn Version

P a g e | 1

OakMobimobiNoticeNeighborhoodAlertServiceAcceptanceTestProcedureVersion 1.0

Susan Kaymon5/7/2012

P a g e | 2

OverviewThis document provides the acceptance testing process for the newly developed on line version of themobiNotice Neighborhood Alert Service (herein known as mobiNotice). This document will outline thefeatures of the on line service, the functional performance of each page, the objects on the page andthe expected outcome of object events. In the event an object fails to perform as outlined a bug reportshall be created and the bug assigned a level of criticality.

Definition of TermsApplication – a series of web pages inter-linked to provide the full range of functions necessary tosuccessfully manage the user account and create and view mobiNotice alerts.

Area – a neighborhood defined for the mobiNotice Alert Service

Blast Keyword – the first series of letters in a Blast Message that identifies to which Area a BlastMessage is targeted

Blast Message – an alert message sent to all registered phones in an area

Bug – an unexpected event or failure of the program to complete an event as described.

Bug Criticality – the degree to which a bug interferes with the user’s ability to use the application asdefined below:

Level BI – the application failed to accomplish the task resulting in the user being unable toproperly interact with the application. For example: a link fails to respond or a 401Unauthorized Access (without an OakMobi Logo) is displayed, 404 Document Not FoundError is displayed or a warning message is displayed across the top of the web page.

Level BII – the page content is overlapping elements, out of order or otherwise incoherentdue to formatting issues.

Level BIII – page styling and page to page variations are distracting or not appealing.

Element – a feature of the web page such as an image, table, paragraph, button, etc.

Enrolled Household – a household within an area that is enrolled in mobiNotice

Event – the action taken by the web page to carry out the intention of the user through the interactionof an object. For example, the action taken based on the click of a button.

Know Abbreviations – abbreviations that have been entered into the mobiNotice database by users ofthe application

Object – a page element the user interacts with to perform various activities on the page and within theapplication.

Page – a single web page presented to an Internet user.

Performance Level – the level of importance of the requirement for overall success of the application

Level PI – critically important to the overall success of the program. Failure to meet theserequirements will result in a delay in the release of the application.

Level PII – important but can be de-activated pending correction. Failure to meet theserequirements will cause the feature to be deactivated for the application release and re-activated after correction.

P a g e | 3

Level PIII – nice to have feature. Failure to implement this requirement will not impact therelease of the application.

Registered Phone – a mobile number registered with mobiNotice

Short Code – The five digit text message ‘phone number’

User – anyone interacting with the mobiNotice application

mobiNotice On Line Application SummaryThe mobiNotice on line application is an extension of the mobiNotice Mobile Neighborhood AlertService. The on line application allows new users to enroll in the service while allowing existing users tomanage their account and create and view alert messages. Figure 1: Top-Level mobiNotice Application,below, provides an overview of the main pages of the mobiNotice web application. The details belowwill cover each of these pages and their expected performance.

Figure 1: Top-Level mobiNotice Application

Application Functional RequirementsEvery application has specific functional requirements that define the expected performance of theapplication. Those requirements for the mobiNotice application are defined below.

Enrollment Top Level Application Performance Objectives

Online mobiNotice Service EnrollmentPerformance Level: PI

P a g e | 4

The user shall be able to initiate enrollment in mobiNotice via the OakMobi website. Enrollment shallinclude gathering primary account holder name, address and mobile phone number, up to fouradditional mobile phone numbers based on the type of address and collecting payment via a third-partymerchant processor.

1. Primary account holder name and mobile numbera) Performance Level: PIb) The application shall obtain primary account holder name, mobile number and email

address for purposes of billing and contact2. Additional mobile numbers

a) Performance Level: PIIb) The application shall obtain any additional mobile numbers the user wishes to enroll in the

service3. Address to enroll

a) Performance Level: PIb) The application shall collect the enrollment address. This information is used to determine

the area of the enrolled address and the appropriate plan for billing purposes4. Enrolled address type – business or residential

a) Performance Level: PIb) The application shall collect the type of address being enrolled. This information is used to

determine the correct billing plan5. Billing Name and Address

a) Performance Level: PIb) If different then the primary account holder and enrolled address, the application shall

collect the billing name and address of the person enrolling in the service. This informationis used by the third-party payment processor to verify debit/credit card account.

Create Log InPerformance Level: PI

After successfully completing enrollment, the user shall be offered the ability to create an online accessaccount.

1. Every user with a registered phone shall be able to create an online access to the enrolledhousehold account

2. The registered phone number shall be verified against the registered number database toauthenticate eligibility of the user to access mobiNotice online.

3. The user shall be required to enter a strong password consisting of a minimum of 8 charactersand a maximum of 16 characters with at least 1 capital letter, 1 number and 1 symbol

4. The user shall be required to enter a password hint, not equal to the password, to remind themof their password

P a g e | 5

mobiNotice Online Application

Log InPerformance Level: PI

After creating an online access password, the user shall be able to access the mobiNotice webapplication. Access to the application shall enable the user to manage their account, create and sendblast messages, and view blast messages for their area.

1. Log in shall require the user to enter their registered mobile number and their password to gainaccess to the application.

2. The user shall have three failed log in attempts before being locked out of the application forthree days.a) Prior to locking the user out of the service, the application shall offer the user the ability to

reset their password. Upon opting to reset their password, the user shall be texted atemporary password to the registered number if it is actually registered with the service. Inthe event the mobile number is not registered with the service the user shall be locked outof the application.

Online mobiNotice Service AdministrationPerformance Level: PI/PIII

Once successfully enrolled in mobiNotice, the user shall be able to activate online accountadministration. Online account administration shall consist of the ability to:

1. Removal from mobiNoticea) Performance Level: PIb) The user shall have the ability to remove themselves from mobiNotice by removing the last

remaining Enrolled Household from the service.2. Add new service area

a) Performance Level: PIIIb) To be added. This feature shall enable the user to monitor other service areas such as

where they work, where they spend a considerable amount of time or monitor an areawhere a relative resides.

3. Add or delete registered phonesa) Performance Level: PI/PIIIb) The user shall be able to add or remove registered phones from their account.

i) Registered phones shall be removed from the service immediately(1) Performance Level: PI

ii) The application shall automatically enroll additional phones where no payment is duebased on the plan terms.(1) Performance Level: PI

iii) A cookie shall be created to hold pending registered phone additions for 30 days or untilpayment is collected whichever is met first

P a g e | 6

(1) Performance Level: PIII4. Update names of registered phone users

a) Performance Level: PIIb) The user shall be able to modify the names of users indicated for registered phones

5. Change primary account holdera) Performance Level: PIIb) The user shall be able to change the primary account holder designation

6. Update primary account addressa) Performance Level: PIIb) The user shall be able to update their billing address

7. Review plan termsa) Performance Level: PIIb) The user shall be able to review but not change mobiNotice plan terms, including

enrollment date, plan costs and allowable phones8. Change online access password

a) Performance Level: PIb) The user shall be able to change their online password at any time including obtaining a

temporary password when they forget their existing password.9. Collect payments

a) Performance Level: PIb) In the event the user exceeds the included number of phones or adds additional service

areas the pending additions shall be indicated on the admin page and payment shallcollected prior to adding the services to the account.

Create Alert MessagePerformance Level: PII

The mobiNotice application shall provide the user the ability to create and send a blast message fromtheir computer.

1. In the event the user is monitoring more than one area, the application shall allow the user toselect which area to send the blast message to.

2. The application shall display the Blast Keyword for the targeted area3. The Blast Message length shall be no more than 160 characters, including the length of the blast

keyworda) Upon entering the text of a blast message the application shall indicate how many

characters are remaining in the message.b) When exceeding the 160 character length limit, the application shall suggest the user

optimize the message length by converting words to abbreviations.4. The application shall allow the user to optimize the Blast Message by converting words to

abbreviations that have been entered by the users of the application5. This page shall include a listing of important emergency and non-emergency phone numbers for

the city in which the area resides.

P a g e | 7

6. The user shall have the ability to enter unique abbreviations and corresponding words orphrases for those abbreviations. These abbreviations shall be used by the application tooptimize message length.

View Alert MessagePerformance Level: PII

The application shall provide the user with the ability to review blast messages sent by mobiNotice.

1. Upon loading the page, the application shall display messages from the most current day ofmessaging.

2. The user shall be able to select a time period of most current message minus one week, onemonth, one year or all messages.

3. The messages shall be shown in the form they were texted to the registered users and shall becleared of known abbreviations.

4. The application shall enable the user to submit abbreviations to the mobiNotice abbreviationsdatabase.

Detail Page Review and Testing RequirementsThis section of the specification shall review each page of the application, its objective and specificperformance expectations. Testing pass/fail criteria shall be established.

mobiNotice Online Service Enrollment

Access1 and ObjectiveThe mobiNotice Enrollment Page shall be accessible from the OakMobi website via the mobiNotice:Neighborhood Notification Services link on the website header. The page shall also be available on theOakMobi Products page via the Neighborhood Notification Services link.

This page gathers the data necessary to determine the appropriate area to enroll the user, determinethe proper service plan and to gather the information required by the merchant processing third-partyvendor. While processing this page the application will:

Check to see if the user is already enrolled. If so, the application will redirect the user to the login or create log in page as necessary

Determine in which area the address entered for monitoring resides. If the address is notcontained in an active area, the user will be asked if they want to be contacted to create anarea.

Determine the appropriate pricing plan. For example: does the address indicate it is part of agroup plan; or, is the address a business address?

Based on payment results the application will perform the following tasks: if the payment fails,the user will be informed as to why the payment failed and asked if they would like to try again;

1 Prior to release of the application the link from the OakMobi website shall be inactive.

P a g e | 8

if the user cancels they payment process or the page times out, the application will revert to theEnrollment Page; if the payment is successful, the user is informed of the opt in status of themobile phones they provided and instructed on how to create and send a blast message.

Acceptance Test RequirementsTest page access: https://mobiNotice.oakmobi.com/nnsenroll.html

Figure 2: mobiNotice Enrollment Page, below is a screenshot of the mobiNotice Enrollment Page. Thepage is broken down into five areas: Enrollment Address, Primary Account Holder Information,Additional Mobile Numbers, Credit Card Information and Form Submission.

Figure 2: mobiNotice Enrollment Page

Acceptance Testing Procedure

Test ConditionsTester:

Test Date:Browser: Internet Explorer/Google Chrome/Opera/Safari/Firefox/Other:

Browser Version:Computer Type: Desktop/Laptop

NOTE: ALL ACTUAL TEXT MESSAGING IS TURNED OFF DURING TESTING

Known Issues1. Layout on smaller monitors such as laptops and tablets, needs to be reduced

P a g e | 9

a. Resolved – created adjustimg.js to run on opening of page2. Page needs to be refreshed/resent after opening pdf files

a. Resolved – launched pdf files in their own window3. Browser back button event needs to be captured

a. Pend – instituted a timeout script to force logout if inactive. Logout destroys the session4. Adding more than the number of included phones results in only the included phone added to

the Active Registered Mobile Phones table – the cookie is not created.a. Resolved

Enrollment ApplicationEnrollment Address Section1. Partially complete the information requested and click the ‘Submit’ button

a) Expected Outcome: Dialog box informing you that the missing information must be providedb) Expected Outcome Achieved?

Yes No If no,explain:

c) Complete Enrollment Address, move to Primary Account Holder InformationPrimary Account Holder Information Section1. Incorrectly complete the Mobile Number entry, i.e.: enter the wrong number of digits or enter

charactersa) Expected Outcome: When moving from the first two boxes to the next box you should get a

dialog box indicating the error (wrong number of digits or presence of characters)b) Expected Outcome Achieved?


c) Correct the entry as requested2. Partially complete the remaining requested information and click the ‘Submit’ button

a) Expected Outcome: Dialog box informing you that the missing information must be providedb) Expected Outcome Achieved?


c) Correct the entry as requested3. Enter an incorrectly formatted email address, i.e., one that does not contain the “@” symbol or

one with the “.” after the “@” symbol missing and click the ‘Submit’ buttona) Expected Outcome: Dialog box informing you that the email address is invalidb) Expected Outcome Achieved?


c) Correct the entry as requested, move on to Additional Mobile Numbers4. Enter one additional number. If you incorrectly enter the phone number you will get the same

message as you did in the Primary Account Holder Information.a) Optionally enter User First Name and User Last Name

P a g e | 10

b) Move to the Credit Card Information Section5. Click ‘Name on Credit Card Same As Primary Account Holder’ checkbox

a) Expected Outcome: the text boxes with ‘Enter Cardholder First Name’ and ‘Enter CardholderLast Name’ will be filled in with the Primary Account Holder Name and the text boxes will bedisabled.

b) Expected Outcome Achieved?Yes No If no,

explain:6. Click the ‘Submit’ button

a) Expected Outcome: Dialog box indicating you must provide a Billing Address or check the‘Billing Address Same as Enrollment Address’ box


explain:c) Check the ‘Billing Address Same as Enrollment Address’ checkbox, move to ‘Submit Form

Section’7. Click the ‘Submit’ button

a) Expected Outcome: Dialog box indicating that you must accept the mobiNotice Termsb) Expected Outcome Achieved?


c) Check the ‘I have reviewed and accepted the mobiNotice Terms of Service’ check box.8. Click the ‘Submit’ button

There are five potential Expected Outcomes of the ‘Submit’ button event. The first you havealready tested – verifying the form data was entered. If the required data was not entered youreceived a notice telling you to correct the error. The remaining outcomes are: if the addressyou entered does not exist or the Area is not active; the mobile number you entered is alreadyregistered and has an online access account; the mobile number you entered is alreadyregistered but does not have an online access account; the address is correct, the Area existsand none of the numbers are registered with mobiNotice. Each of these expected outcomes aredescribed below.

a) Test Condition: Incorrect address

Test Data:Address:Street Number: 7590Street Name: Anywhere DrCity: OaklandState: CAZip: 94605Type of Address: ResidentialPrimary Account Holder:Mobile number: (xxx) xxx-xxxx

P a g e | 11

First name: yoursLast name: yoursCredit Card Information:Name On Credit Car Same As Primary Account Holder: CheckedBilling Address Same As Enrollment Address: CheckedTerms:I have reviewed and accepted the mobiNotice Terms of Service: checked

i) Expected Outcome:A dialog indicating the error. The checkbox for ‘Billing Address Same As Enrollment Address’will be unchecked so changes to the address will be updatedii) Expected Outcome Achieved?


iii) Correct the Street Number to 7589, CHANGE THE PRIMARY ACCOUNT HOLDER MOBILENUMBER TO xxx xxx-xxxx, click ‘Submit’

b) Test Condition: Enrolled mobile number with an online account

Test Data:Address:Street Number: 7589Street Name: Anywhere DrCity: OaklandState: CAZip: 94605Type of Address: ResidentialPrimary Account Holder:Mobile number: (xxx) xxx-xxxxFirst name: yoursLast name: yoursCredit Card Information:Name On Credit Car Same As Primary Account Holder: CheckedBilling Address Same As Enrollment Address: CheckedTerms:I have reviewed and accepted the mobiNotice Terms of Service: checked

i) Expected Outcome:You will be redirected to the mobiNotice Log In Form with the mobile number entered.ii) Expected Outcome Achieved?


iii) Click the browers ‘BACK’ button, CHANGE THE PRIMARY ACCOUNT HOLDER MOBILENUMBER TO xxx xxx-xxxx, click ‘Submit’

c) Test Condition: Enrolled mobile number without an on line account

Test Data:

P a g e | 12

Address:Street Number: 7589Street Name: Anywhere DrCity: OaklandState: CAZip: 94605Type of Address: ResidentialPrimary Account Holder:Mobile number: (xxx) xxx-xxxxFirst name: yoursLast name: yoursCredit Card Information:Name On Credit Car Same As Primary Account Holder: CheckedBilling Address Same As Enrollment Address: CheckedTerms:I have reviewed and accepted the mobiNotice Terms of Service: checked

i) Expected Outcome:You will be redirected to the Create a mobiNotice Log In Form with the mobile numberentered. If there is more than one registered phone number without an online accessaccount you will be asked to select the number you are creating an account forii) Expected Outcome Achieved?


The remaining functional aspects of the mobiNotice Enrollment Page consist of: Validating the optional mobile numbers entered in Additional Mobile Numbers

o The procedure for validating these numbers was performed with the Primary AccountHolder’s mobile number

o User First and Last Names are optional. If left blank the application will use the PrimaryAccount Holder’s name

When the ‘Name On Credit Card Same As Primary Account Holder’ and ‘Billing Address Same AsEnrollment Address’ boxes are left unchecked the application verifies the information is enteredand validates the zip code is a number. These procedures were verified in the EnrollmentAddress section of the form.

If the ‘I have reviewed and accepted the mobiNotice Terms of Service’ box is left unchecked theapplication will display a message telling the user they must accept the terms.

Payment ProcessingThis section of the testing focuses on what happens when the user successfully completes themobiNotice Enrollment page and clicks the ‘Submit’ button. Upon clicking ‘Submit’ the user is taken to athird-party merchant processing page, currently Sage Payment Processing. The conditions under testare:

P a g e | 13

The payment processing page displays without error and the user’s information is accuratelydisplayed in the

The correct amount due is presented The user cancels the transaction or the transaction times out The payment is declined

While testing the payment processing use the following credit card information:

Card Number Security CodeVisa 4111111111111111 Any three digit numberMasterCard 5499740000000057 Any three digit number

The process of collecting the payment is broken into three pages – the Payment Processing page, shownin Figure 3: Payment Processing Page, below; the Billing Information Page, shown in Figure 4: BillingInformation below; and, the Transaction Detail Page, shown in Figure 5: Transaction Detail below . ThePayment Processing page shows the user the amount due and collects the user credit card number,expiration date and security code. The amount due is based on the type of residence and the number ofphones enrolled in the service. The Billing Information page shows the user the billing information theyentered on the mobiNotice Enrollment page. The Transaction Detail Page shows the result of thepayment: approved or declined.

Figure 3: Payment Processing Page

P a g e | 14

Figure 4: Billing Information

Figure 5: Transaction Detail

P a g e | 15

During the process of testing you may be given variations in order to test the applications response tocertain conditions. These variations will be provided when those test conditions arise.

1. The payment processing page displays without errorTest Data:Address:Street Number: 7589Street Name: Anywhere DrCity: OaklandState: CAZip: 94605Type of Address: ResidentialPrimary Account Holder:Mobile number: (xxx) xxx-xxxxFirst name: yoursLast name: yoursCredit Card Information:Name On Credit Car Same As Primary Account Holder: CheckedBilling Address Same As Enrollment Address: CheckedTerms:I have reviewed and accepted the mobiNotice Terms of Service: checked

a) With the mobiNotice Enrollment page displaying the Test Data as shown above, click the‘Submit’ button.i) Expected Outcome:The Payment Information page will be displayed. The Primary Account Holder’s mobilenumber will be shown as Reference 1. The Subtotal will be $25, with a Total of $25.iii) Expected Outcome Achieved?


iv) Click ‘Cancel’ you will be taken back to the mobiNotice Enrollment page.2. Validate the correct amount due is presented.

Test Data:Address:Street Number: 7589Street Name: Anywhere DrCity: OaklandState: CAZip: 94605Type of Address: BusinessPrimary Account Holder:Mobile number: (xxx) xxx-xxxxFirst name: yoursLast name: yoursCredit Card Information:Name On Credit Car Same As Primary Account Holder: Checked

P a g e | 16

Billing Address Same As Enrollment Address: CheckedTerms:I have reviewed and accepted the mobiNotice Terms of Service: checked

a) In the previous section you validated the page was presented without error and the basicenrollment cost of $15 for two phones with a $10 set up fee. In this section you will validatethe Business enrollment fees.

i) With the mobiNotice Enrollment page displaying the Test Data as shown above, click the‘Submit’ button.

ii) Expected Outcome:The Payment Information page will be displayed. The Primary Account Holder’s mobilenumber will be shown as Reference 1. The Subtotal will be $30, with a Total of $30.v) Expected Outcome Achieved?


vi) Click ‘Cancel’ you will be taken back to the mobiNotice Enrollment page.b) Validate the application charges the correct amount when more than two phones are

enrolled.i) Make the following changes to the mobiNotice Enrollment page

(1) Type of Address: Residential(2) Enter in two additional mobile phone numbers (enter any xxx-xxx-xxxx numbers –

the phones numbers do not have to be real)

ii) Expected Outcome:The Payment Information page will be displayed. The Primary Account Holder’s mobilenumber will be shown as Reference 1. For three enrolled phones the Subtotal will be $30,with a Total of $30, for four enrolled phones the Subtotal will be $35, with a Total of $35vii) Expected Outcome Achieved?


viii) Enter a credit card number from above. Click ‘Next’ you will be taken to BillingInformation page. Verify Billing Information is as submitted.

c) Test for Payment Declined Conditioni) To perform this verification:

(1) Click the ‘Back’ button on the Billing Information Page to return to the PaymentInformation Page.

(2) CHANGE THE SUBTOTAL AMOUNT TO $2.00.(3) Click the button ‘Next’ to return to the Billing Information Page(4) Click the ’Submit’ button to submit the payment.

ii) Expected OutcomeThe submitted payment will be declined because of an incorrect security code. You will bepresented with a Declined Payment Page as shown in Figure 6 below.

P a g e | 17

Figure 6: Declined Payment Page

iii) Expected Outcome Achieved?Yes No If no,

explain:iv) Click the ‘Retry’ button to be taken back to the mobiNotice Enrollment Page

d) Text for Payment Approved Conditioni) To perform this verification:

(1) Click ‘Submit’ on the mobiNotice Enrollment Page(2) Enter a card number on the Payment Information Page. LEAVE THE SUBTOTAL

AMOUNT AS IS.(3) Enter a CVV value – it doesn’t matter what number you use(4) Click ‘Next’ to go to the Billing Information Page(5) Verify the Billing Information, click ‘Submit’ to submit the payment

ii) Payment Approved(1) Expected Outcome:

The Transaction Detail will indicate the payment was Approved.(2) Expected Outcome Achieved?


P a g e | 18

(3) Click the ‘Close’ button. You will be taken to the Enrollment Status Page, shown inFigure 7: Enrollment Status Page below.

Figure 7: Enrollment Status Page

The Enrollment Status Page indicates to the user the status of the numbers they are enrolling inmobiNotice, provides a sample Blast message, gives access to the Quick Reference Guides for the area inwhich they just enrolled and offers to them the opportunity to create an online access account.

mobiNotice Enrollment StatusAs described above, this page informs the user of the status of their enrollment after successfulpayment. Accepting this page requires the following verification:

1. Validate the page does not display error messages and does not indicate the enrollment failed inany waya) Review the page.

i) If you see any error messages indicating a file was not accessible or there was an sqlerror the page fails.

ii) If you see ‘Retry’ or ‘Done’ buttons along with sample blast messages the page fails.iii) If you don’t see the mobile numbers listed above without an explanation, the page fails.

b) Expected OutcomeThe page will look very similar to the page shown in Figure 7 above. If there are failures in theregistration of the mobile numbers there will be an explanation of the failure. However, in thiscondition, you will not see failures.a) Expected Outcome Achieved?

P a g e | 19


2. The sample message includes the text message short code and the blast keyworda) Review the page

i) Next to ‘Address Message To’ verify the short code is displayedii) Next to ‘Create Message’ verify the first word is a Blast keyword (i.e., SHN)

b) Expected OutcomeYou will see the short code and blast keyword in both the ‘To Send a Blast Alert Message’ and‘Example Blast Alert Message’ tablesc) Expected Outcome Achieved?


3. The user can download sample Quick Reference Guidesa) Below the ‘Example Blast Alert Message’ table, click the HERE link.

i) Review the .pdf file to ensure the area is accurate, and the short code and blast keywordare shown.

b) Expected OutcomeYou will be taken to a .pdf file for the area shown in the title of the page; in this case, SequoyahHills. The Quick Reference Guides are replicated on the file so the user can easily printadditional cards.c) Expected Outcome Achieved?


4. The user can create an online access accounta) Verify the ‘Create New Log In’ button is active.b) Expected OutcomeYou will be taken to the ‘Create a mobiNotice Log In’ page as shown in Figure 8 below.c) Expected Outcome Achieved?


P a g e | 20

Figure 8: Create mobiNotice Log In Page

Create a mobiNotice Log InThis page allows the users of mobiNotice to create an online access account. This account will enablethe ability to manage plans and registered phones. It will also allow the user to view and send blastmessages. The completion of this page marks the end of the enrollment process. Verifying the creationof an online account requires:

1. If necessary, selecting the registered mobile number to use as a user id. This option is availablewhen the user registers more than one phone. If one phone is registered the mobile numberprovided will be shown on the page.a) Expected Outcome – if one number was registered the number will already be listed,

otherwise a dropdown list of available numbers is shown.b) Expected Outcome Achieved?


2. Creating a Strong Password – must be between 8 and 16 characters with at least 1 capital letter,1 number and 1 symbola) Expected Outcome – if the user fails to enter a strong password they will be warned that

they must create a strong password and a red box will appear next to the passwordindicating it is weak. If the user enters a strong password a green box will appear next tothe password indicating it is strong.

b) Expected Outcome Achieved?

P a g e | 21


3. Verifying the entered passworda) Expected Outcome – if the passwords don’t match the user will be informed of the

mismatch.b) Expected Outcome Achieved?


4. Entering a password hinta) Expected Outcome – if the user reenters their password as their hint they will be informed

they cannot use any form of their password as a hint.b) Expected Outcome Achieved?


5. Submitting the forma) Expected Outcome

i) In any case where the requested data is left blank the user will be informed they mustprovide the requested data.

ii) The user will be shown the ‘Create mobiNotice Log In Successful’ page as shown inFigure 9 below


explain:

Figure 9: Create Log In Success Page

P a g e | 22

This completes the mobiNotice Enrollment Process. The next section of this test procedure deals withthe mobiNotice Online Application.

mobiNotice Online ApplicationThis section of the acceptance test procedure will start with logging into the online account and proceedthru each of the functions described previously.

Access2 and ObjectiveThe mobiNotice Enrollment Page shall be accessible from the OakMobi website via the NeighborhoodNotification Services page. The page shall also be available on the OakMobi Products page via theNeighborhood Notification Services link..

The mobiNotice Online component of the mobiNotice service allows the user to: administer theiraccount; create and send blast messages; and, view blast messages. The application consists of thefollowing pages:

Log In Administration Create Blast Message View Blast Message

Depending on the function of the page, a page may have subpages. For example, the Administrationpage also provides access to a Checkout page and a Change Password page. The functions of each pageand subpage are discussed below.

Acceptance Test RequirementsTest Application Access: https://mobiNotice.oakmobi.com/login.php. Use the mobile number andpassword you created on the Create mobiNotice Log In page.

The mobiNotice Online Log In, shown in Figure 10 below, is the gateway page to mobiNotice Online.Access to the remaining pages is limited to users with valid user ids and passwords. A component of thisprocedure shall be to verify access to application pages are limited to authorized users only.

2 During the testing phase of mobiNotice Online the access to the program will be directly through the mobiNoticeLog In page. The live version of the application will allow log in from the Neighborhood Services page of theOakMobi website.

P a g e | 23

Figure 10: mobiNotice Online Log In

Log InThe log in page allows the user to gain access to mobiNotice Online. Verification of the page requiresverifying the user can gain access to their online account.

1. Verify ‘Create mobiNotice Log In Now!’ link transfers the user to the Create mobiNotice Log InPagea) Click link to go to Create mobiNotice Log In pageb) Expected OutcomeYou will be taken to the Create mobiNotice Log In page with no errors or system messagesdisplayedc) Expected Outcome Achieved?


d) Click the browser ‘Back’ button to return to the Log In page2. Verify error is raised when entering wrong mobile number

a) ENTER A NUMBER OTHER THAN THE MOBILE NUMBER YOU USED TO CREATE YOURACCOUNT and your password

b) Expected OutcomeYou will be shown an Invalid Log In page indicating you used the wrong mobile number andasked if you want to retry or quit.c) Expected Outcome Achieved?

P a g e | 24


d) Click the ‘Retry’ button to return to the Log In page3. Verify error is raised when entering the wrong password

a) Enter the mobile number you used to create your account and ENTER AN INCORRECTPASSWORD

b) Expected OutcomeYou will be shown an Invalid Log In page indicating you provided an incorrect password. You willbe shown the hint you provided for your password and informed you have 1 more attemptbefore you are locked out of your account for 24 hours.c) Expected Outcome Achieved?


d) Click ‘Retry’ to return to the Log In page4. Verify access to mobiNotice Online is provided

a) Enter the mobile number and password you used to create your account.b) Expected OutcomeYou will be taken to the Account Administration Pagec) Expected Outcome Achieved?


Account AdministrationThe Account Administration page, shown in Figure 11 below, is the most detailed page in mobiNoticeOnline. This page allows the user to: remove them from the service; add or remove registered phones;change billing information; change registered phone user information; and, review the mobiNotice Plan.

P a g e | 25

Figure 11: Account Administration

Each of these functions is divided among four tables: Enrolled Area; Active Registered Mobile Phones;Billing Account Information; and, mobiNotice Plan Summary. Additionally, if changes by the user causeadditional fees to be incurred, the ‘Submit Cart’ button will be enabled.Enrolled AreaThis section of the Administration page allows the user to see the address they are monitoring, the areaname, the blast keyword, access to the Quick Reference Guide for the area, the date they enrolled in thearea and the ability to remove themselves from the area.

1. Verify address is the same as the Enrollment Address provided on the Enrollment pagea) In the ‘Enrolled Area’ table, verify the Street, City, Zip Code and Area Name.b) Expected OutcomeAddress is the same as the enrolled address used on the Enrollment Addressc) Expected Outcome Achieved?


2. Verify the Blast Keyword and Date Enrolled is correcta) In the ‘Enrolled Area’ table, verify the Blast Keyword and Date Enrolled are providedb) Expected OutcomeEach is shown in the appropriate columnc) Expected Outcome Achieved?


P a g e | 26

3. Verify the Reference Guide for the enrolled area is availablea) In the ‘Enrolled Area’ table, click the downward green arrowb) Expected OutcomeYou are shown the pdf file containing the Quick Reference Guides for the area shown. The blastkeywords are the same in the Enrolled Area table and in the Quick Reference Guidec) Expected Outcome Achieved?


d) Click the browser ‘Back’ button to return to the Administration Pagee) KNOWN ISSUE: Clicking ‘Back’ button from pdf file results in Webpage Expired Notification.

This is being investigated. Refresh the page to work around this issue.4. Verify removal from serviceTHIS FUNCTION WILL BE PERFORMED AT THE END OF THE TESTINGActive Registered Mobile Phones

This table allows the user to add or remove mobile phones from the service and to update names andthe assignment of the primary account responsibility. The ability to add more phones is dependent onthe maximum phones per enrolled household or business. The number of phones allowed under theplan is shown in the mobiNotice Plan Summary table. Specifically, the maximum number of phones inshown on the row labeled ‘Maximum Phones Per Enrolled Household/Business.’ The cost per addedphone is shown on the row labeled ‘Additional Cost Per Phone.’ When adding phones, the cost ofadding the new phone is prorated based on the Renewal Date shown in the Billing Account Information.If the number of active registered mobile phones is less than the maximum phones per enrolledhousehold the ‘Add A Phone’ button will be enabled, otherwise, the ‘Add A Phone’ button will bedisabled.

The process of adding, deleting and updating registered phones will be validated below.

1. Verify the ability to update registered mobile phone user information.a) In any of the textboxes labeled First Name or Last Name change the text to something new.b) Expected Outcome

i) The ‘Update Changes’ button will become enabled and the background color will changeto green.

ii) Clicking the ‘Update Changes’ button results in a dialog indicating the changes weremade, the table is updated and the ‘Update Changes’ button becomes disabled andreturns to a gray background color.

c) Expected Outcome Achieved?Yes No If no,

explain:2. If you have less than the maximum number of phones, verify the process of adding a registered

phonea) Click the ‘Add A Phone’ button in the Active Registered Mobile Phones table

i) Expected Outcome:

P a g e | 27

You will be presented the mobiNotice Register New Mobile Phones page. The number ofphones available for registration will be the difference between the maximum number ofphones for your plan and the number of phones registered to your account.ii) Expected Outcome Achieved?


b) Click the ‘Cancel’ buttoni) Expected Outcome:You will be returned to the Administration page. The ‘Submit Cart’ button will be disabledand the ‘Add A Phone’ button will be enabled.ii) Expected Outcome Achieved?


c) On the Administration page, click the ‘Add A Phone’ button to return to the mobiNoticeRegister New Mobile Phones page.i) Enter a mobile number and user first and last nameii) Click the ‘Submit’ button

(1) Expected Outcome:You are presented a dialog box that tells you to add the numbers to your account toclick the ‘Submit Cart’ button at the bottom of the page.(2) Expected Outcome Achieved?


iii) Click the ‘OK’ button to return to the Administration page.(1) Expected Outcome:On the Administration page you will see the ‘Submit Cart’ button enabled with a greenbackground color. The Active Registered Mobile Phones table will show the ‘NewPhones Pending Checkout’ section of the table, see Figure 12 below.(2) Expected Outcome Achieved?


P a g e | 28

Figure 12: Administration Page Pending New Phones

d) Verify submission of the new phonei) Click ‘Submit Cart’ button

(1) Expected OutcomeYou are taken to the ‘Check Out’ page showing the pending additions to your account,see Figure 13 below. The Check Out page allows the user to review the cost of thechange, remove pending changes and to update billing information(2) Expected Outcome Achieved?


ii) In the ‘Pending Mobile Phones Additions’ section of the page, click an below the‘Remove’ heading(1) Expected Outcome

(a) If you added one phone, you will get a dialog box indicating you have removedall pending payments, otherwise the table will update and the pending numberwill be removed.

(b) Expected Outcome Achieved?Yes No If no,

explain:iii) If you were presented with a dialog box, click ‘OK’ to return to the Administration page.

(1) Expected OutcomeYou will no longer see the pending phone change in the Active Registered MobilePhones table and the ‘Submit Cart’ button will be disabled.

P a g e | 29

(1) Expected Outcome Achieved?Yes No If no,

explain:

Figure 13: Check Out Page

iv) If you removed all of the pending mobile phone changes, click the ‘Add A Phone’ buttonon the Administration page. On the mobiNotice Register New Mobile Phones page,enter a new mobile number and user first and last name. Click the ‘Submit’ button. Youhave now returned to the Administration page showing the pending changes as shownin Figure 12 above. Click the ‘Submit Cart’ button to return to the Check Out page asshown in Figure 13 above.

d) Verify New Service Payment Processingiv) Click ‘Submit’ to process the addition of the new phone.You will be taken through the payment processing cycle like you were for the initialenrollment

(2) Payment Information page(a) Verify the amount due is the same as it was on the Check Out page(b) Enter card number 4111111111111111, CVV 458, click ‘Next’

(3) Expected Outcome – the Billing Information page is shown(4) Expected Outcome Achieved?


P a g e | 30

ii) Verify Billing Information is the same as the Billing Information on the Check Out page,click ‘Submit’(1) Expected Outcome -- For one phone with the cost of $4.95, your payment will be

declined(2) Expected Outcome Achieved?


(3) When presented with the Payment Declined page, click ‘Retry’ to go back to theCheck Out page(a) Click ‘Submit’ to return to the Payment Processing page(b) Using the same credit card number and CVV as above, CHANGE THE SUBTOTAL

AMOUNT TO $3.00(c) Click ‘Next’ to view the Billing Information(d) Click ‘Submit’ to view the Transaction Detail

(i) Expected Outcome – Your payment will be approved.(ii) Expected Outcome Achieved?


(iii) Click ‘Close’ to see the ‘Add Service Results’ page1. Expected Outcome – the page will show that you have opted in the

mobile number and give you a sample blast message as was the case inthe Enrollment process3.

2. Expected Outcome Achieved?Yes No If no,

explain:(4) In the navigation header of the Add Service Page, click the ‘Account Administration’

link to return to the Administration page.(a) Expected Outcome – you are returned to the Administration page and the

number you added is now shown in the Active Registered Mobile Phones table.If you have the maximum number of phones per your plan, the ‘Add A Phone’button will be disabled.

(b) Expected Outcome Achieved?Yes No If no,

explain:3. Verify the ability to remove a registered phone from mobiNotice

a) In the Active Registered Mobile Phones table, click any under the Delete headeri) Expected Outcome – the phone will be removed from the tableii) Expected Outcome Achieved?


3 Under normal conditions, a text message is sent to the user of the newly registered mobile phone informing themthey have been opted into the enrolled area. This feature is disabled during testing.

P a g e | 31

4. Verify the ability to update Billing Account Informationa) Modify any of the values presented in a textbox in the Billing Account Information table

i) Expected Outcome – the ‘Update Billing’ button will become enabled and thebackground color of the button changes to green

ii) Expected Outcome Achieved?Yes No If no,

explain:b) Click the ‘Update Billing’ button

i) Expected Outcome – you will see a dialog box indicating your changes were made.ii) Expected Outcome Achieved?


c) Click the ‘Send Alert Message’ link

Send Alert MessageThe Send Alert Message page, shown in Figure 14 below, allows the user to create and send alertmessages from their computer. The page consists of four sections: Create An Alert Message; ImportantPhone Numbers; Common mobiNotice Message Abbreviations; and, Add New Abbreviation.

Figure 14: Send Alert Message

1. Generally on the page,a) Verify the Import Phone Numbers table and Common mobiNotice Message Abbreviations

table are presented with no errors.b) Verify the abbreviations table scrolls so the user can see all abbreviations.

P a g e | 32

c) Expected OutcomeThe content is shown as stated above.

d) Expected Outcome Achieved?Yes No If no,

explain:2. Verify the page is presented with no errors or systems messages

a) Expected Outcome – page is presented with no errorsb) Expected Outcome Achieved?


3. Verify the user can create, optimize and send a blast messagea) In the Create An Alert Message table, enter a message next to the label ‘Enter your

message’i) Expected Outcome

(1) As you type you will be shown how many characters are remaining in your message(2) Expected Outcome Achieved?


a) Type your message until you get a dialog box indicating you have exceeded your characterlimit.i) Expected Outcome

(1) As you type you will be shown how many characters are remaining in your message(2) Expected Outcome Achieved?


e) Click the ‘Optimize Message’ buttoni) Expected Outcome

(1) The ‘Message With Abbreviations’ box will be populated with your message,replacing words and phrases with abbreviations

(2) The new number of remaining characters, with the abbreviations included, is shownunder the optimized message.


explain:f) Click the ‘Accept Changes’ button

i) Expected Outcome(1) The message you typed will be replaced with the optimized message shown in the

‘Message With Abbreviations’ textbox and the number of remaining characters isupdated


explain:g) Click ‘Send’ to send the message

P a g e | 33

i) Expected Outcome(1) The message shown next to the ‘Enter your message’ textbox will be sent4


explain:h) Type some text into the textbox next to ‘Enter your message’; click the ‘Cancel’ button.

i) Expected Outcome(1) The textbox will be cleared.(2) Expected Outcome Achieved?


4. Verify a new abbreviation can be added to the applicationa) Enter a Word or Phrase and Abbreviation in the Add New Abbreviation tableb) Expected Outcome:

i) You will receive a dialog box indicating your abbreviation was addedii) The Common mobiNotice Message Abbreviations table will be updated

c) Expected Outcome Achieved?Yes No If no,

explain:

View Message AlertsFrom the Send Alert Message page, click the View Message Alerts link in the navigation header to openthe View Message Alerts page, as shown in Figure 15 below.

4 Under normal conditions the message will be sent out. This feature is disabled during testing.

P a g e | 34

Figure 15: View Message Alerts

The View Message Alerts allows the user to view messages based on timeframe, look up commonmessage abbreviations and add new abbreviations.

1. General page overviewa) Verify the page loads without errors or system messages

i) Expected Outcome – page loads without errorsii) Expected Outcome Achieved?


2. Verify user can view messages from different timeframes.a) User can see most recent messagesb) User can see the span of time between the most recent message and 1 week prior to that

messagec) User can see the span of time between the most recent message and 1 month prior to that

messaged) User can see the span of time between the most recent message and 1 year prior to that

messagee) User can see all messages

i) Expected Outcome – user is able to see all messagesii) Expected Outcome Achieved?


3. Verify user can browse Common mobiNotice Message Abbreviations

P a g e | 35

a) Expected Outcome – page loads without errorsb) Expected Outcome Achieved?


4. Verify user can add new abbreviationsa) Expected Outcome – page loads without errorsb) Expected Outcome Achieved?


Log OutPart of the navigation bar on the primary pages is the Log Out link. Clicking this link logs the user out ofmobiNotice Online

1. Verify the user is logged out of the applicationa) Click the ‘Log Out’ link on any navigation barb) Expected Outcome – the user is logged out of the application.c) Expected Outcome Achieved?


Service TerminationDuring the verification of the Account Administration page you were instructed to skip over verifyingyour removal from the service. This section of the acceptance test procedure will remove you from theservice.

1. Verify service terminationa) Log back into mobiNoticeb) Upon successful log in you will be taken to the Account Administration pagec) In the Enrolled Area table, click the under the ‘Delete’ headingd) Expected Outcome – the user will be shown a page indicating the service was terminatede) Expected Outcome Achieved?


Documents

mobiNotice Acceptance Test LinkedIn Version