Beruflich Dokumente
Kultur Dokumente
Process / screen
10
20
Change in Policy
23
Create Policy
41
Create Policy
73
96
Policy Enquiry
97
Policy Enquiry
98
Create Policy
183
Create Policy
184
Create Policy
192
CoreApp
193
Create Policy
197
Change in Policy
198
200
Change in Policy
201
202
204
Create Policy
205
Create Policy
206
Change in Policy
228
Create Policy
231
Policy Enquiry
232
Policy Enquiry
Detail of error
Lead upload form multiple error messages get displayed when form submitted
w/o entering any details
Actual result
Click on Lead Upload menu link, when form get opened w/o entering any details
Click Next button
Error messages get displayed 3 times for 'Choose Files' and 2 times for 'Batch
Description.
Test Data
do not entered/select anything in any input box/drop down and clicked on 'next'
button.
Expected Result
Error message should display once for each fields.
No changes are made on form and click on Save Changes button, error message
not displayed.
Actual result
1. Select Batch Description from dropdown box.
2. Page get displayed with records. Do not change in status and do not click on
'Proceed' arrow button; then click on 'Save changes' button.
3. Green box appeared on page with message content 'Done'
Error message not displayed as "No new changes to save/update"
Test Data
NA
Expected Result
Informative error message should get displayed such as "No new changes to
save/update"
Proceed button against records not behaving correctly. If status has not changed
to "Offer Accepted" then also re record Proceed button click navigate to 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 'Proceed' arrow button.
3.Error message not displayed as 'Please select applicable status to proceed
with Policy creation. Instead of error message displaying, page get navigated 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 with Policy creation.'
Change Call Status to 'Follow up' without providing Follow Up date and or
remarks for re lead displayed and click on Save changes button, No error
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 and or remarks for re lead and click on Save changes
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 and click on Save button, Error message should get 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 date value and click on save changes 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 "Follow up date is not applicable if call
status is Offer rejected for record of {lead Name}."
Without input of any data in any field, Clicked on 'Process', All mandatory fields
get not displayed with red highlights.
Actual Result
1. User goto 'Change in Policy Plan', Do not enter anything in any input box, &
Click on 'Process' button.
All mandatory fields not get displayed with red highlights. And the displayed pop
up box position is not appropriate.
For all input boxes, error message get displayed twice on page.
Test Data
do not enter anything in any input box.
Expected Result
pop up box position should be appropriate on page and mandatory fields should
display with red highlights. Single error message should be displayed for each
field.
Create Policy issues for 'Family' cover -if family type policy created re details for
spouse and cover type not get persisted
Steps:
Create Policy of Type Family - Hospital cash and provide all required details;
policy get created successfuly
Now search policy using CSD screen as below 1. User goto 'CSD' menu.
2. Entered valid number in 'MSISDN' input box, clicked on 'Search' icon.
3. All customers policies details get appeared in search result.
4. search result get displayed as Hyperlink to select, Clicked on displayed policy.
5. Get navigated on Main Policy Enquiry page with all the policies displayed
under a selected MSISDN account.
6. Clicked on 'Benificiary' tab, user get navigated for Beneficiary tab.
Policy holder spouse details get not displayed as a Beneficiary.
Actual Result:
Policy holder spouse detailis not displayed as beneficiary
Cover Type: Individual
Expected Result
Policy holder spouse details should get displayed as a Beneficiary.
The Cover type of the user should display as Family
If in uploaded file user has provided header but does not clicked on Check Box
to mark first row Column Names, Error message get not displayed as expected.
(TC - 4.5)
Actual result
1. User goto menu 'Lead upload', provide all data on form and unticked the
check box 'First Row has Column Names' then after clicked on next button.(In
Batch file, header Columns should be added.)
Error message get not displayed as "First row contains column header" &
there is no any opportunity for user to correct file upload data mapping page
when it get displayed.
Test Data
Used valid batch file with valid data.
Expected Result
Error message should get displayed as first row contains column header instead
of actual leads data OR if error message not get displayed then there is an
opportunity for user to correct file upload data Mapping Page when it get
displayed.
Value for 'User Id' and 'Create Date' column get displayed in CSD screen for
policy which is created via CoreApp but not displayed for policy which is Created
via USSD.
Actual Result
1. User go to CSD menu, searched for MSISDN '256713107708' which is created
via CoreApp and selected.
2. User get navigated to CSD screen with details for selected MSISDN, Value for
'User Id' and 'Create Date' column get displayed on screen.
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 created via USSD or CoreApp. It's hepls in auditing.
Already captured data does not get refreshed on Policy Enquiry Page after re
navigation on same page.
Actual Result
1. User clicked on CSD menu.
2. User get navigated on Main Policy Enquiry page capture few details/search for
policy
3. Navigate to other pages
4. Again open CSD page, all the data selected/captured earlier get displayed,
not get resetted to the initial stage with default values.
Expected Result
Data should get resetted to default values on policy enquiry page after the page
re navigation.
Hospital Cash Policy does not get created via CoreApp for MSISDN which is
already registered for 'Broken Bone' policy through CoreApp.
Actual Result
1. User goto 'Create Policy' menu, selected MSISDN which is already registered
for broken bone policy through CoreApp.
2. All the details get displayed on screen against MSISDN except 'Gender' which
is provided at the time of registration.
Gender does not get displayed on screen which is mandatory field and 'Gender'
dropdown box is non editable. It's creating issues while creating hospital cash
policy.
Test Data
Used MSISDN as '256713107708' for creating policy.
Expected Result
Core apps should allow policy creation.
Gender should get displayed on screen which is provided at the time of
registration.
Without choosing gender user can not create policy.
Hospital Cash Policy does not get created for MSISDN which is already registered
for 'Broken Bone'.
Actual Result
1. User goto 'Create Policy' menu, selected MSISDN which is already registered
for broken bone policy through CoreApp.
2. Selected all the details against MSISDN, selected product as 'Hospital Cash'
and clicked on 'Issue Policy' button.
Policy does not get created and error message get displayed on screen as:
"ORA-01422: exact fetch returns more than requested number of rows"
Test Data
Used MSISDN as '713106611' for creating policy.
Expected Result
Core apps should allow policy creation.
Broken bone policy does not get registered for MSISDN which is already
registered for 'Hospital Cash'
Actual Result
1. User goto 'Create Policy' menu, selected MSISDN which is already registered
for hospital cash policy through CoreApp.
2. Selected all the details against MSISDN, selected product as 'UTL Broken
Bone' and clicked on 'Register' button.
User does not get registered for free broken bone policy and error message get
displayed on screen as: "ORA-01422: exact fetch returns more than requested
number of rows"
Test Data
Used MSISDN as '713106613'
Expected Result
Core apps should allow registration and user should get registered for free broke
bone policy.
One Additional Title as 'Ms.' get displayed in 'Title' dropdown box for Subscriber
and Spouse both.
Actual Result
1. User go to 'Create Policy page, Clicked on 'Title' dropdown box for Subscriber,
Title 'Ms.' get displayed in dropdown value.
2. Selected Product as 'Hospital Cash Plan' and 'Product Type' as 'Family',
additional fields get displayed on screen.
3. Clicked on 'Title' dropdown box for Spouse, Title 'Ms.' get displayed in
dropdown value.
Expected Result
Title 'Ms.' should get removed from 'Title' dropdown for Subscriber and Spouse
both.
Note: [According to Nigel] Only Title "MR, MISS, Prof, DR, MRS, REV" should get
displayed in dropdown box.
After input of valid MSISDN in 'Enter MSISDN' input box for broken bone
customer, pop up error message get displayed.
Actual Result
1. User go to 'Change In Policy Plan' page and entered valid MSISDN against
broken bone customer.
pop up error message get displayed as: "Your search returned no results."
Test Data
Used MSISDN which is registered against broken bone policy.
Expected Result
Pop up should get appear with list of broken bone customer against MSISDN
number.
Proceed" &
Query:
1. What defines header 'MAIN' and what is the need of it??
Few mandatory fields does not get displayed with highlighted red mark.
Actual result
1. User go to 'Create Policy' page.
2. Do not entered/selected anything in any input box and clicked on 'Issue
Policy' button.
Below mandatory fields does not get displayed with highlighted red mark.
1. Product
2. Product Type
3. Pay method
Test Data
Do not entered/selected anything in any input box.
Expected Result
1. Product dropdown field should get displayed with highlighted red mark.
Because if user does not select 'Product' dropdown field, user can not select the
"Product Type, Premium Mode & Pay Method".
2. Product Type & Pay Method should get displayed with highlighted red mark
because if user does not select product type and pay method, user can not buy
policy.
3. Premium field should not get displayed with highlighted red mark because
'Premium' get auto populate after selection of "Product Type, Premium Mode &
Pay Method".
After menu option 'Change In Policy plan' selection, Input box get not displayed
in proper position for "Enter MSISDN" input box.
Actual Result
1. User go to menu 'Change in Policy Plan'
The position of 'Enter MSISDN' input box is not proper.It seems that 'Enter
MSISDN' input box slightly moved toward right direction as compare to another
input box.
Expected Result
The position of 'Enter MSISDN' input box should proper according to another
input box.
Too get Hospital cash plan created against the same MSISDN
Actual Result
1.User registered hospital cash plan with Individual,m-sente monthly policy
through 'Agent Upsell'
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 'Family','Monthly'
7. Clicked on 'Issue Policy' policy created.
Test data
Used MSISDN 725304640
Expected Result
policy should not created again when MSISDN registered and Active
Policy renewal is not working as expected for user,who has active Upsell
individual cover and Airtime Pay Method.
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/01/17 & 26/01/17 to mark 4 airtime deductions against
policy.
3. Set last processed date as "23-FEB-17" as Policy maturity date and renewed
the policy by menu 'SA Policy Renewal'
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 not get displayed, Sum Assured get displayed as "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.
Evidence/Scree
nshot/referenc
e
Refer Evidence1
for details /
ScreenshotsEvidences 2Dec.doc
Refer Evidence 2
& 3 for details /
ScreenshotsEvidences 2Dec.doc
Severity
P3
Status
Logged by AL owner
Date
Logged
Shammi
Core App
4-Dec-16
Shammi
Core App
4-Dec-16
Failed on
retest
P4
AL to
resolve
Refer Evidence 4
for details /
ScreenshotsEvidences 2Dec.doc
Refer Evidence
11 for details /
ScreenshotsEvidences 2Dec.doc
P3
Shammi
Core App
4-Dec-16
Shammi
Core App
4-Dec-16
Failed on
retest
P3
AL to
resolve
Shammi
Refer Evidence
12 & 13 for
details /
ScreenshotsEvidences 2Dec.doc
P2
AL to
resolve
Core App
4-Dec-16
Shammi
Refer Evidence
14 & 15 for
details /
ScreenshotsEvidences 2Dec.doc
P2
AL to
resolve
Core App
4-Dec-16
Refer Evidence
16 & 17 for
details /
ScreenshotsEvidences 2Dec.doc
Shammi
Core App
4-Dec-16
Shammi
Core app
5-Dec-16
P2
AL to
resolve
Refer Evidence 1
for details/
ScreenshotsEvidences 5Dec.doc
P3
AL to
resolve
Shammi
Refer Evidence
2,3,4 & 5 for
details/
ScreenshotsEvidences 6Dec.doc
P3
7-Dec-16
Failed on
retest
Nigel
P4
Core app
AL to
resolve
7-Dec-16
Shammi
P3
AL to
resolve
Core App
12-Dec-16
Refer Evidence
12 & 13 for
details/
ScreenshotsEvidences 17Dec.doc
Shammi
Inclusivity
17-Dec-16
Shammi
Core App
17-Dec-16
P2
AL to
resolve
NA
P3
AL to
resolve
Refer Evidence
14 & 15 for
details/
ScreenshotsEvidences 17Dec.doc
Refer Evidence 2
& 3, for details/
ScreenshotsEvidences 28Dec.doc
P3
Shammi
Core App
17-Dec-16
Shammi
Core App
28-Dec-16
Failed on
retest
P3
AL to
resolve
Refer Evidence 4
& 5, for details/
ScreenshotsEvidences 28Dec.doc
Shammi
Core App
28-Dec-16
Swati
Core App
29-Dec-16
P3
AL to
resolve
Refer Evidence 2
& 3 for details /
screen shot &
Evidence(Agent
Upsell & Core
app)
P2
AL to
resolve
NA
Shammi
Core App
29-Dec-16
Shammi
Core App
30-Dec-16
P3
AL to
resolve
NA
P2
AL to
resolve
Shammi
Refer Evidence 1,
for details/
ScreenshotsEvidences 30Dec.doc
P3
AL to
resolve
Core App
30-Dec-16
NA
Shammi
Core App
30-Dec-16
Shammi
Core App
31-Dec-16
P2
AL to
resolve
Refer Evidence 1
& 2 for details/
ScreenshotsEvidences 31Dec.doc
P3
AL to
resolve
Refer Evidence 5
for details/
ScreenshotsEvidences 31Dec.doc
Shammi
Core App
31-Dec-16
Shammi
Core app
31-Dec-16
P3
AL to
resolve
Refer Evidence 7
for details/
ScreenshotsEvidences 31Dec.doc
P3
AL to
resolve
Refer Evidence 8
& 9 for details/
ScreenshotsEvidences 31Dec.doc
Refer Evidence
10 for details/
ScreenshotsEvidences 31Dec.doc
P3
Shammi
Core app
31-Dec-16
Shammi
Core app
31-Dec-16
Failed on
retest
P3
AL to
resolve
NA
Swati
Shammi
Core App
P2
Al to resolve
NA
P2
Al to resolve
23-Jan-16
Shammi
NA
P1
Al to resolve
Core App
23-Jan-16
Resolve
Date
Retest
failed?
Yes
Comment/Status
[AL Response: 23 Dec] Now only one message appears for the
Error of Batch Description and one message appears for the
Error ofFile Upload.
[Teksolto: 23 Dec] Two message get appeared for the error of
Batch Description and two message get appeared for the Error
of File Upload.
(Refer Evidence1 for details / Screenshots-Evidences 24Dec.doc)
Yes
Yes
Yes
Yes
Proposed
solution