Test Protocol and Test Plan

In a validation project, Tests Plans or Test Protocols are used to demonstrate that a system meets requirements previously established in specification, design, and configuration documents. Test Plans document the general testing strategy; Test Protocols are the actual testing documents. In many cases, the Test Plan and Test Protocol are combined into a separate document.

The Test Plan outlines the testing requirements and strategy. It should include the general process for performing the testing, documenting evidence of testing and the process for handling testing failures. The Test Plan may also include the types of testing, descriptions of environments where testing will be performed, who is responsible for testing, equipment or testing that will be used in testing, or other organizational requirements for testing.

Test Protocols describe the specific testing. Test Protocols are collections of Test Cases which check a specific element of the system. Each test case should include the purpose of the test, any pre-requisites that need to be done before testing, and the acceptance criteria for the test.

Each test case is made up of a series of test steps. Each step should include an instruction, an expected result, and the actual result. The instructions should include enough detail so that a tester can consistently perform the required testing activity. There should also be a place for the tester to assess whether each step passes or fails.

The process of following the instructions and recording the results is called “executing” the protocol. When executing test protocols, the tester should follow established Good Documentation Practices. This includes using a compliant computer system to record the testing results or documenting the results on paper and pen. Any discrepancy between the expected result and the actual result should be tracked as a deviation. Deviations should be resolved before validation is complete.

Software validation usually uses three specific testing protocols:

• Installation Qualifications (IQ) verify that systems are on machines suited to run the software, that the system has been properly installed and that the configuration is correct. These requirements are outlined in the Design Specification.
• Operational Qualifications (OQ) verify that systems perform as expected. The OQ tests requirements outlined in the Functional Requirements.
• Performance Qualifications (PQ) verify that systems perform tasks in real-world conditions. The PQ tests requirements outlined in the User Requirement Specification.

Engineering Validations sometimes use two additional testing protocols:

• Factory Acceptance Test (FAT) – Factory acceptance tests are an attempt to verify that the equipment meets requirements outlined in the User Requirement Specification or Functional Requirements. FATs are performed at the point of assembly. Customers will often ask to be present for FAT, though the tests are usually performed by the manufacturer. Many companies do not allow the company to ship the item without passing the factory acceptance test, and some contractual payments are dependent upon the item passing FAT.
• User Acceptance Test (UAT) or Site Acceptance Test (SAT) – User and site acceptance tests verify that the item performs as required by the User Requirement Specification or Functional Requirements. Once an item passes UAT/SAT, it is ready for use, unless other contractual arrangements are made between the user and the vendor.

Test Protocols should be approved before protocol execution. A copy of the unexecuted protocol should be kept in the validation package. The unexecuted protocol should be approved by the System Owner and Quality Assurance. The executed protocol should be signed by the tester and reviewed by the system owner and Quality.