mobiNotice Acceptance Test LinkedIn Version

P a g e | 1
OakMobi
mobiNotice Neighborhood Alert Service
Acceptance Test Procedure
Version 1.0
Susan Kaymon
5/7/2012

P a g e | 2
Overview
This document provides the acceptance testing process for the newly developed on line version of the
mobiNotice Neighborhood Alert Service (herein known as mobiNotice). This document will outline the
features of the on line service, the functional performance of each page, the objects on the page and
the expected outcome of object events. In the event an object fails to perform as outlined a bug report
shall be created and the bug assigned a level of criticality.
Definition of Terms
Application – a series of web pages inter-linked to provide the full range of functions necessary to
successfully 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 Blast
Message 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 as
defined below:
 Level BI – the application failed to accomplish the task resulting in the user being unable to
properly interact with the application. For example: a link fails to respond or a 401
Unauthorized Access (without an OakMobi Logo) is displayed, 404 Document Not Found
Error 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 incoherent
due 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 interaction
of 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 of
the application
Object – a page element the user interacts with to perform various activities on the page and within the
application.
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 these
requirements will result in a delay in the release of the application.
 Level PII – important but can be de-activated pending correction. Failure to meet these
requirements 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 the
release 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 Summary
The mobiNotice on line application is an extension of the mobiNotice Mobile Neighborhood Alert
Service. The on line application allows new users to enroll in the service while allowing existing users to
manage 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 below
will cover each of these pages and their expected performance.
Figure 1: Top-Level mobiNotice Application
Application Functional Requirements
Every application has specific functional requirements that define the expected performance of the
application. Those requirements for the mobiNotice application are defined below.
Enrollment Top Level Application Performance Objectives
Online mobiNotice Service Enrollment
Performance Level: PI

P a g e | 4
The user shall be able to initiate enrollment in mobiNotice via the OakMobi website. Enrollment shall
include gathering primary account holder name, address and mobile phone number, up to four
additional mobile phone numbers based on the type of address and collecting payment via a third-party
merchant processor.
1. Primary account holder name and mobile number
a) Performance Level: PI
b) The application shall obtain primary account holder name, mobile number and email
address for purposes of billing and contact
2. Additional mobile numbers
a) Performance Level: PII
b) The application shall obtain any additional mobile numbers the user wishes to enroll in the
service
3. Address to enroll
b) 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 purposes
4. Enrolled address type – business or residential
b) The application shall collect the type of address being enrolled. This information is used to
determine the correct billing plan
5. Billing Name and Address
b) 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 information
is used by the third-party payment processor to verify debit/credit card account.
Create Log In
After successfully completing enrollment, the user shall be offered the ability to create an online access
account.
1. Every user with a registered phone shall be able to create an online access to the enrolled
household account
2. The registered phone number shall be verified against the registered number database to
authenticate 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 characters
and 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 them
of their password

P a g e | 5
mobiNotice Online Application
Log In
After creating an online access password, the user shall be able to access the mobiNotice web
application. Access to the application shall enable the user to manage their account, create and send
blast 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 gain
access to the application.
2. The user shall have three failed log in attempts before being locked out of the application for
three 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 a
temporary password to the registered number if it is actually registered with the service. In
the event the mobile number is not registered with the service the user shall be locked out
of the application.
Online mobiNotice Service Administration
Performance Level: PI/PIII
Once successfully enrolled in mobiNotice, the user shall be able to activate online account
administration. Online account administration shall consist of the ability to:
1. Removal from mobiNotice
b) 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: PIII
b) 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 area
where a relative resides.
3. Add or delete registered phones
a) Performance Level: PI/PIII
b) 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 due
based on the plan terms.
(1) Performance Level: PI
iii) A cookie shall be created to hold pending registered phone additions for 30 days or until
payment is collected whichever is met first

P a g e | 6
(1) Performance Level: PIII
4. Update names of registered phone users
b) The user shall be able to modify the names of users indicated for registered phones
5. Change primary account holder
b) The user shall be able to change the primary account holder designation
6. Update primary account address
b) The user shall be able to update their billing address
7. Review plan terms
b) The user shall be able to review but not change mobiNotice plan terms, including
enrollment date, plan costs and allowable phones
8. Change online access password
b) 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
b) 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 shall
collected prior to adding the services to the account.
Create Alert Message
Performance Level: PII
The mobiNotice application shall provide the user the ability to create and send a blast message from
their computer.
1. In the event the user is monitoring more than one area, the application shall allow the user to
select which area to send the blast message to.
2. The application shall display the Blast Keyword for the targeted area
3. The Blast Message length shall be no more than 160 characters, including the length of the blast
keyword
a) 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 application
5. 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 or
phrases for those abbreviations. These abbreviations shall be used by the application to
optimize message length.
View Alert Message
Performance 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 of
messaging.
2. The user shall be able to select a time period of most current message minus one week, one
month, one year or all messages.
3. The messages shall be shown in the form they were texted to the registered users and shall be
cleared of known abbreviations.
4. The application shall enable the user to submit abbreviations to the mobiNotice abbreviations
database.
Detail Page Review and Testing Requirements
This section of the specification shall review each page of the application, its objective and specific
performance expectations. Testing pass/fail criteria shall be established.
mobiNotice Online Service Enrollment
Access1 and Objective
The 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 the
OakMobi Products page via the Neighborhood Notification Services link.
This page gathers the data necessary to determine the appropriate area to enroll the user, determine
the proper service plan and to gather the information required by the merchant processing third-party
vendor. 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 log
in or create log in page as necessary
 Determine in which area the address entered for monitoring resides. If the address is not
contained in an active area, the user will be asked if they want to be contacted to create an
area.
 Determine the appropriate pricing plan. For example: does the address indicate it is part of a
group 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 the
Enrollment Page; if the payment is successful, the user is informed of the opt in status of the
mobile phones they provided and instructed on how to create and send a blast message.
Acceptance Test Requirements
Test page access: https://mobiNotice.oakmobi.com/nnsenroll.html
Figure 2: mobiNotice Enrollment Page, below is a screenshot of the mobiNotice Enrollment Page. The
page 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 Conditions
Tester:
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 Issues
1. 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 page
2. Page needs to be refreshed/resent after opening pdf files
a. Resolved – launched pdf files in their own window
3. Browser back button event needs to be captured
a. Pend – instituted a timeout script to force logout if inactive. Logout destroys the session
4. 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 Application
Enrollment Address Section
1. Partially complete the information requested and click the ‘Submit’ button
a) Expected Outcome: Dialog box informing you that the missing information must be provided
b) Expected Outcome Achieved?
Yes No If no,
explain:
c) Complete Enrollment Address, move to Primary Account Holder Information
Primary Account Holder Information Section
1. Incorrectly complete the Mobile Number entry, i.e.: enter the wrong number of digits or enter
characters
a) 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)
Yes No If no,
explain:
c) Correct the entry as requested
2. Partially complete the remaining requested information and click the ‘Submit’ button
a) Expected Outcome: Dialog box informing you that the missing information must be provided
Yes No If no,
explain:
c) Correct the entry as requested
3. 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’ button
a) Expected Outcome: Dialog box informing you that the email address is invalid
Yes No If no,
explain:
c) Correct the entry as requested, move on to Additional Mobile Numbers
4. 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 Section
5. Click ‘Name on Credit Card Same As Primary Account Holder’ checkbox
a) Expected Outcome: the text boxes with ‘Enter Cardholder First Name’ and ‘Enter Cardholder
Last Name’ will be filled in with the Primary Account Holder Name and the text boxes will be
disabled.
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
Yes No If no,
explain:
c) Check the ‘Billing Address Same as Enrollment Address’ checkbox, move to ‘Submit Form
Section’
a) Expected Outcome: Dialog box indicating that you must accept the mobiNotice Terms
Yes No If no,
explain:
c) Check the ‘I have reviewed and accepted the mobiNotice Terms of Service’ check box.
There are five potential Expected Outcomes of the ‘Submit’ button event. The first you have
already tested – verifying the form data was entered. If the required data was not entered you
received a notice telling you to correct the error. The remaining outcomes are: if the address
you entered does not exist or the Area is not active; the mobile number you entered is already
registered and has an online access account; the mobile number you entered is already
registered but does not have an online access account; the address is correct, the Area exists
and none of the numbers are registered with mobiNotice. Each of these expected outcomes are
described below.
a) Test Condition: Incorrect address
Test Data:
Address:
Street Number: 7590
Street Name: Anywhere Dr
City: Oakland
State: CA
Zip: 94605
Type of Address: Residential
Primary Account Holder:
Mobile number: (xxx) xxx-xxxx

P a g e | 11
First name: yours
Last name: yours
Credit Card Information:
Name On Credit Car Same As Primary Account Holder: Checked
Billing Address Same As Enrollment Address: Checked
Terms:
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 updated
ii) Expected Outcome Achieved?
Yes No If no,
explain:
iii) Correct the Street Number to 7589, CHANGE THE PRIMARY ACCOUNT HOLDER MOBILE
NUMBER TO xxx xxx-xxxx, click ‘Submit’
b) Test Condition: Enrolled mobile number with an online account
Test Data:
Address:
Street Number: 7589
City: Oakland
State: CA
Zip: 94605
First name: yours
Last name: yours
Terms:
You will be redirected to the mobiNotice Log In Form with the mobile number entered.
Yes No If no,
explain:
iii) Click the browers ‘BACK’ button, CHANGE THE PRIMARY ACCOUNT HOLDER MOBILE
NUMBER 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: 7589
City: Oakland
State: CA
Zip: 94605
First name: yours
Last name: yours
Terms:
You will be redirected to the Create a mobiNotice Log In Form with the mobile number
entered. If there is more than one registered phone number without an online access
account you will be asked to select the number you are creating an account for
Yes No If no,
explain:
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 Account
Holder’s mobile number
o User First and Last Names are optional. If left blank the application will use the Primary
Account Holder’s name
 When the ‘Name On Credit Card Same As Primary Account Holder’ and ‘Billing Address Same As
Enrollment Address’ boxes are left unchecked the application verifies the information is entered
and validates the zip code is a number. These procedures were verified in the Enrollment
Address section of the form.
 If the ‘I have reviewed and accepted the mobiNotice Terms of Service’ box is left unchecked the
application will display a message telling the user they must accept the terms.
Payment Processing
This section of the testing focuses on what happens when the user successfully completes the
mobiNotice Enrollment page and clicks the ‘Submit’ button. Upon clicking ‘Submit’ the user is taken to a
third-party merchant processing page, currently Sage Payment Processing. The conditions under test
are:

P a g e | 13
 The payment processing page displays without error and the user’s information is accurately
displayed 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 Code
Visa 4111111111111111 Any three digit number
MasterCard 5499740000000057 Any three digit number
The process of collecting the payment is broken into three pages – the Payment Processing page, shown
in Figure 3: Payment Processing Page, below; the Billing Information Page, shown in Figure 4: Billing
Information below; and, the Transaction Detail Page, shown in Figure 5: Transaction Detail below . The
Payment 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 of
phones enrolled in the service. The Billing Information page shows the user the billing information they
entered on the mobiNotice Enrollment page. The Transaction Detail Page shows the result of the
payment: 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 to
certain conditions. These variations will be provided when those test conditions arise.
1. The payment processing page displays without error
Test Data:
Address:
Street Number: 7589
City: Oakland
State: CA
Zip: 94605
First name: yours
Last name: yours
Terms:
a) With the mobiNotice Enrollment page displaying the Test Data as shown above, click the
‘Submit’ button.
The Payment Information page will be displayed. The Primary Account Holder’s mobile
number will be shown as Reference 1. The Subtotal will be $25, with a Total of $25.
iii) Expected Outcome Achieved?
Yes No If no,
explain:
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: 7589
City: Oakland
State: CA
Zip: 94605
Type of Address: Business
First name: yours
Last name: yours

P a g e | 16
Terms:
a) In the previous section you validated the page was presented without error and the basic
enrollment cost of $15 for two phones with a $10 set up fee. In this section you will validate
the Business enrollment fees.
i) With the mobiNotice Enrollment page displaying the Test Data as shown above, click the
‘Submit’ button.
ii) Expected Outcome:
number will be shown as Reference 1. The Subtotal will be $30, with a Total of $30.
v) Expected Outcome Achieved?
Yes No If no,
explain:
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:
number 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 $35
vii) Expected Outcome Achieved?
Yes No If no,
explain:
viii) Enter a credit card number from above. Click ‘Next’ you will be taken to Billing
Information page. Verify Billing Information is as submitted.
c) Test for Payment Declined Condition
i) To perform this verification:
(1) Click the ‘Back’ button on the Billing Information Page to return to the Payment
Information 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 Outcome
The submitted payment will be declined because of an incorrect security code. You will be
presented 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 Condition
i) 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?
Yes No If no,
explain:

P a g e | 18
(3) Click the ‘Close’ button. You will be taken to the Enrollment Status Page, shown in
Figure 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 in
mobiNotice, provides a sample Blast message, gives access to the Quick Reference Guides for the area in
which they just enrolled and offers to them the opportunity to create an online access account.
mobiNotice Enrollment Status
As described above, this page informs the user of the status of their enrollment after successful
payment. Accepting this page requires the following verification:
1. Validate the page does not display error messages and does not indicate the enrollment failed in
any way
a) Review the page.
i) If you see any error messages indicating a file was not accessible or there was an sql
error 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 Outcome
The page will look very similar to the page shown in Figure 7 above. If there are failures in the
registration of the mobile numbers there will be an explanation of the failure. However, in this
condition, you will not see failures.
a) Expected Outcome Achieved?

P a g e | 19
Yes No If no,
explain:
2. The sample message includes the text message short code and the blast keyword
a) Review the page
i) Next to ‘Address Message To’ verify the short code is displayed
ii) Next to ‘Create Message’ verify the first word is a Blast keyword (i.e., SHN)
b) Expected Outcome
You will see the short code and blast keyword in both the ‘To Send a Blast Alert Message’ and
‘Example Blast Alert Message’ tables
c) Expected Outcome Achieved?
Yes No If no,
explain:
3. The user can download sample Quick Reference Guides
a) 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 keyword
are shown.
b) Expected Outcome
You will be taken to a .pdf file for the area shown in the title of the page; in this case, Sequoyah
Hills. The Quick Reference Guides are replicated on the file so the user can easily print
additional cards.
Yes No If no,
explain:
4. The user can create an online access account
a) Verify the ‘Create New Log In’ button is active.
b) Expected Outcome
You will be taken to the ‘Create a mobiNotice Log In’ page as shown in Figure 8 below.
Yes No If no,
explain:

P a g e | 20
Figure 8: Create mobiNotice Log In Page
Create a mobiNotice Log In
This page allows the users of mobiNotice to create an online access account. This account will enable
the ability to manage plans and registered phones. It will also allow the user to view and send blast
messages. The completion of this page marks the end of the enrollment process. Verifying the creation
of an online account requires:
1. If necessary, selecting the registered mobile number to use as a user id. This option is available
when the user registers more than one phone. If one phone is registered the mobile number
provided 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.
Yes No If no,
explain:
2. Creating a Strong Password – must be between 8 and 16 characters with at least 1 capital letter,
1 number and 1 symbol
a) 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 password
indicating it is weak. If the user enters a strong password a green box will appear next to
the password indicating it is strong.

P a g e | 21
Yes No If no,
explain:
3. Verifying the entered password
a) Expected Outcome – if the passwords don’t match the user will be informed of the
mismatch.
Yes No If no,
explain:
4. Entering a password hint
a) 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.
Yes No If no,
explain:
5. Submitting the form
a) Expected Outcome
i) In any case where the requested data is left blank the user will be informed they must
provide the requested data.
ii) The user will be shown the ‘Create mobiNotice Log In Successful’ page as shown in
Figure 9 below
Yes No If no,
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 with
the mobiNotice Online Application.
mobiNotice Online Application
This section of the acceptance test procedure will start with logging into the online account and proceed
thru each of the functions described previously.
Access2 and Objective
The mobiNotice Enrollment Page shall be accessible from the OakMobi website via the Neighborhood
Notification Services page. The page shall also be available on the OakMobi Products page via the
Neighborhood Notification Services link..
The mobiNotice Online component of the mobiNotice service allows the user to: administer their
account; create and send blast messages; and, view blast messages. The application consists of the
following 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 Administration
page also provides access to a Checkout page and a Change Password page. The functions of each page
and subpage are discussed below.
Acceptance Test Requirements
Test Application Access: https://mobiNotice.oakmobi.com/login.php. Use the mobile number and
password 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 this
procedure 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 mobiNotice
Log In page. The live version of the application will allow log in from the Neighborhood Services page of the
OakMobi website.

P a g e | 23
Figure 10: mobiNotice Online Log In
Log In
The log in page allows the user to gain access to mobiNotice Online. Verification of the page requires
verifying 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 In
Page
a) Click link to go to Create mobiNotice Log In page
b) Expected Outcome
You will be taken to the Create mobiNotice Log In page with no errors or system messages
displayed
Yes No If no,
explain:
d) Click the browser ‘Back’ button to return to the Log In page
2. Verify error is raised when entering wrong mobile number
a) ENTER A NUMBER OTHER THAN THE MOBILE NUMBER YOU USED TO CREATE YOUR
ACCOUNT and your password
b) Expected Outcome
You will be shown an Invalid Log In page indicating you used the wrong mobile number and
asked if you want to retry or quit.

P a g e | 24
Yes No If no,
explain:
d) Click the ‘Retry’ button to return to the Log In page
3. Verify error is raised when entering the wrong password
a) Enter the mobile number you used to create your account and ENTER AN INCORRECT
PASSWORD
b) Expected Outcome
You will be shown an Invalid Log In page indicating you provided an incorrect password. You will
be shown the hint you provided for your password and informed you have 1 more attempt
before you are locked out of your account for 24 hours.
Yes No If no,
explain:
d) Click ‘Retry’ to return to the Log In page
4. Verify access to mobiNotice Online is provided
a) Enter the mobile number and password you used to create your account.
b) Expected Outcome
You will be taken to the Account Administration Page
Yes No If no,
explain:
Account Administration
The Account Administration page, shown in Figure 11 below, is the most detailed page in mobiNotice
Online. 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 cause
additional fees to be incurred, the ‘Submit Cart’ button will be enabled.
Enrolled Area
This section of the Administration page allows the user to see the address they are monitoring, the area
name, the blast keyword, access to the Quick Reference Guide for the area, the date they enrolled in the
area and the ability to remove themselves from the area.
1. Verify address is the same as the Enrollment Address provided on the Enrollment page
a) In the ‘Enrolled Area’ table, verify the Street, City, Zip Code and Area Name.
b) Expected Outcome
Address is the same as the enrolled address used on the Enrollment Address
Yes No If no,
explain:
2. Verify the Blast Keyword and Date Enrolled is correct
a) In the ‘Enrolled Area’ table, verify the Blast Keyword and Date Enrolled are provided
b) Expected Outcome
Each is shown in the appropriate column
Yes No If no,
explain:

P a g e | 26
3. Verify the Reference Guide for the enrolled area is available
a) In the ‘Enrolled Area’ table, click the downward green arrow
b) Expected Outcome
You are shown the pdf file containing the Quick Reference Guides for the area shown. The blast
keywords are the same in the Enrolled Area table and in the Quick Reference Guide
Yes No If no,
explain:
d) Click the browser ‘Back’ button to return to the Administration Page
e) 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 service
THIS FUNCTION WILL BE PERFORMED AT THE END OF THE TESTING
Active Registered Mobile Phones
This table allows the user to add or remove mobile phones from the service and to update names and
the assignment of the primary account responsibility. The ability to add more phones is dependent on
the maximum phones per enrolled household or business. The number of phones allowed under the
plan is shown in the mobiNotice Plan Summary table. Specifically, the maximum number of phones in
shown on the row labeled ‘Maximum Phones Per Enrolled Household/Business.’ The cost per added
phone is shown on the row labeled ‘Additional Cost Per Phone.’ When adding phones, the cost of
adding 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 enrolled
household the ‘Add A Phone’ button will be enabled, otherwise, the ‘Add A Phone’ button will be
disabled.
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 change
to green.
ii) Clicking the ‘Update Changes’ button results in a dialog indicating the changes were
made, the table is updated and the ‘Update Changes’ button becomes disabled and
returns to a gray background color.
Yes No If no,
explain:
2. If you have less than the maximum number of phones, verify the process of adding a registered
phone
a) Click the ‘Add A Phone’ button in the Active Registered Mobile Phones table

P a g e | 27
You will be presented the mobiNotice Register New Mobile Phones page. The number of
phones available for registration will be the difference between the maximum number of
phones for your plan and the number of phones registered to your account.
Yes No If no,
explain:
b) Click the ‘Cancel’ button
You will be returned to the Administration page. The ‘Submit Cart’ button will be disabled
and the ‘Add A Phone’ button will be enabled.
Yes No If no,
explain:
c) On the Administration page, click the ‘Add A Phone’ button to return to the mobiNotice
Register New Mobile Phones page.
i) Enter a mobile number and user first and last name
ii) Click the ‘Submit’ button
You are presented a dialog box that tells you to add the numbers to your account to
click the ‘Submit Cart’ button at the bottom of the page.
Yes No If no,
explain:
iii) Click the ‘OK’ button to return to the Administration page.
On the Administration page you will see the ‘Submit Cart’ button enabled with a green
background color. The Active Registered Mobile Phones table will show the ‘New
Phones Pending Checkout’ section of the table, see Figure 12 below.
Yes No If no,
explain:

P a g e | 28
Figure 12: Administration Page Pending New Phones
d) Verify submission of the new phone
i) Click ‘Submit Cart’ button
(1) Expected Outcome
You 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 the
change, remove pending changes and to update billing information
Yes No If no,
explain:
ii) In the ‘Pending Mobile Phones Additions’ section of the page, click an below the
‘Remove’ heading
(a) If you added one phone, you will get a dialog box indicating you have removed
all pending payments, otherwise the table will update and the pending number
will 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.
You will no longer see the pending phone change in the Active Registered Mobile
Phones table and the ‘Submit Cart’ button will be disabled.

P a g e | 29
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’ button
on 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. You
have now returned to the Administration page showing the pending changes as shown
in Figure 12 above. Click the ‘Submit Cart’ button to return to the Check Out page as
shown in Figure 13 above.
d) Verify New Service Payment Processing
iv) Click ‘Submit’ to process the addition of the new phone.
You will be taken through the payment processing cycle like you were for the initial
enrollment
(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
Yes No If no,
explain:

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
Yes No If no,
explain:
(3) When presented with the Payment Declined page, click ‘Retry’ to go back to the
Check 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?
Yes No If no,
explain:
(iii) Click ‘Close’ to see the ‘Add Service Results’ page
1. 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 in
the 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 header
i) Expected Outcome – the phone will be removed from the table
Yes No If no,
explain:
3
Under normal conditions, a text message is sent to the user of the newly registered mobile phone informing them
they 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 Information
a) 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 the
background color of the button changes to green
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.
Yes No If no,
explain:
c) Click the ‘Send Alert Message’ link
Send Alert Message
The Send Alert Message page, shown in Figure 14 below, allows the user to create and send alert
messages from their computer. The page consists of four sections: Create An Alert Message; Important
Phone 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 Outcome
The 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 errors
Yes No If no,
explain:
3. Verify the user can create, optimize and send a blast message
a) 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
Yes No If no,
explain:
a) Type your message until you get a dialog box indicating you have exceeded your character
limit.
i) Expected Outcome
(1) As you type you will be shown how many characters are remaining in your message
Yes No If no,
explain:
e) Click the ‘Optimize Message’ button
i) 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 shown
under the optimized message.
Yes No If no,
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 is
updated
Yes No If no,
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
Yes No If no,
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.
Yes No If no,
explain:
4. Verify a new abbreviation can be added to the application
a) Enter a Word or Phrase and Abbreviation in the Add New Abbreviation table
b) Expected Outcome:
i) You will receive a dialog box indicating your abbreviation was added
ii) The Common mobiNotice Message Abbreviations table will be updated
Yes No If no,
explain:
View Message Alerts
From the Send Alert Message page, click the View Message Alerts link in the navigation header to open
the 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 common
message abbreviations and add new abbreviations.
1. General page overview
a) Verify the page loads without errors or system messages
i) Expected Outcome – page loads without errors
Yes No If no,
explain:
2. Verify user can view messages from different timeframes.
a) User can see most recent messages
b) User can see the span of time between the most recent message and 1 week prior to that
message
c) User can see the span of time between the most recent message and 1 month prior to that
message
d) User can see the span of time between the most recent message and 1 year prior to that
message
e) User can see all messages
i) Expected Outcome – user is able to see all messages
Yes No If no,
explain:
3. Verify user can browse Common mobiNotice Message Abbreviations

P a g e | 35
a) Expected Outcome – page loads without errors
Yes No If no,
explain:
4. Verify user can add new abbreviations
a) Expected Outcome – page loads without errors
Yes No If no,
explain:
Log Out
Part of the navigation bar on the primary pages is the Log Out link. Clicking this link logs the user out of
mobiNotice Online
1. Verify the user is logged out of the application
a) Click the ‘Log Out’ link on any navigation bar
b) Expected Outcome – the user is logged out of the application.
Yes No If no,
explain:
Service Termination
During the verification of the Account Administration page you were instructed to skip over verifying
your removal from the service. This section of the acceptance test procedure will remove you from the
service.
1. Verify service termination
a) Log back into mobiNotice
b) Upon successful log in you will be taken to the Account Administration page
c) In the Enrolled Area table, click the under the ‘Delete’ heading
d) Expected Outcome – the user will be shown a page indicating the service was terminated
e) Expected Outcome Achieved?
Yes No If no,
explain:

mobiNotice Acceptance Test LinkedIn Version

Recommended

Recommended

More Related Content

Similar to mobiNotice Acceptance Test LinkedIn Version

Similar to mobiNotice Acceptance Test LinkedIn Version (20)

mobiNotice Acceptance Test LinkedIn Version