Académique Documents
Professionnel Documents
Culture Documents
screen
26
Claim
Menus
42
Claim
Menus
44
Claim
Initiation
54
Claim
Assessor
60
Claim
Initiation
61
Claim
Initiation
62
Claim
Initiation
63
Claim
Assessor
65
Claim
Accessor
71
Request
Approval
72
Request
Approval
91
Claim
Initiation
92
Claim
Initiation
93
Claim
Initiation
102
Request
Approval
225
Claim
Initiation
Detail of error
Verify menus after menu option 'Transactions' selection,Menu get not
displayed in proper position.
Actual Result
1. User Login himself & select 'Policy & Administration'.
2. User select 'Claim', then select 'Transactions'.
Main menu get appeared with below options
1. Claim Initiation
2. Claim Assessor
3. Claim Request
4. Request Approval
5. Claim/Settlement Inquiry
6. Claim Initiation Apex
The position of menu 'Claim Initiation Apex' is not proper.It seems that the
menu slightly moved toward right direction as compare to another menu.
Test Data
User login himself with valid credentials.
Expected Result
The position of 'Claim Initiation Apex' menu should proper according to
another menu.
Verify menus after menu option 'Transactions' selection, Menu get not
displayed in proper position.
Actual Result
1. User Login himself & select 'Policy & Administration'.
2. User select 'Claim', then select 'Transactions'.
Main menu get appeared with below options
1. Claim Initiation
2. Claim Assessor
3. Claim Request
4. Request Approval
5. Claim/Settlement Inquiry
6. Claim Initiation Apex
The position of menu 'Claim Initiation Apex' is not proper. It seems that the
menu slightly moved toward right direction as compare to another menu.
Test Data
User login himself with valid credentials.
Expected Result
The position of 'Claim Initiation Apex' menu should proper according to
another menu.
Without input of any date in 'Date of admission' & 'Date of Discharge' field,
clicked on 'Check eligibility', correct error message not get displayed.
Actual Result
1. User selected option 1 'Claim Initiation', User get navigated to claim
initiation page.
2. User selected valid MSISDN & valid Claimant type.
3. User do not entered any date in 'Date of admission' & 'Date of Discharge'
field and clicked on 'Check eligibility'.
Error message get appeared as "Not allow null Admit date."
Test Data
User selected valid MSISDN & valid Claimant type.
Expected Result
Error message should appears as "Date of Admission/Discharge is
mandatory."
Claim Initiation : Dates validation for 30 days not working, date difference
more than 30 days are allowed to input
Expected Error message not get displayed if number of nights more than 30, and on
click of eligibility button cover amount get calculated
Unsaved changes save confirmation popup does not get displayed if without
saving details click on menu link
Actual : Edit claim accessor form and do not save details instead directly
tries to open a other menu option such as Claim Request. Unsaved page
details confirmation popup does not get displayed
Expected : Popup should get appeared if any unsaved details on form,
After click on 'Req. Type' dropdown box, Value get not displayed as expected
by business.(TC - 4.1)
Actual Result
1. User clicked on 'Request Approval' menu, get navigated to request
approval page.
2. Clicked on Req. Type dropdown box, value get appeared as below:
Claim
Settlement
Policy Loan
Annuity
Expected Result
Only require "Claim" in the drop down box.
After input of invalid data in 'Code' input box, Error message get not
displayed as expected.(TC - 6.2)
Actual Result
1. User clicked on 'Request Approval' menu, get navigated to request
approval page.
2. Clicked on 'Decision' button, Pop up get appeared on screen.
3. Inputted invalid data in 'Code' input box and clicked on 'Decision Note'
area.
Error message get not displayed as: "Incorrect decision code. Please enter a
correct code."
Expected Result
error message should get displayed as: "Incorrect decision code. Please
enter a correct code."
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 Query' icon
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.
P3
AL to
resolve
Logged
by
AL owner Date
Logged
Shammi
Resolve
Date
Shammi
USSD
6-Dec-16
Shammi
P3
AL to
resolve
P4
Failed on
retest
P3
Shammi
Shammi
Failed on
retest
P3
AL to
resolve
Shammi
Shammi
Shammi
P4
AL to
resolve
P2
AL to
resolve
P2
AL to
resolve
Shammi
Shammi
Shammi
P3
AL to
resolve
P3
AL to
resolve
P3
AL to
resolve
P4
P2
Shammi
Shammi
Failed on
retest
Failed on
retest
Shammi
P4
Failed on
retest
Shammi
Inclusivity 18-Dec-16
Shammi
P2
AL to
resolve
P3
Failed on
retest
Retest Comment/Status
failed?
Proposed solution
Yes
Yes
No
Approach 1
1. Before session get timed
out core app can show
message in pop up modal
window as "Your session
getting timeout in minutes
xxx, please click on continue
button to use current
session. ".
2. In cases where use did
not click on continue button
before timeout, core app can
automatically navigate to
login page.
Approach 2
If core app don't want to
display popup window for
pre timeout, then on
click/selection of any
button/link core app need to
check if session has already
timed out if yes then they
can take user on login page
and ask to re login.
Yes
Yes
Yes
Yes