Process Flow for Testing of

Computerized System

Purpose of SOP?

SOPs are written instructions that document a

routine or repetitive activity followed by an
organization.
The SOP for Testing of Computerized systems
applies to the activities associated with the
automated and manual testing of computerized
systems.
The SOP focuses on how to collect the
documented evidence in order to confirm that
the systems performs as intended and specified.

Process Flow for Testing

The process flow begins with determining a test
strategy and ends with the test summary report.

Process Flow for Testing

Determine Test
Strategy
Document the
Test Plan

Develop Manual
System
Test(MST)

Develop User
Acceptance Test(UAT)
Execute User Acceptance
Test(UAT)

Execute Manual
System Test
Create Defect
Log/Minor Issues
Log
Document the
Test Summary
Report
Obtain
signatures for all
documents

Submit Summary
Report to QA

Test Strategy
1.Test Strategy determines the overall techniques
that are going to be used for the testing of the
computerized systems.
2. Each application that is computerized may have
a different testing approach.
3. The Test Strategy will outline the test inputs and
verification of test results (outputs). It also includes
the method of capture of test results or proof of
testing.

Test Plan
1.Test plan is the systematic approach to test a
software system. The plan typically contains a
detailed layout of what the eventual testing
workflow will be.
2. It will provide details of the test data such as
volumes and formats and corresponding output
values.

Manual System Test (MST)

1.

2.

3.
a.
b.
c.

Manual System Test verifies that the overall system

works properly. Both functional and structural type
of tests are performed to verify that the system
performs as intended.
The MST Script document outlines the steps
involved for system testing to ensure all the
modules and code are working in accordance with
the requirements.
The MST test scripts are designed to
confirm intended functionality of the major components.
test integration with other systems(if applicable).
confirm that the changes do not have any unintended
consequences.

The MST execution evidence document is nothing

but the
completed MST scripts(overall script
outcome) with the
corresponding screenshot which
demonstrates the result of executing a step.
4.

User Acceptance Test(UAT)

1. UAT is generally executed by business users.
2. UAT is categorized into the following types;
Functional testing
Relates to testing of system functionality.
User interface testing
Relates to testing of user screens, forms and
windows.
Regression testing
Relates to testing of existing system functionality.
This is to ensure that any new updates did not
upset existing functionality.

Defect Log and Minor Issues Log

1.Defect log is a running log of any defect encountered while
testing.
2. Each defect is a unique number .
3. Defect log is generally completed after all tests are
completed.
4. Defect log is compiled from all the defect forms.
5. Defect log is completed by the test lead or the test
reviewer.
6. Minor issues log contains issues related to testing steps
such as syntax errors, wrong numbering, and spelling
mistakes.

Test Summary Report

1. The Test Summary report is compiled after all testing is
completed, Defect forms/defect logs are filled out and Minor
issues log is completed.
2. The test summary report will summarize the defects by
severity category and how many defects are still open and
how many were closed.
3. The test summary will explain how the defects were
deemed closed. That is, if these were retested and details of
retest.

Test Summary
Report(contd.)
4. Test summary must explain all open defects and
possible solutions on how they would be handled , that is,
if it is acceptable by the business to implement the
system with a work around solution.
5. A system with Open defect with a major category
cannot be implemented until it is resolved.
6. Test Reviewer and Business owner must sign on all
testing documents as well as test summary report.