Sie sind auf Seite 1von 85

Error #

Process / screen

Call center upsell Lead upload

Call center upsell Lead upload

Call center upsell Lead upload

Call center upsell Campaign

Call center upsell Campaign

Call center upsell Campaign

10

Call center upsell Campaign

20

Change in Policy

23

Create Policy

41

Create Policy

73

Call center upsell Lead upload

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

Call center upsell Campaign

200

Change in Policy

201

Call center upsell Lead upload

202

Call center upsell Campaign

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.

Invalid file type get accepted in lead upload form


Actual result
Upload leads file with invalid file type format, file get uploaded
Test Data
User upload file such as excel/doc/docx file type.
Expected Result
On upload of invalid file type on same page error should be displayed as "Only
CSV file types are allowed for batch upload" instead of upload of file.

Lead upload entered/selected data get refreshed/cleared when Previous button


clicked on lead upload page (Step2)
Actual Result
1. Enter Batch Desc, select file for upload and click on check box
2. Click on Next button, all file records get displayed
3. Click on Previous button and observe result
All previously selected/entered data get cleared.
This should be behaviour of Cancel Button.
There is no difference in Cancel and Previous buttons behaviour.
Test Data
User upload file, user enter batch description, User Select batch type.
Expected Result
All previously selected/entered data should be persisted on click of Previous
button on Step 2 of upload.

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

Change label of following 2 fields:


"Own / SP Gen" to "Spouse Gender"
"Own / SP DOB" to "Spouse DOB"

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.

Sub menus disappeared after transaction intended, selection of sub option


'Create Policy'
Actual Result
1. After Login core app screen selected menu 'Policy & Administration'
2. Goto sub option 'Tele Sale'
3. Selected option Transactions & any sub option as 'Create Policy'
4."Claim, Tele Sale, CSD" sub menu are disappeared.
Expected Result
After selected any sub Options as - 'create policy', these three sub menus
should be appeared "Claim, Tele Sale, CSD" .

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.

Observed Exception list report, It does not get displayed proper.


Actual Result
1. User enter batch description name, select already uploaded valid csv file to
upload.
2. User upload CSV file successfully.
3. User go to menu Tele Sale>Transactions>Campaign, Selected same 'Batch
description' as entered above.
4. Clicked on 'Exception List' button, Exception list report get displayed.
But the report content does not get displayed proper.
Test Data
selected already uploaded valid csv file to upload.
Expected Result
1. Header "Bank Exception List" should get changed into "Exception List".
2. Reference No. should get displayed for all data.
3. Label CNIC No. should get changed into MSISDN No, and hyphen should get
removed from MSISDN No.
4. Label "Account No, Branch Code, Mobile No & Package" get displayed on
report but not a single record get displayed for these label. If these labels are
not in use, Please Remove it.
5. DOB should get displayed for all data.
6. Description "CNIC already exist in DB" should change into "MSISDN No.
already exist in DB".

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' & 'Cover Type and clicked on 'Process' button.
2. Policy details get updated.
3. User go to 'CSD' menu and searched for same MSISDN which is selected for
update in 'Change In Policy Plan' page.
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???

Header 'Home' get displayed instead of 'Lead Upload'


Actual Result
1. User go to menu 'Lead Upload'
Header 'Home' get displayed on screen.
Expected Result
1.'Lead Upload' should get displayed instead of header 'Home'.
2. Header should get visible, Currently header is not displaying very clear.
Observations :
1. No space available between label and input box for below labels:
1. Batch Description
2. Batch Type
Expected Result
Space should get provided between label and input box.
Query: Why label 'Batch Description' colour is red???TBC by business.

No space available between label and input box.


Actual Result
1. User go to menu 'Campaign'
No space provided between label 'Batch Description' and input box.
By default "Name MSISDN Call Status Remarks Follow Up Date Proceed" & "No
data found." get displayed on screen
Expected Result
1. Space should get provided between label and input box.
2. By default "Name MSISDN Call Status Remarks Follow Up Date
"No data found." should not get displayed on screen.

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

Invalid values get set in 'Pay Method' dropdown.


Actual Result
1. User go to 'Create policy' page.
2. Do not select/enter anything in any input box.
3. Click on 'Product' dropdown box, Selected any product and clicked on 'Clear'
button.
Invalid value get set in 'Pay Method' dropdown box.
After click on 'Pay Method' dropdown box, invalid dropdown value get displayed.
Expected Result
After click on 'Clear' button, all the data should get clear from all fields.

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 Administration>CSD>Searched for valid MSISDN - On click of 'Details'


hyperlink, it takes approximate 7-8 minute to open the pop up.

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

NA, Refer test


data

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

Agent Upsell 18-01-2017

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)

[AL Response: 23 Dec]This is not possible. The user has to


make sure that he/she uploads the CSV file only.
Furthermore,as the user uploads the wrong file format and
presses Next, thengarbage data appears in the next screen
which shows that wrong file has been uplaoded. So, the user
can simply press cancel and try again to upload the corerct file
format.
[Nigel: 23 Dec] OK. I agree we can live with this as it is for the
time being. I have therefore reduced severity to P4.

Yes

[Teksolto: 3 Jan] Previously selected/entered data does not get


persisted on click of Previous button. Entered/selected data get
refreshed/cleared when Previous button clicked on lead upload
page (Step 2)

[AL Response: 16 Jan] Flow of each option available in Campain


required complete document. Initially proceed for policy option
developed, rest of the options can be develop in Post
Implementatin phase with reports. These are not showstoper
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 back after the Follow Up
Date is reached. Follow Up Date should be compulsory. We can
discuss alternatives if this flow is complex to implement.
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 Proceed button.
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 with a valid future date,
user should receive the following error message: Please
provide a valid follow up date for {MSISDN}.
Block Follow Up Date field if Call Status = Invalid number, No
call made, Offer accepted, Offer declined.

[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 back after the Follow Up
Date is reached. Follow Up Date should be compulsory. We can
discuss alternatives if this flow is complex to implement.
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 Proceed button.
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 with a valid future date,
user should receive the following error message: Please
provide a valid follow up date for {MSISDN}.
Block Follow Up Date field if Call Status = Invalid number, No
call made, Offer accepted, Offer declined.

[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 back after the Follow Up
Date is reached. Follow Up Date should be compulsory. We can
discuss alternatives if this flow is complex to implement.
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 Proceed button.
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 with a valid future date,
user should receive the following error message: Please
provide a valid follow up date for {MSISDN}.
Block Follow Up Date field if Call Status = Invalid number, No
call made, Offer accepted, Offer declined.

Yes

As per our understanding of the product specs, in HCP,


beneficiary is the client, not the spouse. Policy terminates in
case of death of client.
[Nigel: 13 Dec] You are correct that the spouse details should
not be listed under beneficiary. But the main problem is that the
policy was captured with Product Type = Family, but it is
activated with Product Type = Individual.See Evidence 2 and
Evidence 4 screen shots in the 6 Dec file. It appears that Family
policies are being created as Individual policies, which wil
prevent any further testing on Family policies.
[AL Response: 20 Dec] Kindly refer to the CSD screen, under
the Cover heading the correct Product Type, whether it is Family
or Individual, should appear now. However, this will only apply
to fresh cases being issued; not on historical data.
[Teksolto: 20 Dec] Issue retested below are the observations
after retest.
Family type get set to Policy after policy creation with correct
amount as 173,800 .
Main issue resolved for Family type policy creation so reducing
serverity from P1 to P2
There are other minor issues still exists - evidence are provided
in file named as "ScreenShots-Evidences 20-DecIssue#23.doc" on shared location.
(1) Evidence 1
Age get calculated wrongly for same date age calculate as 26
and 27

[AL Response: 21 Dec] We would strongly recommend that this


feature remain un touched. The reason being that once your
users are well trained they might not want to type headings in
the first row. This means that all the user has to do now is to un
check the check box titled First row contains column header &
he may proceed. If we do it the way you have recommended
this feature will no longer be available to the user. Secondly we
feel the check box is self-explanatory & will not cause any
ambiguity to the user.
[Nigel: 21 Dec] We are not asking to remove the check box, but
simply a way of correcting the upload if the check box was
mistakenly not ticked when the upload file contains a header
row. The easiest solution seems tobe to use the Previous
button on the 2nd screen where the user will see their error to
go back to the file upload screen (1st screen) and tick the check
box. But currently the 1st screen is cleared after clicking the
previous button. Can you change this so it "remembers" the
data previously captured (i.e. batch description and file to be
uploaded)?

[Nigel: 21 Dec] Set Create Date = Issue Date. Is it possible to


differentiate between USSD self-registrations and USSD agent
registrations? If it is possible, setUser ID = USSD - Subscriber
for self-registrations and USSD - Agent for agent registrations.
[AL Response: 14 Jan] TheUser ID for the policies issued via
USSD is not possible in test as they are issued using the
simulator.
[Nigel: 23 Jan]Will User ID and Create Day be set in production
environment? And what will they be set to for self-registations
and for agent registrations?

Previously searched data is appearing when re-navigated to


CSD page, as it gets cached. Should not interfere with any
procesing/testing. We propose this error is moved to P3.
[Nigel: 23 Jan] I'm happy to change to P3 priority.

Yes

[AL Response - 17 Jan] Now the policy can be issued via


CoreApp for the Hospital Cash on the MSISDN which was
previously used for regestration of Broken Bone. Furthermore,
user have to reselect the Title in order to display Gender in
input field. Besides Gender, rest of the previously saved details
is already fetched by entering the valid MSISDN.
[Teksolto: 18 Jan] Issue retested and Observations are below:1. Major issues hasbeen resolved, Hospital Cash Policy get
created via CoreApp for MSISDN which is already registered for
'Broken Bone' policy through CoreApp.I have changed priority to
P3.
2. "Gender' and 'Title' Should get fetched automatically as rest
of the previously saved details get fetched by entering the valid
MSISDN.

[AL Response 24 Jan] Issue resolved.

Yes

[AL Response: 14 Jan] This issue has been resolved. Please


retest.
[Teksolto: 16 Jan] Issue retested below are the observations
after retest:1. Do not entered/selected any value in any input/dropdown
box, and clicked on'Pay Method' dropdown box, invalid data get
displayed in dropdown box.(Refer Evidence 1 for details/
Screenshots-Evidences 16-Jan.doc
Note: 'Pay Method' dropdownvalue should not get
displayeduntill user does not select'Premium Mode'.
[AL - 18 Jan] 1. Have viewed evidence file but it shows "Pay
Method" dropdown as blank. Which invalid value are you
referring to please clarify.
2.Incorrect 'Pay Method' cannot be selected, whatever
'Premium mode' is. Prepopulated fields would help in efficiency
as they would be set to most common type of premium mode.
[Teksolto: 19 Jan] Issue retested below are the observations
after retest:1. Do not entered/selected any value in any input/dropdown
box, and clicked on 'Pay Method' dropdown box, 'Blank'
dropdown value get displayed.
2. But if user click on 'Premium Mode'or 'Product Type'
dropdown box,there is no any dropdown value get displayed as
blank.
3. Can you clarify why 'Blank' dropdown value is displaying in
'Pay Method' dropdown box.
[Teksolto: 23 Jan]Changed Priority from P2 to P3.
This defects is about inconsistancy in drop down values

Proposed
solution

Das könnte Ihnen auch gefallen