KT plan

S.no. KT session on Duration

1 Scripting Process 2 weeks

2 Test Plan 1 day

3 CVS 1 day

4 QC 1 day

5 Toll gate Checklist for Scripting 1 day

6 Application and domain knowledge 2 days

7 Use case wise functional knowledge 2 weeks

Classification: GE Internal

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


Major Change

















































PROCESS FLOWS IN SCRIPTING TEAM

WRITING SCRIPTS

Get all the WR Docs planned for that release

Study the WR Doc, raise an Issue log

Attend the walkthrough of the WR given by GE BA

Get the Issue Log cleared

After getting the idea of the WR, have an LoE prepared for that WR for CS Scripting

BR & FD Doc changed by BSL BA and gets Sign-off for the changes

Get Test Conditions for the WR from GE BAAnalyse Test Conditions and identify how many existing scripts are affected because of the

WR

Identify how many scripts have to be remediated for the WR

For remediating a script , include the new test condition that can be validated in the script,

and complete the flow

Change the criteria (aWRount 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 AWRount 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 loopAfter the Scripts are reviewed and any comments given to change the scripts by GE BA,

change the scripts aWRordingly,and mail the scripts again to GE BA, WR 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 UWRondition 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



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 ChangeChange the Script as per the analysis done, note the changes done in the Version sheet of the

script


Update the changes done in the Scipt, in Test Plan in TD/QC 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


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 aWRount 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 aWRount 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

















































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


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.



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

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


TEST STEPS

TS contains 6 columns they are subject, test name, step, condition id, description and expected resultCopy the above columns from the sheet which needs to be uploaded into the TS sheet of TD

templateType 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 order3. 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


WHILE UPLOADING SO/TS INTO TEST DIRECTOR


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.




TS contains 6 columns they are subject, test name, step, condition id, description and expected result









CHECKLIST FOR REMEDIATION OF A SCRIPT WHILE SOLVING AN "IR"

1. Check-out that particular script from CVS/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 CVS/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.





1. Check-out that particular script from CVS/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.



RESPONSIBILITY 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 review of impacted scripts and 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), if there is a major remediation required 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.



RESPONSIBILITY 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 review of impacted scripts and then 1st level of verification with Test Data team.

4. Capture the issues (Criteria/Test Steps/Conditions).



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), if there is a major remediation required during IR fixing.

11 .Only Team SPOC/Lead will communicate with regard to Release communications.1 2 . 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.





8. Follow up with BSL BA or get-in-touch with GE BA for CC test conditions before the deadline.



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



Fail





KT plan

Documents