Section 1. Pre Implementation Testing: Not Only Those Requiring NBIM Assistance

You might also like

Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 8

GCARS TESTING TEMPLATE

NOTE: This is not required for Informational GCARS, NBIM Internal Deploys or FW changes. not only those requiring NBIM assistance. Created By: Last Update: Updated By: Changes are in RED Sharon Knowles 14-Jul-10 Sharon Knowles

GCARS Number U-8LHCLT-F90 Global Helpdesk Notified? Monitoring Notified? User Guide Provided to GHD?

Section 1. Pre Implementation Testing


Section 1 & 2 are to be filled out and attached to GCARS BEFORE Approvals

NOTE: If Global Helpdesk Testing is required, this DOES NOT take the place of the email that needs to be sent to the Global Helpd

Functional Area(s)

Who Performed the Test

Contact Number of Tester (cell)

Email Address of Tester

CSC Technical Global Helpdesk ITS Third Party Vendor (Vendor Name)

Sumavardhan R Pakanati

9949971825 spakanati@csc.com

N/A This is sample data only N/A This is sample data only

Section 2. Planned Post Implementation Testing (note: all post testing should occur within t
Section 1 & 2 are to be filled out and attached to GCARS BEFORE Approvals

Functional Area(s)

Who Will Perform the Test

Contact Number of Tester (cell)

Email Address of Tester

CSC Technical Global Helpdesk ITS Third Party Vendor (Vendor Name)

Sumavardhan R Pakanati

9949971825 spakanati@csc.com

N/A N/A

Section 3. Actual Post Implementation Testing (note: all post testing should occur within th
Please fill this section out and attach to GCARS again AFTER post testing is complete.

Functional Area(s)

Who Performed the Test

Contact Number of Tester (cell)

Email Address of Tester

CSC Technical Global Helpdesk ITS Third Party Vendor (Vendor Name) N/A N/A

nal Deploys or FW changes. It is required for all other changes,

to be sent to the Global Helpdesk to notify them of the need for testing.

Date of Test

Type of Change (Baseline, SR, Project) 9:00 CET 9:00 CET Baseline

10-Oct-11

should occur within the change window)

Planned Date(s) of Test Planned Start Time(s) No High Severity Tickets To Be Raised During this Testing Period - Plan Carefully. No High Severity Tickets To Be Raised During this Testing Period - Plan Carefully.

Planned End Time(s) No High Severity Tickets To Be Raised During this Testing Period - Plan Carefully.

Type of Change (Baseline, SR, Project)

10-Oct-11

9:00 CET

9:00 CET

Baseline

hould occur within the change window)


Actual Date(s) of Test No High Severity Tickets To Be Raised During this Testing Period - Plan Carefully. Actual Start Time(s) No High Severity Tickets To Be Raised During this Testing Period - Plan Carefully. Actual End Time(s) No High Severity Tickets To Be Raised During this Testing Period - Plan Carefully. Type of Change (Baseline, SR, Project)

Type of Test

Expected Results

Actual Results

Pass / Fail

Send emails though application servers xxx

email should deliver without fail xxxx

email should deliver without fail xxxx

xxxx xxxx

Type of Test

Expected Results

Actual Results

Pass / Fail

Send emails though application servers

email should deliver without fail

email should deliver without fail

xxxx

Type of Test

Expected Results

Actual Results

Pass / Fail

Comments / Notes

xxx xxx

Comments / Notes

xxx

Comments / Notes

You might also like