System Name-Script Title Test Script
Company Logo / Document: Script NumberVersion: Version Number

System Name:System Name[greyed fields can be updated by clicking File, selecting Properties, custom Tab, and then typing in a new value for the corresponding text. Press ctrl –a and then F9 to update all fields]

Script Title: Script Title

Location:Location

Document Number:Script Number

Version Number:Version Number

Pre-Execution Approval

Approval signatures indicate that the approvers are in agreement with the content of this document.

Author:

Author Name
Title / Date

Approved by:

Name
Title
System Owner / Date
Name
Title
(Add if needed)
Note: Keep signatures to minimum to satisfy requirements. / Date
Name
Title
SME / Date
Name
Title
QA / Date

Post-Execution Approval

The signatures below indicate review and approval of the executed script.

Approved by:

Name
Title
System Owner / Date
Name
Title
(Add if needed)
Note: Keep signatures to minimum to satisfy requirements. Must be the same as the pre-approvers / Date
Name
Title
SME / Date
Name
Title
QA / Date

Template Instructions: (Delete this page after completion of this template.)

All instructions are in red. Please follow the instructions and fill in information as appropriate.

Some instructions are fields.

Fields may be updated by changing in the document properties, selecting all and pressing F9.

Make sure all instructions are removed prior to sending for review.

SPELL CHECKprior to sending for review.

Update(F9) TOC prior to sending for review.

More information can be added to this template but content cannot be taken away unless instructed.

Add page breaks as necessary. (CTRL-enter)

All signers should receive this document for electronic review prior to sending for signature

Number test steps to facilitate references in comments or deviations, etc. Combination of test number and step number provides a unique reference.

Version History

Version / Description / Author / Date
a.b / MM/DD/YYYY

Draft versions may be tracked with versions such as 0.1, 0.2, etc. Draft revision history may be removed when v. 1.0 is created for signing.

For description of Version 1.0 Description say “Initial version for approval”.

Below is a table showing what this looks like when there are additional versions.

Version / Description / Author / Date
1.0 / Initial Version for Approval / [Previous Issue Date]
x.y / <Fairly detailed list of changes> / MM/DD/YYYY

1.0Purpose

The purpose of thisscript is to demonstrate that the Script Title…..(Define the purpose of the script)

2.0Script Environment

Describe the requirements in terms of the systems to be used (development, production, quality assurance instances, etc.).Will some testing be performed in one location while other testing is performed in another, etc.?

2.1.Testing Requirements

The testingrequiresthe following …

Indicate special testing needs in each environment if there are more than one. For example, will there be specific printers, scanners, servers, software clients, testers in each operational zone?

Identify the personnel and system resources required to complete the testing.

2.2.Test Data

This section should explain where data for testing purposes will come from and how and where it will be documented for testing. This is used in combination with the test prerequisite section of each test script.

3.0Script Execution Instructions

3.1.General Instructions

  1. Execute the protocol according to the requirements of SOP XXXXX, “Validation/Qualification Execution Instructions”.
  2. All entries must be recorded in accordance with SOP XXXXX. “Proper Completion of Documentation/Records.”

3.2.Deviations

Deviations shall be handled according to SOP XXX“Protocol Deviations.”.

3.3.Signature Identification Sheet

Each person who signs and/or initials any part of the executed test scripts, deviations or attachments is required to complete the Signature Identification Log. The sheet may be copied as needed.

3.4.Training Sheet

Executors of test scripts must complete the training log to verify that they have had the necessary training required to perform the protocol execution and operate the software.

4.0Signature Identification Sheet

The following is a record of each individual involved in the execution and verification of the tests and/or procedures in this document. Name (printed), title, full signature, initials, and date shall identify them. Duplicate this form, if needed.

Name (print)
Title / Signature / Initials / Date

4.1.Training Sheet

Name (printed) / Trained In (list doc no. as appropriate) / Verified by: (signature)
and Date

ConfidentialPage 1 of 9October 17, 2018

System Name--Script Title Test Script
Company Logo / Document:Script Number Version: Version Number

4.2.System Function A, B, C, etc.System Name

Test Objective / [This will be a series of tests, 7.2, 7.3, 7.4, etc., testing the functions described in the title of the test. Briefly state the objective of the test in this section.]
Test Method / Describe the test method to be used.
Acceptance Criteria / The acceptance criteria must relate to the objective. Expected and actual the same is not AC.
Prerequisite / [Describe any required prerequisites for this test, or say 'None' if there are no prerequisites]
Setup Data / Describe any configurations or setup that must occur for the script to execute successfully.
4.2System Function A, B, C, etc.> System Name
Step / Expected Result / Actual Result / Pass/ Fail / Performed By Init./Date
  1. <Test step directions>

  1. <Test step directions>

Comments:
Reviewed By: / Date:

ConfidentialPage 1 of 9October 17, 2018

System Name--Script Title Test Script
Company Logo / Document:Script Number Version: Version Number
4.2System Function A, B, C, etc.System Name
Acceptance Criteria / List the AC from the table above.
Test Script Overall Status PassFail
Comments:
Reviewed By: / Date:

ConfidentialPage 1 of 9October 17, 2018