For writing new Scripts

Assign temporary Condition id's for the Test Conditions provided

Write Scripts such that conditions are validated in the Scripts
Assign temporary Script id's to the Scripts
Send Scripts for Sign off to the resp GE BA, keeping BSL BA in the loop
Update the same in template which contains the list of temporary condition and script id's
Include the scripts, new and remediated in Cycle 1,2,3 of the repository for that release
Classification : Internal
IR RESOLUTION
If an IR is directly assigned to Assurance (Scripting) team, the status of the IR would be NEW
Analyze the IR
If the Script needs to change, check if it is a minor or a major change
Minor Change
Track the changes done in Format Tracker for that release
Major Change
If the Criteria needs to change, check if it is a minor or a major change
Minor Change
Track the changes done in Format Tracker for that release
Major Change
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
PROCESS FLOWS IN SCRIPTING TEAM
WRITING SCRIPTS
Get all the CC Docs planned for that release
Study the CC Doc, raise an Issue log
Attend the walkthrough of the CC given by GE BA
Get the Issue Log cleared
After getting the idea of the CC, have an LoE prepared for that CC for CS Scripting
BR & FD Doc changed by BSL BA and gets Sign-off for the changes
Get Test Conditions for the CC from GE BA
Analyse Test Conditions and identify how many existing scripts are affected because of the
CC
Identify how many scripts have to be remediated for the cc
For remediating a script , include the new test condition that can be validated in the script,
and complete the flow
Change the criteria (account or test) to include the changes done, and attach it in the script
For writing new Scripts
Assign temporary Condition id's for the Test Conditions provided
Write Scripts such that conditions are validated in the Scripts
Each Script should have a minimum of one condition, and try to avoid validating many
conditions in a single script
Assign temporary Script id's to the Scripts
Also write the Test Criteria or Account criteria for the Script whichever is necessary, attach
them along with the script
Prepare a template which gives the list of which condition is validated in which script(as per
temporary id's) for both new and remediated scripts
Send Scripts for Sign off to the resp GE BA, keeping BSL BA in the loop
After the Scripts are reviewed and any comments given to change the scripts by GE BA,
change the scripts accordingly,and mail the scripts again to GE BA, cc BSL BA, for final Sign-
off
After getting final Sign-off for the Scripts and Criteria assign the Condition and script id's
from repo i.e.; QA Ledger and UCCondition Id's Inventory
Update the same in template which contains the list of temporary condition and script id's
Include the scripts, new and remediated in Cycle 1,2,3 of the repository for that release
Classification : Internal
IR RESOLUTION
If an IR is directly assigned to Assurance (Scripting) team, the status of the IR would be NEW
If the IR is analysed by some other team and later assigned to Assurance team then the status
of the IR would be Assigned
Analyze the IR
If the Script needs to change, check if it is a minor or a major change
Minor Change Change the Script as per the analysis done, note the changes done in the Version sheet of the
script
Track the changes done in Format Tracker for that release
Update the changes done in the Scipt, in Test Plan in TD in the correct path, changes would be
automatically reflected in test lab.
Change the status of the IR to Ready For Retest (RFR), and assign it to Execution team. Also
enter the rootcause for the IR.
Major Change
Major change generally includes those changes which would effect Test Conditions validated
in the script
Change the script and criteria if necessary as per the analysis done, and Mail the changed
script and the old script to resp GE BA for review.
If the changes done are approved by GE BA then follow similar process as in case of changing
script for Minor Change
If the Criteria needs to change, check if it is a minor or a major change
Minor Change
Change the Criteria as per the analysis done after discussing with TestData team, note the
changes done in the Version sheet of the criteria
Track the changes done in Format Tracker for that release
If it is a test criteria which is changed then attach the changed Test Criteria to Test Plan for
that script, removing the old version of the Test Criteria, changes would be automatically
Assign the IR to Test Data team, to provide a new account as per the changed criteria, and
give proper comments for the other team to understand. Also enter the rootcause for the IR.
After TestData team has the account ready, they will change the status to RFR and will assign
it to Execution.
Major Change
Major change generally includes those changes which would effect Test Conditions validated
in the script
Change the criteria and script if necessary as per the analysis done after discussing with
TestData team, and Mail the changed script and the old script to resp GE BA for review.
If the changes done are approved by GE BA then follow similar process as in case of changing
Criteria for Minor Change
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
CHECKLIST FOR PREPARATION OF TD TEMPLATE
TD Template consists of 2 Sheets i.e. SO (Script Overview) and TS (Test Steps)
SCRIPT OVERVIEW
Checklist
1. Cut the text written in assumptions column and Paste in the test script description column.
2. Leave the creation date, design, status and assumptions columns as blank.
3. There shouldn't be any strike through present in the entire sheet. If present then delete that.
TEST STEPS
TS contains 6 columns they are subject, test name, step, condition id, description and expected result
Checklist
1. In all the rows of the "test step" column the test script id must be present
2. All the steps in the "step" column must be in order
4. There shouldn't be any strike through present in the entire sheet. If present then delete that.
WHILE UPLOADING SO/TS INTO TEST DIRECTOR
Select the part of the script to be uploaded into TD (except the heading row named subject, test name, etc.)
Click on "Tools" in the menu bar of excel sheet, then click on "Export to Test Director"
Follow the steps carefully after "Test director export whizard" opens.
Checklist
1. Select SO/TS properly
2. Map the columns in the excel sheet with that to be uploaded into TD very carefully.
3. After uploading the script attach the "Test Criteria" in Test Plan of Test Director for all the uploaded scripts.
Classification : Internal
CHECKLIST FOR PREPARATION OF TD TEMPLATE
TD Template consists of 2 Sheets i.e. SO (Script Overview) and TS (Test Steps)
Make a new excel sheet in your desktop, having two sheets named as SO and TS. There
should be 3 different templates for Cycle I,II, and III as it would be easier while uploading
SCRIPT OVERVIEW
SO contains 10 columns they are subject, test name, test script description, creation date,
design, status, actor, assumptions, host, mode. Copy the above columns from the sheet which needs to be uploaded into the SO sheet of TD
template Type the appropriate path in the Subject column where the script will be loaded into test
director.
Checklist
1. Cut the text written in assumptions column and Paste in the test script description column.
2. Leave the creation date, design, status and assumptions columns as blank.
3. There shouldn't be any strike through present in the entire sheet. If present then delete that.
TEST STEPS
TS contains 6 columns they are subject, test name, step, condition id, description and expected result Copy the above columns from the sheet which needs to be uploaded into the TS sheet of TD
template Type the appropriate path in the Subject column where the script will be loaded into test
director.
Checklist
1. In all the rows of the "test step" column the test script id must be present
2. All the steps in the "step" column must be in order
3. If more than one condition is validated in a particular step then the condition id should be
changed by using "/" e.g. C_CS13_205 / 39
4. There shouldn't be any strike through present in the entire sheet. If present then delete that.
WHILE UPLOADING SO/TS INTO TEST DIRECTOR
Select the part of the script to be uploaded into TD (except the heading row named subject, test name, etc.)
Click on "Tools" in the menu bar of excel sheet, then click on "Export to Test Director"
Follow the steps carefully after "Test director export whizard" opens.
Checklist
1. Select SO/TS properly
2. Map the columns in the excel sheet with that to be uploaded into TD very carefully.
3. After uploading the script attach the "Test Criteria" in Test Plan of Test Director for all the uploaded scripts.
Classification : Internal
TS contains 6 columns they are subject, test name, step, condition id, description and expected result
Select the part of the script to be uploaded into TD (except the heading row named subject, test name, etc.)
3. After uploading the script attach the "Test Criteria" in Test Plan of Test Director for all the uploaded scripts.
Classification : Internal
Classification : Internal
Classification : Internal
CHECKLIST FOR REMEDIATION OF A SCRIPT WHILE SOLVING AN "IR"
1. Check-out that particular script from VSS into your working folder by giving appropiate comments.
2. Remediated the step as per the requirement, but don't delete any text - make that text as strike through.
3. Any changes made in the exsisting script during the release should be with the release
colour as decided by the release SPOC.
4. Give appropiate comments in the "Version" sheet for that particular script.
5. Save the changes made and Check-in the script into VSS.
6. Make the same changes in the Test Plan for that particular script and click on save button. 7. Track all the changes made to that particular script in the Format Tracker prepared for the
release.
Classification : Internal
Classification : Internal
1. Check-out that particular script from VSS into your working folder by giving appropiate comments.
2. Remediated the step as per the requirement, but don't delete any text - make that text as strike through.
Classification : Internal
RESPONCIBILITY OF A TEAM MEMBER DURING ANY RELEASE
1. List out the WRs (scope for the release) you own it for that Release.
2. Prepare xls sheet with Impacted Use case(s)/scripts IDs for reference.
3. Do a peer reviewof impacted scriptsand then 1st level of verification with Test Data team.
4. Capture the issues (Criteria/Test Steps/Conditions).
5. Update those issues in the "Issue Log" template and forward it to the respective BSL BA for signoff.
6. After receiving the signoff, necessary remediation should be done in the Test Script(s) ASAP.
7. Validate the updated script in the VSS (Check-out and Check-in).
8. Follow up with BSL BA or get-in-touch with GE BA for CC test conditions before the deadline.
10. Ensure to get signoff of script(s), ifthere is a major remediationrequired during IR fixing.
11.Only Team SPOC/Lead will communicate with regard to Release communications.
13. Always keep updated within the team w.r.t to any process/task.
Classification : Internal
RESPONCIBILITY OF A TEAM MEMBER DURING ANY RELEASE
1. List out the WRs (scope for the release) you own it for that Release.
2. Prepare xls sheet with Impacted Use case(s)/scripts IDs for reference.
3. Do a peer reviewof impacted scriptsand then 1st level of verification with Test Data team.
4. Capture the issues (Criteria/Test Steps/Conditions).
5. Update those issues in the "Issue Log" template and forward it to the respective BSL BA for signoff.
6. After receiving the signoff, necessary remediation should be done in the Test Script(s) ASAP.
7. Validate the updated script in the VSS (Check-out and Check-in).
8. Follow up with BSL BA or get-in-touch with GE BA for CC test conditions before the deadline.
9. Write the new scripts as per the test condition received and send them for Sign-off to GE
BA keeping BSL BA and Scripting Team Lead in Loop.
10. Ensure to get signoff of script(s), ifthere is a major remediationrequired during IR fixing.
11.Only Team SPOC/Lead will communicate with regard to Release communications.
12. Use proper subject line while sending Emails like "Release_Name/Script Id/Issue (in
brief)" e.g. R7.2 STS_100_01:Step 16 remediation OR R7.2 ST IR#12345
13. Always keep updated within the team w.r.t to any process/task.
Classification : Internal
5. Update those issues in the "Issue Log" template and forward it to the respective BSL BA for signoff.
6. After receiving the signoff, necessary remediation should be done in the Test Script(s) ASAP.
8. Follow up with BSL BA or get-in-touch with GE BA for CC test conditions before the deadline.
Classification : Internal
DUTIES OF RELEASE SPOC
1. Co-ordinate with the Team Lead and Project Manager to get the testing scope for the release.
5. Keeps track of the count of scripts and the changes made in the Data Sheet.
6. He/She is responsible for any kind of Release Communication with regard to Scripting Team.
7. To give regular update to the Team Lead with regard to the scripting activities within the team.
Classification : Internal
DUTIES OF RELEASE SPOC
1. Co-ordinate with the Team Lead and Project Manager to get the testing scope for the release.
2. Prepare the Data Sheet as per the testing scope for that release. (The sample of the Data
Sheet is present in the next sheet)
3. Co-ordinate with the team members on a daily basis to get the updates regarding the WRs
in scope and like wise update in the data sheet.
4. Divides the task of uploading scripts into test director among team mates and ensures all
the scripts are uploaded correctly.
5. Keeps track of the count of scripts and the changes made in the Data Sheet.
6. He/She is responsible for any kind of Release Communication with regard to Scripting Team.
7. To give regular update to the Team Lead with regard to the scripting activities within the team.
8. Once the execution starts the SPOC should keep a track on which scripts executed on a
particular day, how many got passed and how many got failed? 9. Follow the Execution Strategy decided by the Team Lead/PM and move the passed scripts
to ST or UAT phases as per the need. This process of moving the scrpts is done on a daily
basis.
10. Co-ordinates with the team to close IR's related to assurance and gives the daily status
update to the Release Lead
11. Communicates with Test Data and Execution Team (both ST and UAT) for any updates or
changes made in the execution plan.
Classification : Internal
1. Co-ordinate with the Team Lead and Project Manager to get the testing scope for the release.
6. He/She is responsible for any kind of Release Communication with regard to Scripting Team.
7. To give regular update to the Team Lead with regard to the scripting activities within the team.
Classification : Internal
Classification : Internal
EXECUTION STRATEGY
This execution strategy was agreed by both BSL and GE for release 7.3 onwards. But please
do check with your team lead / project manager regarding this as in future this strategy
might change.
Classification : Internal
Classification : Internal
SL No. WR # Impacted / New Script ID Use Case
Available in
Test Lab
Test
Criteria
Attached
The Data Sheet contains 4 sheets
(a)Release Summary (b)Data Sheet
(c)Execution Status (d)History.
To be filled by Scripting Team
Classification : Internal
Other Attachment Reqd(ex
CPT\Verification matrix etc) Comments
Account
Expires
on Date
To be filled by Scripting Team To be filled by TestData Team
ST Pass1 Accounts ST Pass2 Accounts
Classification : Internal
Account
Expires
on Date
Comments
Date of
Execution IR No. Comments
To be filled by TestData Team To be filled by Execution Team
Status (Pass/Fail/No-Run)
Classification : Internal
Impacted New Passed Failed
2284 Customer Profile Customer Profile 71
Work with Request Work with Request 4
1979 Account Lookup Account Lookup 66
1941 Agent HomePage Agent HomePage 11 8
10013 Cross Sell Cross Sell 62
2423 Lost/Stolen
Lost/Stolen
28
2020A Manage a Request
Manage a
Request/Work with
request
24
2375 CCL - Increase/Decrease
CCL -
Increase/Decrease
140
Total No. Of Scripts 406 8
No. Of Scripts
414
This is an example of how Execution
Status is Maintained.
Number Of the Scripts
WR # Use Case Use Case Impacted
Classification : Internal
No Run
Number Of the Scripts Percentage
Of Execution
Classification : Internal
SL No Date Particulars
1 3/29/2007 Script Ids-188_03,378_01,192_03 were descoped
This is an example of how the
History of the Release is maintained.
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Reason
These scripts belong to Customer profile,needed exxon mobil
accounts hence descoped as per GE BA
Classification : Internal
Classification : Internal
Classification : Internal
Classification : Internal
Use Case Scripting
SL No. WR # Primary Secondary Primary Owner
1 2284
Customer Profile
Jagan
2
Work with Request
Archana
3 1979
Account Lookup
Jagan
4 1941
Agent HomePage
Jagan
4 10013
Cross Sell
Vathsala
5 2423
Lost/Stolen
Rajiv
6
2020A Manage a Request
Archana
7 2375
CCL - Increase/Decrease
Atul
This is an example of how a summary for a
Data Sheet is maintained during any release.
Classification : Internal
Test Data Execution Team
Secondary Owner Primary Owner Secondary Owner
Shilpa Prachi Kauma
Abhishek
Shilpa Samandeep Neelima
Shilpa Samandeep Neelima
Atul Srinivas Lavanya
Layana Shventank Nirupa
Abhishek Bijoy
Vathsala Seralathan Siji
Classification : Internal