KT Plan - Exe

S.no.
KT session on Duration
1 Execution Process 1 day
2 Modes of execution 1 week
3 Quality center tool 2 days
4 Toll gate Checklist for execution 1 day
5 DTS testing, NICE testing 1 day
6 IR process 1 day
Classification: Birlasoft Internal
EXECUTION CHECKLIST
Check whether Hand book from Build team is available.
Data sheet.
Assumptions Document.
The Handbook :
Data Sheet :
Assumptions Document :
Classification: Birlasoft Internal Classification : Internal
EXECUTION CHECKLIST
Check whether Hand book from Build team is available.
Data sheet.
Assumptions Document.
The Handbook : The Handbook consists of the details such as Contact Informations of the respective persons,
Instance & User ID
details, Test Director details including Test Director URL, path in the Test Plan and Test Lab ,
Name of the Defect Phase etc.
Data Sheet :
Data Sheet contains the fields such as Script ID, CC, Usecase, Account number, Date of
Execution, Status of script and IR number. Execution SPOC deals with the Datasheet.
Assumptions Document :
Assumptions Document consists of the assumptions taken by the tester. For eg: if taken
support from any other team member to pass the particular script or scenario ,ignoring of a
particular step due to Production IR etc.
It consists of the particular Script ID, Usecase, Step number, Name of the Tester, Assumptions
taken and the Date. The tester should fill the Assumptions Document if any assumptions had

PROCESS FLOW OF EXECUTION TEAM
1 Preparation for Execution
Go through the the Test plan and Receive datasheet from respective teams.
Confirm that all the documents and data which are specified in the Execution checklist is
Identify the scripts which are in scope for the release, and ensure that they are loaded in the
(For ST Pass3 ,Scenarios are sent to the execution SPOC with accounts pasted.)
Scripts /Scenarios of Inbound phone mode are to be executed in ILABS and Those are of
Manual /Mail mode are to be executed in Birlasoft Office.
2 Executing the Script
Each team member is assigned with a set of Scripts/Scenarios.
If it is script ,it is taken from Test Director using the given path specified in Hand book and
start execution using the Account pasted in TestRun properties of TD .
If it is scenario ,it is taken from the Excel sheet sent by the Execution Team SPOC and starts
execution using the accounts pasted in it.
Script /Scenarios are being executed and if they are passing ,the run is saved as passed in TD
for the Script ,and the Status is sent as "PASSED" for Scenarios.
Update assumption document and Format Tracker( if needed).
If the Script/Scenario is failing in a step ,IR is raised and the run is saved as failed for the script
and Status is sent as "failed" with the IR number.
3 Executing RFR
Before executing the RFR ,the tester ensures it has a proper rootcause,proper comments ,and it
is assigned to Execution Team with Status "Ready for Retest".
If any of these is missing or incorrect IR can be reopened giving the reason in the "rootcause
While executing the RFR,if the script/scenario fails in the same step or in a step prior to the
step where the IR was raised,then IR is re opened by giving proper comments.
If new problem is faced in later step new IR is raised after closing the current IR , and the
While executing the RFR ,if the problem for which the IR was raised,is resolved, then IR is
If the script/scenarios is working fine then it is passed.
Update Assumption document and Format Tracker if needed.
4 Execution of Inbound mode Script/Scenario in ILABS
The Inbound phone mode Script /Scenario script can be of 3 types.
Normal inbound scripts/Scenarios ,IVR call Scripts/Scenarios , Call Transfer Scripts/Scenario
The difference between Manual/mail mode script and Inbound mode script is that ,for
executing the inbound mode scripts ,Calls are to be made from Call Masters and thus they are
For IVR call Scripts ,to make IVR calls ,the IVR process is to be followed , using the IVR
combinations specified in the Script/Scenario.
All other processes followed for execution of Inbound Script/Scenarios are same as that for
Manual/mail mode Scripts/Scenarios.
5 Leakage of IRs from ST to UAT
If there are IR s in UAT which are the leakges from ST side ,those Scripts/Scenarios can be
executed by ST Team during the RCA ,to confirm that whether those are real miss from ST

Get the Handbook
from the Build team
and the datasheet for
the release
Pass the script and update the
assumptions document (if
needed)
Pass
Fail
Raise IR
Scripts
/scenarios are
executed
Failed script
comes as RFR
Script
/scenario
Execution
Close the IR, pass the script
and update the assumptions
document (if needed).Ask the
scripting team to move the
passed scripts to pass 2.
Pass
Fail
Fail in same /
previous step
Yes
No
Check whether the
impacted scripts are
loaded in the TD in
the appropriate path
Reopen
Fail in some
later step
Close the current IR, fail the
script and raise a new IR for the
latter step
A

Get the Handbook
from the Build team
the release
needed)
Pass
Fail
Raise IR
Scripts
/scenarios are
executed
Failed script
comes as RFR
Script
/scenario
Execution
Pass
Fail
Fail in same /
previous step
Yes
No
Check whether the
loaded in the TD in
Reopen
Fail in some
later step
latter step
A

Get the Handbook
from the Build team
the release
needed)
Pass
Fail
Raise IR
Scripts
/scenarios are
executed
Failed script
comes as RFR
Script
/scenario
Execution
Pass
Fail
Fail in same /
previous step
Yes
No
Check whether the
loaded in the TD in
Reopen
Fail in some
later step
latter step
A

Get the Handbook
from the Build team
the release
needed)
Pass
Fail
Raise IR
Scripts
/scenarios are
executed
Failed script
comes as RFR
Script
/scenario
Execution
Pass
Fail
Fail in same /
previous step
Yes
No
Check whether the
loaded in the TD in
Reopen
Fail in some
later step
latter step
A

Get the Handbook
from the Build team
the release
needed)
Pass
Fail
Raise IR
Scripts
/scenarios are
executed
Failed script
comes as RFR
Script
/scenario
Execution
Pass
Fail
Fail in same /
previous step
Yes
No
Check whether the
loaded in the TD in
Reopen
Fail in some
later step
latter step
A

Get the Handbook
from the Build team
the release
needed)
Pass
Fail
Raise IR
Scripts
/scenarios are
executed
Failed script
comes as RFR
Script
/scenario
Execution
Pass
Fail
Fail in same /
previous step
Yes
No
Check whether the
loaded in the TD in
Reopen
Fail in some
later step
latter step
A
Modes of Execution
Normal Inbound Mode
3 modes of
execution

Manual Phone

Inbound

A
Normal
Inbound
Call Transfer

C B
CSR receives a call
from the call master
B
CSR accepts the call
with or without
account number
CSR is in AVAIL
Call Transfer Flow
A
CSR is in TALK
C
CSR is in TALK
CSR clicks on the
Call transfer icon
A pop up appears
which prompts the
CSR to enter an
extension number
Extension of the CSR to
which the call has to be
transferred is entered

CSR clicks on the
Initiate Transfer
button.
Call is transferred to the
other CSR
IVR Flow
other CSR
Pop up remains on the
screen. CSR clicks on
Complete Transfer
button
Pop up is closed. Call is
completely transferred
D
Take a call master other
than the one that is used to
receive the call
Press CALL APPR
CSR is in AVAIL
Enter #704 and then listen
to the ringtone of the
headset
Enter 18779691391
Listen to options from the
headset
headset
Select the options from the
IVR as per the
requirements in the script

CSR is in
A
Modes of Execution
Normal Inbound Mode
3 modes of
execution
Inbound
Call Transfer Interactive
Voice
Response
( IVR)

D
Mail

A
CSR receives a call
from the call master
CSR accepts the call
with or without
account number
AVAIL mode
Call Transfer Flow
TALK mode

TALK mode
CSR clicks on the
Call transfer icon
A pop up appears
which prompts the
CSR to enter an
extension number
Extension of the CSR to
which the call has to be
transferred is entered
CSR clicks on the
Initiate Transfer
button.
other CSR
IVR Flow
other CSR
Pop up remains on the
screen. CSR clicks on
Complete Transfer
button
Pop up is closed. Call is
completely transferred
D
Take a call master other
than the one that is used to
receive the call
Press CALL APPR
CSR is in AVAIL mode
#704 and then listen
to the ringtone of the
Enter 18779691391
Listen to options from the
Select the options from the
IVR as per the
requirements in the script
CSR is in TALK mode
A
RESPONSIBILITY OF A TEAM MEMBER DURING ANY RELEASE
1. Go through the test plan for the release .
2. Check for the scripts assigned is uploaded in Test Director.
4. Execute the steps according to the script .
5. Verify the Account Status Matrix, CPT matrix , Verify Matrix , etc.as and when needed .
6. If the script fails at any step proper support is taken from concerned team .
7. If the issue is still not resolved, an IR is raised .
8. Status is updated to the Team Lead.
9. In case of any assumption made by the executor it is updated in the Assumption Document in VSS.
12. Retest the script which came as RFR and CLOSE or REOPEN the IR accordingly.
13. Always keep updated within the team w.r.t to any process/task.
RESPONSIBILITY OF A TEAM MEMBER DURING ANY RELEASE
1. Go through the test plan for the release .
2. Check for the scripts assigned is uploaded in Test Director. 3. Check for the assumption part of the script and test criteria ,and set up the environment
accordingly.
4. Execute the steps according to the script .
5. Verify the Account Status Matrix, CPT matrix , Verify Matrix , etc.as and when needed .
6. If the script fails at any step proper support is taken from concerned team .
7. If the issue is still not resolved, an IR is raised .
8. Status is updated to the Team Lead.
9. In case of any assumption made by the executor it is updated in the Assumption Document in VSS. 10. If support is taken from Test Data or Scripting , it is updated in the Format Tracker Document in
VSS.
11. Check whether the raised IR is fixed by the concerned team and is assigned to the Execution team
as
Ready For ReTest with a proper root cause.
12. Retest the script which came as RFR and CLOSE or REOPEN the IR accordingly.
13. Always keep updated within the team w.r.t to any process/task.
ST Strategy
EXECUTION STRATEGY
This execution strategy was agreed by both BSL and GE for all releases
IT Strategy
Pass
Fail
Pass

ST Strategy
IT Execution
ST
Re execute Failed
UAT
ST Pass 3
UAT Pass 3
Re execute failed
Pass
Pass
Pass
Fail
Fail
Fail
Fail
Fail
Fail
Reexecute
failed scripts
IT Signoff

SL No. WR #
Impacted
/ New Script ID Use Case
Available in Test
Lab Test Criteria Attached
FORMAT OF DATA SHEET
To be filled by Scripting Team
Other
Attachment
Reqd(ex
CPT\Verification
matrix etc) Comments
Account
Expires
on Date
Account
Expires
on Date ST Pass1 Accounts ST Pass2 Accounts
FORMAT OF DATA SHEET
To be filled by Scripting Team To be filled by TestData Team
Comments
Date of
Executio
n IR No.
Comment
s Status (Pass/Fail/No-Run)
To be filled by TestData Team To be filled by Execution Team

S.No Script ID Usecase Step# Tester
FORMAT OF ASSUMPTIONS DOCUMENT
Assumptions Date Raised
FORMAT OF ASSUMPTIONS DOCUMENT
PROCESS & RULES TO BE FOLLOWED AT ILABS
1. Cellphones or any electronic devices are not be carried in GE workplace.
2. All accessories should be deposited at security before entering into GE premises.
3. Whenever we go to ILABS, GE Access cards are to be collected from & submitted at security.
4. Should not carry GE access cards backafter leavingILABS.
5. Shouldn't exchange/carry others access cards, thiswill lead to Security violation and high penality.
7. Should work on alotted dedicated machines.
8. We have access to 1B & 3A floors only.
9. Access cards will be deactivated if we dont swipe cards for more than 15 days
PROCESS & RULES TO BE FOLLOWED AT ILABS
1. Cellphones or any electronic devices are not be carried in GE workplace.
2. All accessories should be deposited at security before entering into GE premises.
4. Should not carry GE access cards backafter leavingILABS.
6. Approval should be taken from Nalin(SSO - 324027708) thru mailto enter GE ILABS atleast
in a day advance and activation of deactivated access cards.
7. Should work on alotted dedicated machines.
8. We have access to 1B & 3A floors only.
9. Access cards will be deactivated if we dont swipe cards for more than 15 days
DTS TESTING PROCESS
1. Infra team(Birlasoft)will initialize the logs and will inform testing team tostartexecutionof the scripts.
3.Testing team will take appropriate Screen Shotsof the flows doneas necessary.
5.Infra team(Birlasoft)creates the UI and non-UI files and sends an email to DWH team(Taruna Madaan).
6.DW team will load the UI and Non- UI files and send the details(Batch ID) to Reporting team(Shraddha Tyagi).
7.Reporting team will verify the necessary data and will send the results to all stakeholders.
DTS TESTING PROCESS
2.Testing team will capture the necessary data in the Excel Spreadsheet, which contains
details like Account used, user id used, time taken for navigation from screen to screen, etc.,
3.Testing team will take appropriate Screen Shotsof the flows doneas necessary.
4.Testing team willinforminfra team afterthe completion oftestingforUI and NON UI logs
to becapturedandsend theall details toDWH team
7.Reporting team will verify the necessary data and will send the results to all stakeholders.

KT Plan - Exe

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

KT Plan - Exe

Caricato da

Copyright:

Formati disponibili

S.no.

Potrebbero piacerti anche