You are on page 1of 216

Process /

Error #
screen

Call center upsell


8
- Campaign
Call center upsell
9
- Campaign

Call center upsell


10
- Campaign
17 Make a Payment

27 Agent Upsell
96 Policy Enquiry

102 Request Approval


121 Agent Upsell
176 Client Services
189 Agent Upsell
190 Agent Upsell

200 Change in Policy


214 USSD Upsell

222 SMS Log


226 Create Policy

227 SMS Log


232 Process Airtime

233 Process Airtime


236 Process Airtime

237 Process Airtime


Process Premium
242
MM

263 USSD Upsell


264 USSD Upsell

265 USSD Upsell


266 USSD Upsell

268 Policy Enquiry

269 Loyalty Uploader


270 Loyalty Uploader

273 Loyalty Uploader


Process Premium
274
MM

SA Policy
275
Renewal
278 Create Policy

281 Change in Policy


Changing
282 Payment
mechanism

283 Agent Upsell


Changing
284 Payment
mechanism

287 Claim Assessor


288 Claim Assessor

294 Claim Assessor


295 Claim Assessor

296 Claim Assessor

303 Policy Enquiry


Changing
305 Payment
mechanism

Changing
306 Payment
mechanism
Changing
307 Payment
mechanism

Changing
308 Payment
mechanism
309 SMS Log
310 SMS Log

Changing
311 Payment
mechanism
312 Create Policy
Detail of error

Proceed button against records not behaving correctly. If status has not changed to "Offer Accepted
Create Policy.

Actual Result
1. Select Batch Description from dropdown box.
2. Page get displayed with records. Change status to Offer Declined, Call Back; then click on 'Proce
3.Error message not displayed as 'Please select applicable status to proceed with Policy creation. In
to create policy page.

Test Data - Set status as Offer Declined /Call Back for lead record

Expected Result
Error message should get displayed as 'Please select applicable status (Offer Accepted) to proceed
Change Call Status to 'Follow up' without providing Follow Up date and or remarks for re lead disp
message get displayed.

Actual Result
1. Select Batch Description from dropdown box.
2. Page get displayed with records. Change status to 'Call Back'; without providing Follow Up date
button.
3. Green box appeared on page with message content 'Done' and data removed from batch file..

Test Data
User select uploaded batch name, update details.

Expected Result
Error message should get displayed as 'Please update follow up date, remark for lead {lead Name}

Updating leads details with Call Status as 'Offer Rejected', set follow Up date as future date value a
displayed as follow date is not applicable.

Actual Result
1. Select Batch Description from dropdown box.
2. Page get displayed with records. Change status to 'Offer Declined'; Set follow up date as future d
3. Green box appeared on page with message content 'Done' and data removed from batch file.

Test Data
User select uploaded batch name, update details.

Expected Result
Error message should get displayed as "Follow up date is not applicable if call status is Offer rejecte
User is not able to make the payment/purchase hospital cash. Please refer the steps below
1. Dial the short code
2. Select option 4 Client Services
3. Select option 6 Make A payment--->Go to confirmation screen and choose Yes to pay
4. User is presented with the screen message -"In a few moment you will ....."

Expected Result: User should get a popup on his handset to enter his M-sente PIN
Actual Result: No popup is available at the moment. User is not able to make the payment

Language selection option not get prompted when short code dialed for Agent MSISDN
Steps:
User Dialed Short code as *142*5#.

Actual result
Main menu get not appeared with below options "Main menu should appears with below options
1. Free Insurance
2. Buy Insurance
3. Check Status
4. Client Services
5. Agent (if dialed user is Agent) Correct"

Expected Result
Main menu should appears with below options
First Language Selection.
Value for 'User Id' and 'Create Date' column get displayed in CSD screen for policy which is created
Created via USSD.

Actual Result
1. User go to CSD menu, searched for MSISDN '256713107708' which is created via CoreApp and s
2. User get navigated to CSD screen with details for selected MSISDN, Value for 'User Id' and 'Creat
3. Searched for MSISDN '713107705' which is created via USSD and selected.

Value for 'User Id' and 'Create Date' column get not displayed on screen.

Test Data
Used MSISDN '256713107708' & '713107705' for checks.

Expected Result
Value for 'User Id' and 'Create Date' column should get displayed on screen for each policy which is

After click on Code glass button, Pop up get displayed with 4 code description.

Actual Result
1. User go to menu 'Request Approval', entered valid request number and clicked on 'Execute Quer
2. All the data get auto populated in autopulated fields against entered request number.
3. Clicked on code glass button,

Pop up get displayed with list of 4 code description which is below:


DECLINED
POSTPONED
CREATE RESERVE
REPUDIATE I/C OUTRIGHT

Test Data
Used claim number as '285'.

Actual Result
According to Nigel:
First time Decision button is clicked: only available description should be CREATE RESERVE.
Displayed message is incorrect for active policy with Individual cover and pay method as Airtime.

Actual Result
1.Entered valid mobile number with active upsell coverage and clicked on send button.
2.Below prompt message get displayed as:
"Client has already purchased insurance.@Individual/Family@Hospital Cash active until@1/9/2017
@monthly/yearly@"

Test Data
Used MSISDN 723481816

Expected Result
Below message should get displayed on screen:
"Client has already purchased insurance. Individual Hospital Cash active until [DATE]. Premium: Air

[DATE] = next renewal date


After selection of menu 'Add/change policy details', Message get displayed incorrect for user,who is
loyality coverage.

Actual Result: (Used Simulator for testing)


1. User dialed short code as *142*5#, choose language as english.
2. Goto menu 'Client Services'>>'Add/change policy details'

Message get displayed as below:


"Your name: Jeremy~Press 1 to change your details. For changes to family policy, dial [call centre].

Test Data
Used MSISDN as "789456322"

Expected Result
Error message TBC by business.
Policy does not get created using Agent Upsell for Hospital Cash for individual.

Actual Result
1. User dialed USSD Short code on mobile.(If the dialed user is Agent)
2. Entered client MSISDN number for not yet registered customer.
3. Prompt message get displayed on screen as: "Client has not yet registered for U-insured .To regi
4. Entered client name and press 'Send' button. Then after pressed 1 for Purchase Policy.
5. New prompt get displayed on screen as below: 1.Buy for Individual, 2.Buy for family.
6. Option 1.Buy for Individual selected with payment method as Airtime/Mobile money

Policy details does not get recorded in Core app and doesnot displayed in Policy enquiry page(CSD

Test Data
Used not yet registered MSISDN 7153045635.

Expected Result
Captured policy details by agent should get displayed in CSD Screen with appropriate status as con
Policy does not get created using Agent Upsell for Hospital Cash for family.

Actual Result
1. User dialed USSD Short code on mobile.(If the dialed user is Agent)
2. Entered client MSISDN number for not yet registered customer.
3. Prompt message get displayed on screen as: "Client has not yet registered for U-insured .To regi
4. Entered client name and press 'Send' button. Then after pressed 1 for Purchase Policy.
5. New prompt get displayed on screen as below: 1.Buy for Individual, 2.Buy for family.
6. Option 2.Buy for family selected with payment method as Airtime/Mobile money

Policy details does not get recorded in Core app and doesnot displayed in Policy enquiry page(CSD

Test Data
Used not yet registered MSISDN 7153045635.

Expected Result
Captured policy details by agent should get displayed in CSD Screen with appropriate status as con

Policy change observations requires confirmations or feed back on implemented approach.

Actual Result
1. User go to 'Change In Policy Plan' page, Selected MSISDN & updated the 'Payment Method' & 'Co
2. Policy details get updated.
3. User go to 'CSD' menu and searched for same MSISDN which is selected for update in 'Change In

Changed in "Status Date, Gross Premium and Pay Mode" does not get reflected on CSD screen.

Test Data
Used any active MSISDN No. with active upsell coverage.

Query
When "Status Date, Gross Premium & Pay Mode" get update on CSD Screen???
User does not get prompted for next prompt based on user registration status, who is registered fo
client request.

Actual Result (Used Simulator for Testing)


1. User dialed short code and Selected menu option 'Buy insurance'.

User get prompted for next prompt and content get displayed on screen as:
"Please select the required option:~1. ~2. ~3. ~4."

Test Data
Used MSISDN as '713106624'

Expected Result
User should get prompted for next prompt based on user registration status and content should ge

Query
1. What kind of prompt message should get displayed in case of terminated policy????TBC by busin

Proposal No. and Policy No. does not get displayed for broken bone policy.

Actual Result
1. User go to 'Create Policy' menu and register for a broken bone policy against MSISDN.
2. Go to Tele Sale>Reports>SMS Log - Entered MSISDN, registered for broken bone policy and click

Proposal No. and Policy No. does not get displayed against MSISDN.

Test Data
Used MSISDN as '256713106636'

Expected Result
Proposal No. and Policy No. should get displayed for broken bone policy against MSISDN.
Correct 'SMS Status' value should get displayed and please define how it works???
'SMS Process Date' should get displayed for both hospital cash and broken bone policy.
Lead Upload>> Campaign>> Selected batch description>> Clicked on Proceed Button>> User ge
Middle Name & Last Name" get populated.

Actual Result :
1. User go to menu 'Campaign', selected batch from list, List of value get displayed on screen.
2. Clicked on proceed button, User get navigated to Create Policy page with respective details agai

#. "First Name get displayed in 'First Name' input box, remaining all the word from full name get di
#. "First Name, Middle Name & Last Name" Input box became non-editable.
#. User clicked on 'Last Name' input box and entered any button from keyboard, spaces get remov

Test Data
Used MSISDN as "713106648" and Full Name in CSV File as "RAM SHANKAR PRASAD YADAV"

Query
Example - 1: (Full Name which has 1, 2, 3, 4 and more than 4 word)
1. How "First Name, Middle Name & Last Name" will get displayed in respective input box.
2. "First Name, Middle Name & Last Name" Input box should be editable or non editable??
3. Name which has 4 word or more than 4 word, how system will define - which is middle name???
4. In case of name which has 4 or more than 4 word, How name will get displayed in "First Name, M

SMS content get displayed incorrect, User registered through 'Agent Upsell', Individual-M-sente mo

Actual Result
1.User registered hospital cash plan with Individual,m-sente monthly policy
2.Log In core app
3.Select Policy & Administration>Tele Sale>Reports>SMS Log
4.Message content get displayed as
"To confirm you agree to pay XX each month via airtime deductions for U-Insured hospital cash insu
Note
Message displayed is for airtime instead of M-Sente payment method

Test data
Used MSISDN 725304640 to check the SMS LOG

Expected Result
SMS should displayed as "Do they understand they can pay premium from M-Sente account anytim
at end of the month. 1.Yes 2.No"
Policy renewal is not working as expected for user,who has active Upsell individual cover and Airtim

Actual Result:
1. Created a policy with policy number "256713106678-HCP-U-20170123"
2. Go to menu "Premium Deduction Form" and entered 4 records with date 23/01/17, 24/01/17, 25/
policy.
3. Set last processed date as "23-FEB-17" as Policy maturity date and renewed the policy by menu
4. Go to CSD menu and searched for respective MSISDN, Observations are below:-
#. Maturity date does not get set as "23-MAR-17".
#. Only 4 deductions completed From 23-JAN-17 to 23-FEB-17, But reduced Sum Assured does n
"100000".
#. After renewal process status get set as: "Suspended".

Test Data:
Used Policy number as "256713106678-HCP-U-20170123"

Expected Result:
1. Maturity date should get set according to policy renewal date.
2. Sum Assured should get set based on the premium deductions.
3. Status should get set according to Premium deductions as 'Active' for respective policy.

In case of no payment during waiting period - Policy renewal is not working as expected for user,w
Method.

Actual Result:
1. Created a policy with policy number "256713106679-HCP-U-20170123" and policy is in waiting p
2. Do not entered any record in menu "Premium Deduction Form" to mark any airtime deductions a
3. Set last processed date as "23-FEB-17" as Policy maturity date and renewed the policy by menu
4. Go to CSD menu and searched for respective MSISDN, Observations are below:-
#. Not a single deductions completed From 23-JAN-17 to 23-FEB-17, But Sum Assured does not g
"100000".
#. After renewal process status get set as: "Suspended".

Test Data:
Used Policy number as "256713106679-HCP-U-20170123"

Expected Result:
1. Sum Assured should get set as '0' based on the premium deductions.
2. Status should get set as 'NTU' according to Premium deductions for respective policy.

Query: What Maturity date should get set for NTU Policy???
Incorrect sms notification sent to customer Mobile Number for each daily airtime deductions.

Actual Result:
1. Created a policy with policy number "256713106680-HCP-U-20170124"
2. Go to menu "Premium Deduction Form" and entered 20 records to mark 20 airtime deductions a
3. Go to menu 'SMS Log' and searched for MSISDN "256713106680"
4. 20 premium deduction SMS get displayed in sms log as below:

"Your full monthly premium of 460 has been successfully deducted. Your U-Insured Hospital Cash p
100,000 per night in hospital. Dial *175# or call 100 for more info. Further deductions for next mon

Test Data: Used MSISDN "256713106680" for sms check.

Expected - Appropriate SMS message should get displayed.

Note: above SMS is applicable if 20 daily airtime deduction get completed.

In case of Full premium paid - Policy does not get updated as par rule set based on the airtime ded

Actual Result:
1. Created a policy with policy number "256713106680-HCP-U-20170124"
2. Go to menu "Premium Deduction Form" and entered 20 records to mark 20 airtime deductions a
3. Set last processed date as "24-FEB-17" as Policy maturity date and renewed the policy by menu
4. Go to CSD menu and searched for respective MSISDN, Observations are below:-
#. Policy status get set as suspended instead of active inforce.
#. Maturity date does not get moved forward 1 month.

Test Data:
Used Policy number as "256713106678-HCP-U-20170123"

Expected Result:
1. Policy status: remains Active (Inforce)
2. Maturity date should get moved forward 1 month.
In case of waiting period - If 3 days before renewal date, premium not received. SMS content get d
individual cover and M-Sente monthly pay method.

Actual Result:
1. Created a new policy with policy no. "256713106681-HCP-U-20170125" and do not pay premium
2. Go to "SMS Reminder Process" menu and set the date as 3 days before renewal date.
3. Go to "SMS Log" menu and searched sms for respective MSISDN, Below SMS content get display
"You have not yet paid the next premium to renew your UTL Hospital Cash Plan policy. Please pay 5
suspended."

Test Data: Used MSISDN "256713106681" to check the SMS content.

Expected Result:
1. As per my understanding below sms content should get displayed for Policy which is in waiting p
received.

"You have not yet paid the next premium to renew your UTL Hospital Cash Plan policy. Please pay 5
terminated."

Query: What SMS content should get displayed in SMS Log for policy which is in waiting period and

Wrong prompt' get displayed when Policy Terminated & again purchased hospital cash plan with Ind
Insurance

Actual Result
1) Dialed USSD Short code *142*5#
2) Selected Option 1.Free Insurance
3) Message get displayed as below-
"No active free insurance this month. Use UTL voice, SMS or data to qualify for next month. 2x ben
1.Yes
2.No
4) Selected option 1.Yes
5) Next Prompt get displayed as - "Buy insurance"

Test Data
Used Customer Sim card 713108822 for testing

Expected Result
Message should get displayed - "You have already bought Hospital Cash insurance and your policy
Prompt get displayed with empty options, policy terminated & again policy purchased for hospital c
selected Option '2.Buy insurance'

Actual Result
1) Dialed USSD Short code *142*5#
2) Selected Option 2.Buy insurance
3) Prompt get displayed below-
Please select the required option
1.
2.
3.
4.

Test Data
Used Customer Sim card 713108822 for testing

Expected Result
Message should get displayed - "You have already bought Hospital Cash insurance and your policy

Prompt get displayed with empty options - policy terminated & again policy purchased for hospital
Option 4.Client Services>>Change How to Pay"

Actual Result
1) Dialed USSD Short code *142*5#
2) Selected Option 4.Client Services>>Change How To pay
3) Prompt get displayed below-
Please select the required option
1.
2.
3.
4.

Test Data
Used Customer Sim card 713108822 for testing

Expected Result
Message should get displayed as below:-
Switch to:
(1) airtime, 9,200 monthly
(2) M-Sente, 58,300 yearly
(3) cancel switch.
Prompt get displayed with empty options - policy terminated & again policy purchased for hospital
Option 4.Client Services>>Terminate Policy"

Actual Result
1) Dialed USSD Short code *142*5#
2) Selected Option "4.Client Services>>Terminate Policy"
3) Prompt get displayed below as :-
"Please select the required option"
1.
2.

Test Data
Used Customer Sim card 713108822 for testing

Expected Result
Message should get displayed as below:-
"Press 1 to Confirm that you would like to terminate your Hospital Cash policy."

Different maturity date get set for UTL Broken Bone policy when created through CoreApp interface

Actual Result:
1. User go to CSD menu, searched for MSISDN '256713106712' and selected the MSISDN.
2. User get navigated to CSD screen with details for selected MSISDN.

Core app maturity date setup: Maturity Date get appeared as '01-MAY-25' for policy number - "2567
01-02-2017.

Test Data: Used MSISDN as "256713106712".

Expected Result: Maturity Date should get displayed according to policy comm. date.

Loyalty M-Sente Usage Csv Uploader - CSV file does not get uploaded.

Actual Result:
1. Created a Valid CSV File with File name as: "End-to-end test - Jan MM"
2. Go to Policy & Administration>Tele Sale>Transactions>Loyalty Uploader>Loyalty M-Sente Usage
3. Browsed above explained CSV file and clicked on 'Next' button, User get navigated to 'Table Map
4. Then after clicked on 'Next' button'.

User does not get navigated to next page based on load data and error occured as below:
"ORA-00942: table or view does not exist"

Test Data: Used valid CSV file.

Expected Result:
1. After click on 'Next' button, User should get navigated to next page based on 'Load Data'.
Loyalty CUG Member CSV Uploader - CSV file does not get uploaded.

Actual Result:
1. Created a Valid CSV File with File name as: "CUG Customer Jan"
2. Go to Policy & Administration>Tele Sale>Transactions>Loyalty Uploader>Loyalty CUG Member C
3. Browsed above explained CSV file and clicked on 'Next' button, User get navigated to 'Table Map
4. Then after clicked on 'Next' button'.

User does not get navigated to next page based on load data and error occured as below:
"ORA-00942: table or view does not exist"

Test Data: Used valid CSV file.

Expected Result:
1. After click on 'Next' button, User should get navigated to next page based on 'Load Data'.

Loyalty Cover - "Loyalty Cover" menu is not working properly.

Actual Result:
1. Created a Valid CSV File with File name as: "End-to-end test - Jan airtime"
2. Go to Policy & Administration>Tele Sale>Transactions>Loyalty Uploader>Loyalty Airtime Usage
3. Go to Policy & Administration>Tele Sale>Transactions>Loyalty Uploader>Loyalty Cover
4. Set Date From as 1-Jan-17 and Date To as 31-Jan-17, then after clicked on Process button.

Error message get appeared on screen as below:


ORA-06550: line 2, column 3: PLS-00306: wrong number or types of arguments in call to 'MAIN' OR

5. Again Set Date From as 1-Feb-17 and Date To as 28-Feb-17, then after clicked on Process but
Error message get appeared on screen as below:
ORA-06550: line 2, column 3: PLS-00306: wrong number or types of arguments in call to 'MAIN' OR

Test Data: Used valid CSV file.

Expected Result:
1. "Loyalty Cover" should work properly.
Maturity date does not get set correctly, If policy status moved from active to suspended.

Actual Result:
1. User created a policy with policy number "256713106722-HCP-U-20170203", where policy creati
2. User go to "Premium deduction Form" menu and paid the premium on the date of 03-FEB-17.
3. Go to 'Process Due Criteria' menu, and set "Last Process Date" as 03-MAR-17.
4. Go to SA Policy Renewal menu,and renewed the policy.
5. Go to CSD menu and searched for MSISDN "256713106722"
6. Verified policy maturity date, sum assured & status, Maturity date get displayed as 03-APR-17.
7. Again go to 'Process Due Criteria' menu, and set "Last Process Date" as 03-APR-17.
8. Go to SA Policy Renewal menu,and renewed the policy.
9. Go to CSD menu and searched for MSISDN "256713106722"
10. Verified policy maturity date, sum assured & status.

Maturity Date does not get set as "03-MAY-17"


Sum Assured does not get displayed as "0"
Policy Status get displayed as: "NTU"

Test Data: Used MSISDN "256713106722" & Policy No. as: "256713106722-HCP-U-20170203" for ch

Expected Result:
1. Maturity Date should get set as "03-MAY-17", If policy status moved from active to suspended.
2. Sum Assured should get displayed as "0"
3. Policy Status should get set as: "Suspended"

In case of partial premium paid for previous month - Valid Policy does not get renewed for user who

Actual Result:
1. Created a policy with valid MSISDN which is "256713106734"
2. Go to menu "Premium Deduction Form" and entered 2 records to mark 2 airtime deductions aga
3. Set last processed date as Policy maturity date and tried to renewed the policy by menu 'SA Poli

Policy doe not get renewed and one error message get displayed in the bottom of page as: "FRM-4
exception ORA-00001."

Expected Result:
1. Policy should get renewed.
2. Correct Policy Maturity date should get set in CSD screen.
3. In case of partial premium deduction, reduced sum assured should get displayed in CSD screen.
4.Policy status should get displayed according to premium payment for previous month.
Too get Hospital cash plan created against the same MSISDN

Actual Result
1.User registered hospital cash plan with Family,m-sente monthly policy through 'Agent'
2.Log In core app
3.Select Policy & Administration>Tele Sale>Transactions>Create policy
4.Entered MSISDN information get displayed
5.Select Product 'UTL Hospital cash plan'
6. Selected Product type 'Individual','Monthly'
7. Clicked on 'Issue Policy' policy created.

Test data
Used MSISDN 725304689

Expected Result
policy should not created again when MSISDN registered and Active

Invalid value get set in each input box.

Actual Result:
1. Go to Policy & Administration>Tele Sale>Transactions>Change In Poliocy Plan
2. Selected valid MSISDN from list, all the data against MSISDN get auto populated in respective fie
3. For each input box, incorrect value get set as below:
1. MSISDN get displayed in Proposal No. input box.
2. Proposal No. get displayed in Policy No. input box.
3. Policy No. get displayed in Customer Name input box.
4. Customer Name get displayued in Set No. input box.
5. Set No. get displayed in Mode input box.
6. Mode get displayed in Gross Premium input box.
7. Gross Premium get displayed in Payment Method input box.
8. Payment Method get displayed in Cover input box.

Test Data: Used any valid MSISDN from list.

Expected Result: For each input box, correct value should get set.
Input box not get displayed when "Switched payment" method 'M-Sente Monthly' to 'Airtime', Indiv

Actual Result
1.User dialed USSD short code '*142*5#'
2.Main menu get displayed, Selected option '4 Client Services'>>Change how to pay>>Airtime, 27
3.Next prompt get displayed as below:-
"I understand that 27,500.00 UGX will automatically be deducted in small amounts each day from
Confirm purchase?
1.Yes
2.No

Test Data
Used Customer Sim card (713108800,713108822)

Expected Result
Input box should get displayed for switching Payment method 'M-Sente Monthly to 'Airtime'

Without confirmation "SMS/Mpin" Policy created through 'Agent' for "Hospital Cash plan", Family/Ind
captured in CSD Screen.

Actual Result
1.Dialed USSD short code '*142*5#'
2.Main menu get displayed >>Option '5. Agent'
3.Entered client number >> Entered Client's name
4.Next prompt get displayed "Policy No. 256725304687-FRA-L-20170207 Congratulations, client ha
press 1
5.Selected option 2.Buy for family >> 2.M-Sente, 15,800.00 UGX monthly
6.Next prompt get displayed "Do they understand they can pay premium from M-Sente account an
deducted at end of the month.
1.Yes
2.No
7.selected option 1.Yes
8. "Policy No. 256725304687-HCP-U-20170207 In a few moments, customer will be invited to respo

Test data
Used MSISDN 725304687 for Testing

Expected Result
Policy should be purchased after SMS confirmation.
Gross Premium' amount get displayed incorrect in CSD screen, If User "Switched payment method

Actual Result
1.User dialed USSD code '*142*5#'
2.Selected Option 4.Client services>>4.Change how to pay
3.Choose option 1. Airtime, 9,200.00 UGX monthly, Message get displayed as :- "I understand that
amounts each day from my airtime balance.~Confirm purchase?~1.Yes~2.No"
4.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
1)Login Coreapp>>Policy & Administration>>CSD
2)Entered MSISDN in CSD Screen

Test Data
Used MSISDN 713112807 in Simulator for testing

Expected Result
'Gorss premium Amount' should get changed to "9,200" instead of '5,300' on CSD Screen.

In 'Claimant' input box policy holder name get displayed, in case of child/spouse selected as a claim

Actual Result:
1. Go to claim initiation menu, Initiated a claim by selecting 'Claimant Type' as Child.
2. Go to Claim Assessor menu, searched for valid 'Claim Number' and clicked on 'Execute Query' ic
2. All the auto populated data get auto populate in respective input box.

"In claimant input box,Policy holder name get auto populated."

Test Data: Used claim number '201700016' for checks.

Expected result:
1. In claimant input box, Policy holder name should not get displayed in case of 'Child/Spouse' sele
Claimant input box should get displayed blank. And 'AddLife' button should get enable to add 'Child
added,the details should appear on click of Claimant glass button.
AddLife' button does not get disable,if policy holder is a claimant.

Actual Result:
1. Go to claim Initiation page and initiated a claim by selecting claimant type as 'Self'.
2. Go to Claim Assessor menu, searched for valid 'Claim Number' and clicked on 'Execute Query' ic
2. All the auto populated data get auto populate in respective input box.
4. "In claimant input box,Policy holder name get auto populated."
5. "In 'Claimant Date of Birth' input box,Policy holder date of birth get auto populated."

'AddLife' button get displayed as enable,if policy holder is a claimant.

Test Data: Any valid claim number

Expected Result:
1. In case of 'Self' selected as a claimant type in claim initiation page. Then in claim assessor page
input box.And 'AddLife' button should get disable.
2. Correct date of birth should get displayed.

Note: In case of 'Self' Claimant type if 'AddLife' button get displayed enabled then it can affect our

On click of 'Back' button, Transaction get saved.

Actual Result:
1. Go to Claim Assessor menu, Selected valid claim number for family policy where claimant type a
2. Clicked on 'AddLife' button, one additional pop up page get opened.
3. Selected/Entered all valid data in all fields and clicked on 'Back' button.
4. Successful Pop up message get displayed as below:

"Transaction Successfully Saved"

Test Data: Used claim number "201700016" for checks.

Expected Result:
1. On click of 'Back' button, page should navigated to respective back page and no any data should
2. 'Save' button should get add on the page and after click on 'save' button,Transaction should get
Claimant date of birth does not get displayed correctly.

Actual Result:
1. Go to Claim Assessor menu, Selected valid claim number for family policy where claimant type a
populated data get auto populated in respective input box.
2. Clicked on 'Claimant' glass button,claimant list get displayed.
3. Selected claimant from list.
4. Claimant name and claimant date of birth get auto populated in respective input box.

"Claimant date of birth get displayed incorrect in respective input box."


"It seems that policy holder date of birth get displaying in place of claimant date of birth."

Test Data: Used claim number "201700016" for checks.

Expected Result: Claimant date of birth should get displayed correct.

On click of 'Verified ID' glass button, 'Birth Certificate' does not get displayed in the list.

Actual Result:
1. Go to claim Initiation Page and initiated a claim for family policy where claimant type is child.
2. Go to claim Assessor page>General Tab - Selected/Entered all valid data.
3. Clicked on 'Claimant' glass button and selected child from list.
4. Go to 'Claim Verified' tab and clicked on code glass button.

'Birth Certificate' does not get displayed in the list.

Test data: Used claim number "201700016" for checks.

Expected Result: 'Birth Certificate' should get displayed in the list, if the claimant is child.

For each single premium deduction, 2 times premium payments get displayed in CSD screen,where

Actual Result:
1. Created a policy via CoreApp interface with valid MSISDN "713106768"
2. Go to 'Premium Deduction Form' menu, and paid 3 payments successfully via CoreApp.
3. Go to CSD menu and searched for above explained MSISDN that is "713106768"
4. Go to Details hyperlink>Payment Tab - Verified premium paid deatils:

"For each single premium deduction, 2 times premium payments get displayed."

Test Data: Used MSISDN "713106768" for checks.

Expected Result:
1. For each single premium deduction, only one premium payment should get displayed.
"Cover" get displayed incorrect in CSD Screen, if user switched payment method "Individual,M-Sen

Actual Result
1.User dialed USSD code '*142*5#'
2.Selected Option 4.Client services>>4.Change how to pay
3.Choose option 1. Airtime, 9,200.00 UGX monthly, Message get displayed as :- "I understand that
amounts each day from my airtime balance.~Confirm purchase?~1.Yes~2.No"
4.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
1)Login Coreapp>>Policy & Administration>>CSD
2)Entered MSISDN in CSD Screen
5.User has Individual cover which get changed to family after change in payment method

Test data
Used MSISDN '713112812' in simulator for testing.

Expected Result
Cover should not be changed 'Individual to Family' on CSD Screen.

"Gross Premium" amount get displayed incorrect in CSD screen, If User "Switched payment method

Actual Result
1.User dialed USSD code '*142*5#'
2.Selected Option 4.Client services>>4.Change how to pay
3.Choose option 1. Airtime, 27,500.00 UGX monthly, Message get displayed as :- "I understand tha
amounts each day from my airtime balance.~Confirm purchase?~1.Yes~2.No"
4.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
1)Login Coreapp>>Policy & Administration>>CSD
2)Entered MSISDN in CSD Screen

Test Data
Used MSISDN 713112813 in Simulator for testing.

Expected Result
'Gross premium Amount' should get changed to " 27,500" instead of '15,800' on CSD Screen.
"Grosss Premium amount & Cover" get displayed incorrect in CSD screen, If User "Switched Individ

Actual Result
1.User dialed USSD code '*142*5#'
2.Selected Option 4.Client services>>4.Change how to pay
3.Choose option 1.1. Airtime, 9,200.00 UGX monthly, Message get displayed as :- "I understand tha
amounts each day from my airtime balance.~Confirm purchase?~1.Yes~2.No
4.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
1)Login Coreapp>>Policy & Administration>>CSD
2)Entered MSISDN in CSD Screen
5.User has Individual cover which get changed to family after change in payment method.
Test Data
Used MSISDN [713112816] in simulator for testing.

Expected result
'Gross premium Amount' should get changed to "9,200" instead of '58,300' & Cover should "Indivi

"Gross Premium" amount get displayed incorrect in CSD screen, If User "Switched payment method

Actual Result
1.User dialed USSD code '*142*5#'
2.Selected Option 4.Client services>>4.Change how to pay
3.Choose option 1. 1. Airtime, 27,500.00 UGX monthly, Message get displayed as :- "I understand t
small amounts each day from my airtime balance.~Confirm purchase?~1.Yes~2.No"
4.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
1)Login Coreapp>>Policy & Administration>>CSD
2)Entered MSISDN in CSD Screen

Test Data
Used MSISDN 713112815 in Simulator for testing

Expected Result
'Gross premium Amount' should get changed to "27,500" instead of '173,800' on CSD Screen.
"SMS" content get displayed incorrect in SMS Log Report, User switched payment method 'Individu

Actual Result
1. User registered Hospital Cash Plan with MSISDN (713112812)
2. Entered MSISDN & Entered *123#
3. Select Opton "4.Client Services>>4.Change How To Pay>>1. Airtime, 9,200.00 UGX monthly
4. "I understand that 9,200.00 UGX will automatically be deducted in small amounts each day from
5.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
6.Login Coreapp>>Policy & Administration>>Tele sale>>Reports>>SMS Log
Message get displayed as below:-
"Monthly premium of 5300 will be deducted in small daily amounts from your airtime balance over
topped up."

Test Data
Used MSISDN 713112812 for testing

Expected Result
Message should get displayed in SMS Log Report as - "Your monthly premium of 9,200 will be dedu
first airtime deductions will occur after [DATE]."
"SMS" content get displayed incorrect in SMS Log Report , User switched payment method 'Family

Actual Result
1. User registered Hospital Cash Plan with MSISDN (713112813)
2. Entered MSISDN & Entered *123#
3. Select Opton "4.Client Services>>4.Change How To Pay>>1. Airtime, 27,500.00 UGX monthly, M
UGX will automatically be deducted in small amounts each day from my airtime balance.~Confirm
4.Selected Option 1.Yes, message get displayed as below - "You have successfully switched to airtim
www.utl.co.ug"
1)Login Coreapp>>Policy & Administration>>Tele sale>>Reports>>SMS Log
Message get displayed as below:-
Message get displayed as below:-
"Monthly premium of 15800 will be deducted in small daily amounts from your airtime balance ove
topped up."

Test Data
Used MSISDN 713112813 for testing

Expected Result
Message should get displayed in SMS Log Report as "Your monthly premium of 27,500 will be dedu
first airtime deductions will occur after [DATE].

"Status Date" displayed incorrect on CSD screen, If User switched payment method, "M-Sente mon

Actual Result
1.User registered with family,M-sente monthly
2.Selected Option 4.Client Services>>4Change how to pay>>1. Airtime, 27,500.00 UGX monthly
3.Message get displayed as "I understand that 27,500.00 UGX will automatically be deducted in sm
balance.~Confirm purchase?~1.Yes~2.No"
4.Selected option 1.Yes, now message get displayed as below
"You have successfully switched to airtime payments. For full details, call 100 or visit www.utl.co.ug
5.Log in Core app>>Policy & Administration>>CSD

Test Data
Used MSISDN (725304665) in simulator for testing

Expected Result
'Status Date' should be changed if User switched Payment method 'M-Sente monthly to Airtime'
Policy does not get created for Broken Bone as well as Hospital Cash via CoreApp interface.

Actual Result:
1. User go to 'Create Policy' menu and entered/selected all valid data.
2. Selected Product as: "UTL Hospital Cash Plan / UTL Broken Bone.
3. Selected all other valid data for respective product and clicked on 'Issue Policy' button.
4. Policy does not get created and error occured for both product as below:

For UTL Broken Bone: "Error Error"


For UTL Hospital Cash Plan: " ORA-00001: unique constraint (PAS.PK_PHOLDER) violated ORA-020
line 45 ORA-01403: no data found"

Test Data: Used MSISDN "713106778" for policy creation.

Expected Result:
1. Policy should get created for both product.
Evidence/Scre
enshot/refere Severity Status Logged by AL owner Date Logged
nce
Shammi Core App 4-Dec-16

Refer Evidence
12 & 13 for
details /
P2
Screenshots-
Evidences 2-
Dec.doc

AL to resolve
Shammi Core App 4-Dec-16

Refer Evidence
14 & 15 for
details /
P2
Screenshots-
Evidences 2-
Dec.doc

AL to resolve
Shammi Core App 4-Dec-16

Refer Evidence
16 & 17 for
details /
P2
Screenshots-
Evidences 2-
Dec.doc

AL to resolve
Vipin Core App - 6-Dec-16
USSD

IssueNo17.docx P1

AL to resolve
Swati Core app 7-Dec-16

NA P2

AL to resolve
Shammi Inclusivity 17-Dec-16

Refer Evidence
12 & 13 for
details/
P2
Screenshots-
Evidences 17-
Dec.doc

AL to resolve
Shammi Inclusivity 18-Dec-16

Refer Evidence
3 for details/
Screenshots-
P2
Evidences 18-
Dec.doc

AL to resolve
Swati Core App 6-Dec-16

Refer Evidence
14 for details /
Screenshots- P2
Evidences 6-
Dec.doc

AL to resolve
Shammi Inclusivity 24-Dec-16

NA P2

AL to resolve
Swati Core App 29-Dec-16

NA P1

AL to resolve
Swati Core App 29-Dec-16

NA P1

AL to resolve
Shammi Core App 30-Dec-16

NA P2

AL to resolve
Shammi Inclusivity 4-Jan-16

Refer Evidence
2 for details/
Screenshots- P2
Evidences 4-
Jan.doc

AL to resolve
Shammi Core app 6-Jan-16

Refer Evidence
1 & 2 for
details/
P2
Screenshots-
Evidences 6-
Jan.doc

AL to resolve
Shammi Inclusivity 7-Jan-16

Refer Evidence
5 & 6 for
details/
P2
Screenshots-
Evidences 7-
Jan.doc

AL to resolve
Swati Agent 18-01-2017
Upsell

NA P2

AL to resolve
Shammi Core App 23-Jan-16

NA P1

Al to resolve
Shammi Core App 24-Jan-16

NA P1

AL to resolve
Shammi Inclusivity 24-Jan-16

NA P2

AL to resolve
Shammi Core App 24-Jan-16

NA P2

Al to resolve
Shammi Inclusivity 25-Jan-16

NA P2

AL to resolve
Swati USSD 28-Jan
Menu

Refer Evidence
1 for
details/Screensh P2
ots- Evidences
28-Jan.doc

Al to resolve
Swati USSD 28-Jan
Menu

Refer Evidence
2 for
details/Screensh P2
ots- Evidences
28-Jan.doc

Al to resolve
Swati USSD 28-Jan
Menu

Refer Evidence
3 for
details/Screensh P2
ots- Evidences
28-Jan.doc

Al to resolve
Swati USSD 28-Jan
Menu

Refer Evidence
4 for
details/Screensh P2
ots- Evidences
28-Jan.doc

Al to resolve
Shammi Core app 1-Feb-16

Refer Evidence
2 for details/
Screenshots- P2
Evidences 1-
Feb.doc

AL to resolve
Shammi Core app 1-Feb-16

Refer Evidence
3, 4, 5, 6, 7, 8 &
9 for details/
Screenshots-
Evidences 1-
P1
Feb.doc

&
End-to-end test
- Jan MM.csv

AL to resolve
Shammi Core app 1-Feb-16

Refer Evidence
10, 11 & 12 for
details/
Screenshots-
Evidences 1-
P2
Feb.doc

&
CUG Customer
Jan.csv

AL to resolve
Shammi Core app 3-Feb-16

Refer Evidence
10 & 11 for
details/
Screenshots-
loyality file
upload process
P1
issue(Airtime).d
oc

&
End-to-end test
- Jan airtime.csv

AL to resolve
Shammi Core app 3-Feb-16

Refer Evidence
1, 2, 3, 4 & 5 for
details/
P1
Screenshots-
Evidences 3-
Feb.doc

AL to resolve
Shammi Core app 6-Feb-17

Refer Evidence
1 for details/
Screenshots- P1
Evidences 6-
Feb.doc

AL to resolve
Swati Core app 8-Feb-17

Refer Evidence
1 for details /
ScreenShots- P2
Evidences 8-
Feb.doc

AL to resolve
Shammi Core App 9-Feb-17

Refer Evidence
3 for details/
Screenshots- P2
Evidences 9-
Feb.doc

AL to resolve
Swati USSD 11-Feb-17

Refer Evidence
1 for details/
Screenshots- P2
Evidences 11-
Feb.doc

AL to resolve
Swati USSD 11-Feb-17

NA P2

AL to resolve
Swati USSD 11-Feb-17

Refer Evidence
1 for details/
Screenshots- P2
Evidences 11-
Feb-2017 .doc

AL to resolve
Shammi Core App 13-Feb-17

Refer Evidence
3 for details/
Screenshots- P2
Evidences 13-
Feb.doc

AL to resolve
Shammi Core App 13-Feb-17

Refer Evidence
3 for details/
Screenshots- P2
Evidences 13-
Feb.doc

AL to resolve
Shammi Core App 13-Feb-17

Refer Evidence
8 for details/
Screenshots- P2
Evidences 13-
Feb.doc

AL to resolve
Shammi Core App 13-Feb-17

Refer Evidence
9 for details/
Screenshots- P2
Evidences 13-
Feb.doc

AL to resolve
Shammi Core App 13-Feb-17

Refer Evidence
10 for details/
Screenshots- P2
Evidences 13-
Feb.doc

AL to resolve
Shammi Core App 14-Feb-17

Refer Evidence
1 for details/
Screenshots- P2
Evidences 14-
Feb.doc

AL to resolve
Swati USSD 13-Feb-17

Refer Evidence
1 for details/
Screenshots- P2
Evidences 13-
Feb-2017 .doc

AL to resolve
Swati USSD 13-Feb-17

Refer Evidence
2 for details/
Screenshots- P2
Evidences 13-
Feb-2017 .doc

AL to resolve
Swati USSD 13-Feb-17

Refer Evidence
3 & 4 for
details/
P2
Screenshots-
Evidences 13-
Feb-2017 .doc

AL to resolve
Swati Core App 13-Feb-17

Refer Evidence
5 for details/
Screenshots- P2
Evidences 13-
Feb-2017 .doc

AL to resolve
Swati Core App 13-Feb-17

NA P2

AL to resolve
Swati Core App 13-Feb-17

NA P2

AL to resolve
Swati Core App 13-Feb-17

Refer Evidence
6 for details/
Screenshots- P2
Evidences 13-
Feb-2017 .doc

AL to resolve
Shammi Core App 17-Feb-17

Refer Evidence
1,2,3 & 4 for
details/
P1
Screenshots-
Evidences 17-
Feb.doc

AL to resolve
Resolve Retest
Date failed?
Yes
Yes
Yes
Yes
Yes

Yes
Yes

Yes
Yes
Yes
Yes
Comment/Status

[AL Response: 16 Jan] Flow of each option available in Campain required complete document. Initi
option developed, rest of the options can be develop in Post Implementatin phase with reports. The
options.
[Nigel: 16 Jan] I regard this as a P2 priority to be resolved before launch.
[Nigel: 20 Jan] Flow after selected appropriate status should be as follows:
Call back: our preference is to remove the lead from the list after clicking Save button and add
Date is reached. Follow Up Date should be compulsory. We can discuss alternatives if this flow is co
Invalid number: remove from leads list after clicking Save button.
No answer: leave on leads list after clicking Save button.
No call made: indicates customer has not yet been called. So leave on leads list.
Offer accepted: remove from leads list and take user to Create Policy screen after clicking on Pr
Offer declined: remove from leads list after clicking Save button.

Proceed arrow should only be active for Call Status = Offer Accepted.
Follow Up Date field compulsory for Call Status = Call Back. If Follow Up Date field is not completed
user should receive the following error message: Please provide a valid follow up date for {MSISD
Block Follow Up Date field if Call Status = Invalid number, No call made, Offer accepted, Offer decl

[AL Response 30 Jan] To be dealt with after existing errors have been resolved. As the proper flows
now.

[Nigel: 31 Jan] Changed back to AL to resolve. No further information is required from Inclusivity as
P2's must be completed before working on lower priority errors.
[Nigel: 20 Jan] Flow after selected appropriate status should be as follows:
Call back: our preference is to remove the lead from the list after clicking Save button and add
Date is reached. Follow Up Date should be compulsory. We can discuss alternatives if this flow is co
Invalid number: remove from leads list after clicking Save button.
No answer: leave on leads list after clicking Save button.
No call made: indicates customer has not yet been called. So leave on leads list.
Offer accepted: remove from leads list and take user to Create Policy screen after clicking on Pr
Offer declined: remove from leads list after clicking Save button.

Proceed arrow should only be active for Call Status = Offer Accepted.
Follow Up Date field compulsory for Call Status = Call Back. If Follow Up Date field is not completed
user should receive the following error message: Please provide a valid follow up date for {MSISD
Block Follow Up Date field if Call Status = Invalid number, No call made, Offer accepted, Offer decl

[AL Response 30 Jan] To be dealt with after existing errors have been resolved. As the proper flows
now.

[Nigel: 31 Jan] Changed back to AL to resolve. No further information is required from Inclusivity as
P2's must be completed before working on lower priority errors.

[Nigel: 20 Jan] Flow after selected appropriate status should be as follows:


Call back: our preference is to remove the lead from the list after clicking Save button and add
Date is reached. Follow Up Date should be compulsory. We can discuss alternatives if this flow is co
Invalid number: remove from leads list after clicking Save button.
No answer: leave on leads list after clicking Save button.
No call made: indicates customer has not yet been called. So leave on leads list.
Offer accepted: remove from leads list and take user to Create Policy screen after clicking on Pr
Offer declined: remove from leads list after clicking Save button.

Proceed arrow should only be active for Call Status = Offer Accepted.
Follow Up Date field compulsory for Call Status = Call Back. If Follow Up Date field is not completed
user should receive the following error message: Please provide a valid follow up date for {MSISD
Block Follow Up Date field if Call Status = Invalid number, No call made, Offer accepted, Offer decl

[AL Response 30 Jan] To be dealt with after existing errors have been resolved. As the proper flows
now.

[Nigel: 31 Jan] Changed back to AL to resolve. No further information is required from Inclusivity as
P2's must be completed before working on lower priority errors.
Please refer email with subject "RE: [Uganda-Mobile Money Integrations] - Micro Insurance" dated2
decided that PIN shall not be required from user and Msente be handling PIN verification.
[Nigel: 21 Dec] As per the above-mentioned email trail, the M-Sente vendor was due to complete t
5 Oct 2016. We are following up with them to establish whether the work was complete and obtain
documentation.
[Teksolto: 17 Feb] I changed the status of this isuue from Resolved to AL to resolve because issue is

[AL Response: 14 Jan] Main Menu:


Agent doesn't contain main menu in the flow and
it is not appropriate requirement because if agent select any option from main menu by mistake so
policy would going to be issue on Agent number
therefore this isn't appropriate change. If change is required then first inclusivity needs to change t

Language Option:
If user agent is accessing first time with his/her number they will have language option.After they s
set as default so whenever they dial from agent they won't get language option

It's not an appropriate requirement


[Nigel: 20 Jan] Agents can buy insurance for themselves. So they need access to the main menu. A
same as for non-agents except that they have the additional Agent option. Marked as AL to resolve

[AL Response 27 Jan] 1.Agent can access whole menu now.


2.Select option 5 for Agent menu.
3.Issue resolved

1. Dialed USSD Short code *142*5#


2.Next prompt get displayed Main Menu
"Please select the required option
1.Free Insurance
2.Buy insurance
3.Check status
4.Client Services
5. Agent "
[Retest : 31-jan Agent sim card 713112698]

[AL Response 8 Feb]When an agent can access all 5 tabs including Agent on above sim card, so iss
us. Please describe us more briefly what sort of addition do you reqiure more?
Furthermore, If user agent is accessing first time with his/her number they will have language optio
language will set as default so whenever they dial from agent they won't get language option
[Nigel: 21 Dec] Set Create Date = Issue Date. Is it possible to differentiate between USSD self-regis
registrations? If it is possible, setUser ID = USSD - Subscriber for self-registrations and USSD - Age

[AL Response: 14 Jan] TheUser ID for the policies issued via USSD is not possible in test as they ar
simulator.
[Nigel: 23 Jan]Will User ID and Create Day be set in production environment? And what will they be
and for agent registrations?

[Nigel: 21 Dec] Follow the same process as for Broken Bones claims. Click on Decision button for th
CREATE RESERVE. Click on Decision button for the 2nd time after creating reserve: 3 options availa
GRATIA). Please use the same wording as for Broken Bones claims.

[AL Response 24 Jan] The issue has been resolved


[Teksolto: 31 Jan] Issue retested and observations are below:
1.After click on Decision button for the 1st time: Code glass button appeared,then after clicked on
get displayed with list of 4 code description which is below: Refer Evidence 1 for details/ Screensho
DECLINED
POSTPONED
CREATE RESERVE
REPUDIATE I/C OUTRIGHT

Expected result: For the 1st time,if user clicked on code glass button,only one option should get dis
Reserve"

2. After click on Decision button for the 2nd time: Code glass button appeared,then after clicked on
get displayed with list of 2 code description which is below: Refer Evidence 2 for details/ Screensho
APPROVED - STANDARD
REJECTCLAIM AND APPLYEX-GRATIA

Expected result: For the 2nd time,if user clicked on code glass button,3 options should get displaye
ACCEPT
DECLINE
EX-GRATIA
[AL Response: 14 Jan] Issue has been resolved. Please Retest.

[Teksolto:28-Jan]
Once policy created for Hospital cash plan, Airtime & purchased policy captured on CSD screen, the
defect.
dependent on [Error 189,190]
1.Again retested through Agent option for 'Hospital Cash plan', "Airtime monthly payment method
prompt get displayed as "9,200.00 UGX will be deducted in small amounts from airtime balance ea
moments, customer will be invited to respond to an SMS to confirm purchase." again entered the m
option 2.Buy insurance, it displayed the prompt ""U-Insured Hospital Cash pays 100,000 per night i
more nights in a row. To buy choose option."
1.Buy for individual
2.Buy for family
2.Not displayed the message based on user registered.
[Used MSISDN for testing "725304701"]
1.But policy purchased "Hospital cash plan, Airtme payment, Individual Cover", through Simulator &
4. Status get displayed on the basis of User registration :
"Client has already purchased insurance. Individual Hospital Cash active until 09-Mar-2017.
Premium
Airtime 9200.00 UGX monthly".
[Used MSISDN for Testing 725304702]
[Retest : 11-Feb]
Correct wording and format:
"Your name: Jeremy
Press 1 to change your details. For changes to family policy, dial [call centre]."
Note:
1. Name should be in format: First Name Middle Name Surname (e.g. Nigel Wade Bowman. If no Mi
Bowman).
2. Press 1 should start on a new line. If not possible then format can be "Your name: Nigel Bowman
details. For changes to family policy, dial [call centre]." I.e. include a full stop after name and befor

[AL Response 27 Jan]


1.Issue Resolved.
2.Correct wording is displayed.
3.'Press 1' starts from new line.

User yet registered, Dialed USSD Short code '*142*5#'


1.Selected Option 4.Client Services
2.Selected Option 3.Add/change policy details
Next prompt get displayed as, "Your name UNKNOWN
Press 1 to change your details. For changes to family policy, dial @call centre@."
[Retest : 31-jan customer sim card 713108822]

[AL Response : 08-Feb]


Issue Resolved.
User not yet registered, Dialed USSD short code *142*5#
1.Select option 4.Client Services
2.Select option 3.Add/change policy details
Next prompt get displayed as, "Your name: UNKNOWN
Press 1 to change your details. For changes to family policy, dial[100]."

Note : UNKNOWN term is displayed for those numbers, which are not yet registered.

[Teksolto:9 Feb] If any user is not registerd for hospital cash as well as broken bone policy, Why pro
[AL Response 24 Jan] For Method Payment as Airtime Policy will be generated after SMS confirmatio
policy and customer's confirmation is required for Airtime auto-deductions. For method of payment
generated right away as other processes, and PIN verification request is generated.
[Nigel: 24 Jan] I would prefer consistent treatment of policies with airtime and M-Sente method of p
investigate and revert with a timeline for making the following change: create policy following requ
Payment Methods (airtime and M-Sente), but with inactive status. Change status to Active only onc
recieved (at least 1 daily payment for airtime).

[AL Response 25 Jan]It is new requirement/change in process which we have logged at our end. Tim
at the moment as we are engaged in error fixing.

[Nigel: 27 Jan]As an interim fix, I'm happy to have the policy record created after SMS or PIN confir
customer, provided the report mentioned by Ali in his email dated 27 Jan 2017 is available before l
in the system for those who have not confirmed purchase (via SMS / M-Sente PIN verification). Wou
need?". I have marked this error as "AL to resolve", as I'm waiting on confirmation that the suggest
for launch.
Further to my confirmation and additional question below, can you please confirm our understandin
has currently been set up to work? Please also confirm our understading of the current process is c
Before confirmation:
1. CoreApp persists customer policy details in core app, created by Agent via USSD, customer via U
2. Status get set to something like "Waiting for customer confirmation".
3. CoreApp needs to provide form/page where we could check details for created policy with appro
Following SMS or PIN confirmation:
- Such Policy status should get set to "Active In force" once customer confirm and policy details be
screen.
- Is there way we can test customer confirmation by SMS or PIN authorisation which CoreApp/UTL c
testing?

[Nigel: 31 Jan] Columns to be included in the report:


Currently Im using the following columns and just a date parameter (from and to range)
1. MSISDN
2. Name of Customer
[AL Response 24 Jan] Same as above but If they want Policy to be generated before Confirmation a
a new requirement and is needed to be discussed with PMO and CoreApp team
[Nigel: 24 Jan] I would prefer consistent treatment of policies with airtime and M-Sente method of p
investigate and revert with a timeline for making the following change: create policy following requ
Payment Methods (airtime and M-Sente), but with inactive status. Change status to Active only onc
recieved (at least 1 daily payment for airtime).

[AL Response 25 Jan] It is new requirement/change in process which we have logged at our end. Tim
at the moment as we are engaged in error fixing.

[Nigel: 27 Jan] As an interim fix, I'm happy to have the policy record created after SMS or PIN confir
customer, provided the report mentioned by Ali in his email dated 27 Jan 2017 is available before l
in the system for those who have not confirmed purchase (via SMS / M-Sente PIN verification). Wou
need?". I have marked this error as "AL to resolve", as I'm waiting on confirmation that the suggest
for launch. Please also confirm our understading of the current process is correct.
Before confirmation:
1. CoreApp persists customer policy details in core app, created by Agent via USSD, customer via U
2. Status get set to something like "Waiting for customer confirmation".
3. CoreApp needs to provide form/page where we could check details for created policy with appro
Following SMS or PIN confirmation:
- Such Policy status should get set to "Active In force" once customer confirm and policy details be
screen.
- Is there way we can test customer confirmation by SMS or PIN authorisation which CoreApp/UTL c
testing?

[Nigel: 31 Jan] Columns to be included in the report:


Currently Im using the following columns and just a date parameter (from and to range)
1. MSISDN
2. Name of Customer
3. Date of Registration
4. Status (Pin verified / SMS confirmed?)
Report would display data for both confirmed/unconfirmed policies. Required data can be easily filt
[Nigel: 24 Jan] USSD should evaluate to scenario (2b) in the USSD Menu spec: "Already registered,
coverage", because terminated cover is not active. So customer should move to following screen a
insurance":
"U-Insured Hospital Cash pays 100,000/night in hospital if you spend 3 or more nights in a row.
1. Read policy details
2. Buy for yourself
3. Buy for family"
I've marked this error as AL to resolve.

[AL Response 6 Feb] Issue Resolved


[Teksolto: 7 Feb] Issue retested and observations are below: Still Issue are pending
1. Created a policy through simulator with MSISDN"256713106636"
2. Go to Client Services>Terminate Policy - Terminated the policy.
3. Again dialed short code *123# by simulator and used MSISDN "256713106636" for buy policy, S
Prompt get displayed as:
"U-Insured Hospital Cash pays 100,000/night in hospital if you spend 3 or more nights in a row.
1. Read policy details
2. Buy for yourself
3. Buy for family"
4. purchased policy again, go to CSD screen and searched for 2nd time purchased policy: - Policy d
displayed in CSD screen.
5. Again dialed short code *123# by simulator and used MSISDN "256713106636" for buy policy, S
Prompt get displayed as: "Please select the required option:~1. ~2. ~3. ~4."

[AL Response 30 Jan] Resolved


[Teksolto: 30 Jan] Still issue are pending, Registerd for broken bone policy with MSISDN "256713106
menu and searched for MSISDN "256713106699", Policy number and proposal number does not ge
[Nigel: 24 Jan]
1. How "First Name, Middle Name & Last Name" will get displayed in respective input box. Answer:
should display as First Name. Text after last space should display as Last Name. Text between 1st a
display as Middle Name.
2. "First Name, Middle Name & Last Name" Input box should be editable or non editable?? Answer:
Customer data (including names) from UTL is poor and names will have to be updated / corrected i
3. Name which has 4 word or more than 4 word, how system will define - which is middle name???
1 above.
4. In case of name which has 4 or more than 4 word, How name will get displayed in "First Name, M
input box??? Answer: see my answer to 1 above.
Changed status to AL to resolve.

[AL Response 8 Feb] Issue Resolved. Now the names appear in their respective fields.
[Teksolto: 8 Feb]According to Nigel Guideline - Issue retested and observations are below:
1. Major issue has been resolved -Name get appeared in their respective fields.
2. Some issues are still pending -
#. "First Name, Middle Name & Last Name" Input box became non-editable.
#.In case of, Name which has 4 word or more than 4 word,User clicked on 'Middle Name' input b
from keyboard, spaces get removed between the middle name.
Expected result for above explained both issue:
#. "First Name, Middle Name & Last Name" Input box should be editable.
#. In case of, Name which has 4 word or more than 4 word,spaces should not get removed betw
user clicked on 'Middle Name' input box and entered any button from keyboard,

[AL Respponse 6 Feb] Issue Resolved. Please Retest.


1.Client Registered Through 'Agent', "Individual,M-Sente monthly"
2.Log In core app
3.Select Policy & Administration>Tele Sale>Reports>SMS Log>Entered MSISDN '725304690'
4.Message content get displayed as
SMS1: "Thank you for registering for U-Insured powered by Britam. For more information, call 100.
SMS2 :You have signed up for UTL Hospital Cash Insurance. Policy details to follow via SMS. For full
www.utl.co.ug
SMS3: You will be paid 100,000 UGX cash per night if you stay in hospital for 3 or more nights in a r
year.
SMS4: Hospitalisation for accidents covered immediately. Your full cover (overnight hospital stays f
hospital) will be active 30 days from now.

Expected Result
SMS should get displayed as - "Do they understand they can pay premium from M-Sente account a
If not paid, it will be auto-deducted at end of the month. 1.Yes 2.No"

[Retest: 8 Feb, Used Agent Sim card :713112698]


[AL Response 25 Jan] The issue has been resolved. Now the suspended policy is named as NTU. Fur
date of the NTU policy will remian fixed at Last Maturity Date. In case, the subscriber pays the prem
then the policy will be made active again.
[Nigel: 25 Jan] I'm happy with the explanation by AL provided:
1. Customer may not claim during waiting period (because no premium was recieved).
2. Policy is marked as NTU at end of waiting period. Seems this should be working.
3. The NTU period during which policy can be made active again is not longer than 1 month from d
(the intention of the product specs was that an NTU policy cannot be made active again, but the ru
above is actually fine).
4. Customer may not claim during the NTU period, unless policy is reactivated through a premium

[Teksolto: 30Jan]Issue retested and observations are below:


1. After renewal process status get set as: NTU as expected.
2. Not a single deductions completed From 30-JAN-17 to 28-FEB-17, But Sum Assured does not get
get displayed as "100000".
[Nigel: 27 Jan] The SMS should only be triggered after 20 successful deductions and not after each
deductions. Also note that the premium amount shown in the SMS should be 9,200and not 460 as
x 20). Marked as "AL to resolve".

[AL Response 6 Feb] An appropriate SMS is firing after 20 successful deductions. Please Retest

[Teksolto: 16 Feb]Issue retested And observations are below:


1. Paid premium does not get displayed in CSD Screen.(Used MSISDN 256713106777 for testing).
2. Once paid premium will display in CSD Screen then we can test this defect,because without paid
can not assume that how much payment get received.and after verification we can check for SMS
[Nigel: 27 Jan] SMS wording should be: "You have not yet paid the 1st premium to activate your U-I
Please ensure you have sufficient balance to pay xx before [DATE]." Marked as "AL to resolve".
[AL Response 6 Feb] Why should maturity date change when the policy is Suspended (NTU)?
As per the process scenarios, the user have 1 month period, after NTU, to pay the premium in orde
to Active status. The customer can pay at anytime within 1 month from the date policy is marked N
of the policy will be revised as from the date he paid the full premium. Therefore, the maturity date

[Teksolto: 6 Feb]Suspended status and NTU status,both are differnt.


If any policy is in waiting period and preium does not get paid for that policy till policy renewal date
get change from active to NTU.
If previous month premium paid for a policy and in the current month if premium does not get paid
date. then policy status should get change from active to suspended.
Above statement are based on our understanding, please correct if there is a need for some differe

[Nigel: 13 Feb]I confirm that NTU (not taken up) and Suspended are two different statuses. NTU oc
waiting period if no premium was received during the waiting period. A policy becomes suspended
renewal, no premium is received before the next renewal date. These 2 status are fully described in
and premium/cover scenarios that were provided. For examples, see scenarios 3, 4 and 5 for mobil
rows 22 and 23 in the Product Rules tab of the product specs.

The Maturity Date for Suspended policies does not need to move forward on the renewal run when
from Active to Suspended. But it is critical that a claim cannot be made if the claim event date occ
the Suspended state.

[AL Response 8 Feb] Now the ORA-00001 error does not appear and renewal process runs smoothly
[Teksolto: 8 Feb] Still issue is pending. Used Policy No. - "256713106745-HCP-U-20170208" for chec
renewed.
Comment
USSD menu restart notification received from UTL. Assessing timeline for completing QA.
Resolved and handed over for the UAT
A case of each Premium Mode was tested for the scenario of NTU status - renewal process
was sucessful.
Total 4 cases were tested for Monthly and Yearly premium modes. The renewals were
sucessful. Maturity dates were increased as required. Statuses of the policy changed
according to the scenarios. Each status (Active, NTU, Suspended, and Terminated) are
operating as per required process.
Total 4 cases were tested for Airtime premium modes. Policy renewal was sucessful in case
of Active policy. Pro-rata sum assured was also correctly calculated in case of partial
premium. However, in case of Suspended status the policy is not behaving correctly.
Development team is working on fixing the bugs.

A case of each Premium Mode was tested for the scenario of NTU status - renewal process
was sucessful.
Total 4 cases were tested for Monthly and Yearly premium modes. The renewals were
sucessful. Maturity dates were increased as required. Statuses of the policy changed
according to the scenarios. Each status (Active, NTU, Suspended, and Terminated) are
operating as per required process.
Total 4 cases were tested for Airtime premium modes. Policy renewal was sucessful in case
of Active policy. Pro-rata sum assured was also correctly calculated in case of partial
premium. However, in case of Suspended status the policy is not behaving correctly.
Development team is working on fixing the bugs.
A case of each Premium Mode was tested for the scenario of NTU status - renewal process
was sucessful.
Total 4 cases were tested for Monthly and Yearly premium modes. The renewals were
sucessful. Maturity dates were increased as required. Statuses of the policy changed
according to the scenarios. Each status (Active, NTU, Suspended, and Terminated) are
operating as per required process.
Total 4 cases were tested for Airtime premium modes. Policy renewal was sucessful in case
of Active policy. Pro-rata sum assured was also correctly calculated in case of partial
premium. However, in case of Suspended status the policy is not behaving correctly.
Development team is working on fixing the bugs.
Expected Date for
Process in Development completion of Process in QA
Development
Under QA
Picked for Development TBD
Picked for Development TBD
Handed over to QA
Team

Handed over to QA
Team
Handed over to QA
Team
Resolved and handed over for UAT
Expected Date for
Released for UAT
completion of QA
21-Feb-17
24-Feb-17

26-Feb-17
24-Feb-17
ASAP - Highest Priority 21-Feb-17

You might also like