Anda di halaman 1dari 32

Error # Process /

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."

Client Portfolio 'check all' check box not working


Actual Result
1. User selected 'Claim Assessor' menu, User get navigated to claim
Assessor page.
2. Entered Claim Number and clicked on 'Execute Query' Icon, all the auto
populated data get displayed in 'General' Tab against claim number.
3. Selected 'Client Portfolio' tab, user get navigated to Client Portfolio tab.
3. unticked the 'Check All' check box.
Active check box does not get 'unticked'.
Test Data
Unticked the 'Check All' check box.
Expected Result
Active check box should get 'unticked'.

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

Execute Query icon not functioning properly.


Actual Result
If the form is blank then also execute query icon click pulled up cached
records and show it on form.
Expected Result
If the form is blank then execute query icon should not pulled up cached
records
Session timed out not handled - in case of session timeout click of icons does
not work and not get navigated to login page (TC-13.6)
Actual Result
open claim initiation form, enter all valid data and stay on page for 10
minute still session get timed out, then clicked on any icons, no action get
performed on page.
Expected Result
Instead of no action performing, page should get Navigated on login
page,incase of session timed out.

Claim Acessor : High risk check box is editable (TC-21.1)


Actual - Click on High Risk check box and its get selected
Expected - High risk check box should not get editable, and its should get
auto selected if high risk hospital selected from list

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 selection of displayed customer from list in case of Policy Terminated,


error message does not get displayed as expected.
Actual Result
1. User go to 'Claim Initiation' menu, selected displayed terminated policy
from list.
2. Selected/entered all valid data and clicked on 'Check Eligibility' button.
Pop up message get displayed on screen as 'Eligible'.
Test Data
Used policy number as '9142-HCP-U-20161021'.
Expected Result
Pop up error message should appears as "Not eligible. Policy has been
terminated."

After selection of displayed customer from list in case of Policy Terminated,


Claim Number get generated.
Actual Result
1. User go to 'Claim Initiation' menu, selected displayed terminated policy
from list.
2. Selected/entered all valid data and clicked on 'Check Eligibility' button,
pop up message get displayed on screen as 'Eligible'.
3. Clicked on 'Ok' button, total number of night spent in hospital get
populated in 'Number of Nights' field, then after clicked on 'Save' icon.
Pop up message get displayed as 'Transaction Successfully Saved' and claim
number get generated.
Test Data
Used policy number as '9142-HCP-U-20161021'.
Expected Result
Claim number should not get generate for terminated policy.

After selection of displayed customer from list in case of Policy Suspended,


Claim Number get generated.
Actual Result
1. User go to 'Claim Initiation' menu, selected displayed suspended policy
from list.
2. Selected/entered all valid data and clicked on 'Check Eligibility' button,
pop up message get displayed on screen as 'Eligible'.
3. Clicked on 'Ok' button, total number of night spent in hospital get
populated in 'Number of Nights' field, then after clicked on 'Save' icon.
Pop up message get displayed as 'Transaction Successfully Saved' and claim
number get generated.
Test Data
Used policy number as '9143-HCP-U-20161021'.
Expected Result
Claim number should not get generate for suspended policy, error message
should get displayed as "Not eligible. Cover has been suspended."

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.

No space available between "Policyno"


Actual Result
1. User go to menu 'Claim Initiation' and clicked on 'MSISDN' glass button.
2. Pop up get appeared with list of customer.
No space provided between label "Policyno"
Expected Result
Space should get provided between 'Policyno' and it shgould get displayed
as "Policy No."

Evidence/Screenshot/r Severity Status


eference

Refer Evidence 7 for


details/ ScreenshotsEvidences 6- Dec.doc

P3

AL to
resolve

Logged
by

AL owner Date
Logged

Shammi

Core app 7-Dec-16

Resolve
Date

Refer Evidence 7 for


details/ ScreenshotsEvidences 6- Dec.doc

Shammi

USSD

6-Dec-16

Shammi

Core app 7-Dec-16

P3

AL to
resolve

Refer Evidence 2 for


details/ ScreenshotsEvidences 7- Dec.doc

P4

Failed on
retest

Refer Evidence 14 & 15


for details/ ScreenshotsEvidences 9- Dec.doc

NA, Refer test data

P3

Shammi

Core app 9-Dec-16

Shammi

Core App 10-Dec-16

Failed on
retest

P3

AL to
resolve

NA, Refer test data

Shammi

Core App 10-Dec-16

Shammi

Core App 10-Dec-16

Shammi

Core App 10-Dec-16

P4

AL to
resolve

NA, Refer test data

P2

AL to
resolve

NA, Refer test data

P2
AL to
resolve

Shammi

Core App 10-Dec-16

Shammi

Core App 11-Dec-16

Shammi

Core App 11-Dec-16

P3

AL to
resolve

NA, Refer test data

P3

AL to
resolve

NA, Refer test data

P3

AL to
resolve

Refer Evidence 1 for


details/ ScreenshotsEvidences 17- Dec.doc

Refer Evidence 2, 3 & 4


for details/ ScreenshotsEvidences 17- Dec.doc

P4

P2

Shammi

Core App 17-Dec-16

Shammi

Core App 17-Dec-16

Failed on
retest

Failed on
retest

Shammi

Refer Evidence 5, 6 & 7


for details/ ScreenshotsEvidences 17- Dec.doc

P4

Failed on
retest

Core App 17-Dec-16

Refer Evidence 3 for


details/ ScreenshotsEvidences 18- Dec.doc

Shammi

Inclusivity 18-Dec-16

Shammi

Core app 7-Jan-16

P2

AL to
resolve

Refer Evidence 1 for


details/ ScreenshotsEvidences 7-Jan.doc

P3

Failed on
retest

Retest Comment/Status
failed?

Proposed solution

Yes

[AL Response - 18 Jan]Issue resolved.


[Teksolto: 19 Jan] Issue retested and below
observation get displayed:1.Error message get appeared as "Date of
Admission/Discharge is mandatory"
2. Full stop (.) is missing after word 'mandatory'.
(Refer Evidence 1 for details/ ScreenshotsEvidences 19- Jan.doc
[Teksolto: 23 Jan] Changed defect priority from
P3 to P4. Earlier defects status set was P3.

Yes

[AL Response - 18 Jan] Issue resolved. Now,


check box is marked by default.
[Teksolto: 19 Jan] Issue retested and
Observations are below:1.Check all check box is unused, now on click of
it, nothing will happen. Please feedback.

No

[AL Response - 17Jan] - This issue has been


resolved. Now the Claim initiation does not allow
more than 30 nights and message also
displayed if the number of nights greater than
30.
[Teksolto: 17 Jan] Issue retested and Issue has
been resolved,but we have some query as
below:1. If any patient admitted for more than 30 days
what is criteria to input dates??
[Nigel: 23 Jan] My preference is to allow the user
to capture the actual Discharge Date, even if it
is more than 30 days after the Admission Date.
That way we will have correct data for length of
stay. But then apply the 30-day maximum stay
limit when calculating the number of nights for
the claim amount. This is an unlikely scenario.
So I have changed priority to P3.

This is default Oracle forms behavior.Why


marked as P2 ?
[Nigel: 23 Jan] This is a minor problem and users
should use MSISDN to bring up customer details.
I've marked as a P4 priority.

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

[AL Response - 17 Jan] Issue Resolved. Now the


pop up message appears after user clicks Check
Eligibility button.
[Teksolto: 18 Jan] Issue retested and
Observations are below:1.Pop up error message get displayed as "Not
eligible. Policy has been Terminated."
As expected, 'T' should small in word
'Terminated'.(Refer Evidence 4 for details/
Screenshots-Evidences 18- Jan.doc)
[AL Response - 19 Jan] Issue Resolved
[Teksolto: 19 Jan] Still issue are pending.
[Teksolto: 23 Jan] Changed defect priority from
P2 to P4.

Yes

[AL Response - 17 Jan] Issue Resolved.


[Teksolto: 18 Jan] Issue retested and
Observations are below:1. Pop up error message get displayed as "Not
eligible. Policy has been Terminated."
2. Clicked on 'Ok' button which is available in
pop up message, Number of nights spent in
hospital get displayed in respective input box.
3. Clicked on 'Save' icon, again pop up error
message get displayed as "Not eligible. Policy
has been Terminated."
4. Again Clicked on 'Ok' button which is
available in pop up message, Invalid claim
number get generated on screen as
"201700001".(Refer Evidence 5 for details/
Screenshots-Evidences 18- Jan.doc)
[AL Response - 19 Jan] Issue Resolved
[Teksolto: 19 Jan] Still issue are pending.
[AL Response - 24 Jan] Issue resolved. Now the
claim number is not generated on the
terminated policy

Yes

[AL Response - 17 Jan] Issue Resolved.


[Teksolto: 18 Jan] Issue retested and
Observations are below:1. Pop up error message get displayed as "Not
eligible. Cover has been Suspended." As
expected, 'S' should small in word 'Suspended'.
(Refer Evidence 6 for details/ ScreenshotsEvidences 18- Jan.doc)
2. Clicked on 'Ok' button which is available in
pop up message, Number of nights spent in
hospital get displayed in respective input box.
3. Clicked on 'Save' icon, again pop up error
message get displayed as "Not eligible. Cover
has been Suspended."
4. Again Clicked on 'Ok' button which is
available in pop up message, Invalid claim
number get generated on screen as
"201700004".(Refer Evidence 7 for details/
Screenshots-Evidences 18- Jan.doc)
Note:Claimant who has suspended policy can
make a claim if claimant is eligible for cover.
[Teksolto: 19 Jan] Still issue are pending.
[Teksolto: 23 Jan]Changed defect priority from
P2 to P4.

[Nigel: 21 Dec] Follow the same process as for


Broken Bones claims. Click on Decision button
for the 1st time: only option is CREATE RESERVE.
Click on Decision button for the 2nd time after
creating reserve: 3 options available (ACCEPT,
DECLINE, EX-GRATIA). Please use the same
wording as for Broken Bones claims.
[AL Response 24 Jan] The issue has been
resolved

Yes

[AL Response - 18 Jan] Issue Resolved


[Teksolto: 19 Jan] Still issue not resolved, can u
clarify what you resolved???

Anda mungkin juga menyukai