Version 1.

Instructions
VIT has To 1. Fill in the general description.

2. Choose what level of testing you plan to do on the Test Plan tab. Unit testing is man
mandatory to do both Integration and System testing, but one of them must be perform
Acceptance test is recommended but not mandatory if it is not applicable. Concerning
Acceptance test. Depending on the complexity and risk of the change, this work is rec
done in co-operation with the System Owner or a by him/her appointed person.

3. Fill in planned date for testing, name of tester and types of testing to be performed.
mandatory. See the list below for definitions on different test types.
5. Create the test cases for the tests that should be performed, also enter your name a
which system the test is performed.

6. When a test is performed, fill in the name of the tester, test date and enter the Test R
appropriate sheets. If the test was not OK, enter the corrective action.

System owner 4. Verify and that the proposal for whether Customer Acceptance test should be done
Has To sheet "Level Of testing"). SO must also approve the proposed test plan in this step.
7. Perform Customer Acceptance test or verify that the tests have been performed and
documented

Definitions
Levels of Testing
Involves execution of the unit test cases to evaluate implemented subprogram unit
and resolving unit-level errors. This is accomplished as subprogram units are devel
Unit Testing: they are integrated into larger components and programs units.
It should be performed in development system by the Developer.
Level of Scopetesting,
In integration : 1 Action, 1 single
the units item during unit testing are combined into succ
validated
components and programs and are tested. This is accomplished as subprogram un
Integration Testing: such that integration testing extends (at least) through the coding phase.
It should be performed in Q&A system by Maintenance Team Tester
Testing
Level of that attempts
Scope: to discover
1 Building Block defects
, severalthat are properties
or combined itemsof the entire system rat
individual components.
System Testing:
It should be performed in the Q&A system by Maintenance Team Tester
Level of Scope : 1 full test script
Formal testing conducted to determine whether a system satisfies its acceptance cr
enable the customer to determine whether to accept the system.
Acceptance Testing: It should be performed in the Q&A system, by a Business person. If it is not possibl
explain why.
Level of Scope : Building Block , several or combined items or Full test Script

Test Types
Functional test: Tests focused on validating the target-of-test functions as intended, providing the re
methods, or use cases. This test is implemented and executed against different tes
units, integrated units, applications, and systems.
Regression test: Similar in scope to a functional test, a regression test allows a consistent, repeatab
each new release of a product. Such testing ensures reported product defects have
for each new release and that no new quality problems were introduced in the main
Security test: Though regression
Tests focused testing can
on ensuring be performeddata
the target-of-test manually an automated
(or systems) test suiteonly
are accessible is oft
which they are intended. This test is implemented and executed on various test leve
Volume test: Testing focused on verifying the target-of-test's ability to handle large amounts of d
and output or resident within the database. Volume testing includes test strategies
queries that would return the entire contents of the database, or that would have so
that no data is returned, or where the data entry has the maximum amount of da

Integrity test:
Data and Database Integrity test:
Testing focused on verifying the target-of-test's ability to handle large amounts of d
and output or resident within the database. Volume testing includes test strategies
queries that would return the entire contents of the database, or that would have so
that no data is returned, or where the data entry has the maximum amount of da
Tests that focus on assessing the target-of-test's robustness (resistance to failure),
compliance to language, syntax, and resource usage. This test is implemented and
different test levels, including units and integrated units.
Tests that ensure database access methods and processes function properly and w
corruption.

Structure test: Tests that focus on assessing the target-of-test's adherence to its design and forma
this test is done for Web-enabled applications ensuring that all links are connected,
content is displayed, and no content is orphaned.
Stress test: A type of reliability test that focuses on evaluating how the system responds under
conditions. Stresses on the system could include extreme workloads, insufficient m
services and hardware, or limited shared resources. These tests are often performe
understanding of how and in what areas the system will break, so that contingency
upgrade maintenance can be planned and budgeted for well in advance.
Failover and Recovery test: Test that ensure that the target-of-test can successfully failover and recover from a
hardware, software or network malfunctions with undue loss of data or data integrity

Usability test: Tests that focus on:

• human factors
• esthetics
• consistency in the user interface
• online and context-sensitive help
• wizards and agents
• user documentation
• training materials

Benchmark test:
Contention test:
Load test:
Performance profile:
Maintainability Compliance test:
Configuration test:
Installation test:
A type of performance test that compares the performance of a new or unknown ta
known reference-workload and system.
Tests focused on validating the target-of-test's ability to acceptably handle multiple
the same resource (data records, memory, and so on).
A type of performance test used to validate and assess acceptability of the operatio
system under varying workloads while the system-under-test remains constant. In s
workload remains constant and the configuration of the system-under-test is varied
are usually taken based on the workload throughput and in-line transaction respons
variations in workload usually include emulation of average and peak workloads tha
normal operational tolerances.
A test in which the target-of-test's timing profile is monitored, including execution flo
function and system calls to identify and address both performance bottlenecks and
processes.
Tests focused on evaluating by an independent group the application can be maint
Tests focused on ensuring the target-of-test functions as intended on different hard
configurations. This test might also be implemented as a system performance test.
Tests focused on ensuring the target-of-test installs as intended on different hardwa
configurations, and under different conditions (such as insufficient disk space or po
This test is implemented and executed against applications and systems.

Functional
Regression
Security
Volume
Integrity
Data and Database Integrity
Structure
Stress
Failover and Recovery
Usability
Benchmark
Contention
Load
Performance profile
Maintainability Compliance
Configuration
Installation
 Performed when SolMan
request IS in status:

Plan tab. Unit testing is mandatory. It is not

one of them must be performed. Customer
s not applicable. Concerning the Customer Bus. Impact Approved
the change, this work is recommended to be
her appointed person.

s of testing to be performed. Functional test is

est types.
med, also enter your name as author and in Created

In Development
est date and enter the Test Result in the & To Be Tested
ctive action. & Successful IT-test

eptance test should be done or not is OK (see

osed test plan in this step. Proposal Created
sts have been performed and are properly
Successful IT-test

plemented subprogram units, and tracking

subprogram units are developed, and before
ms units.
eveloper.
ting are combined into successively larger
mplished as subprogram units are developed,
he coding phase.
Team Tester
rties
itemsof the entire system rather than of its

nce Team Tester

m satisfies its acceptance criteria and to

e system.
ss person. If it is not possible to perform,

ems or Full test Script

as intended, providing the required services,

ecuted against different test levels, including

ows a consistent, repeatable validation of

ported product defects have been corrected
were introduced in the maintenance process.
an automated
stems) test suiteonly
are accessible is often usedactors
to those to for
xecuted on various test levels.
o handle large amounts of data, either as input
sting includes test strategies such as creating
abase, or that would have so many restrictions
the maximum amount of data for each field
 ness (resistance to failure), and technical
his test is implemented and executed against

sses function properly and without data

ence to its design and formation. Typically,

that all links are connected, appropriate

he system responds under abnormal

me workloads, insufficient memory, unavailable
ese tests are often performed to gain a better
break, so that contingency plans and
well in advance.
failover and recover from a variety of
loss of data or data integrity.

nce of a new or unknown target-of-test to a

acceptably handle multiple actor demands on

acceptability of the operational limits of a

r-test remains constant. In some variants, the
system-under-test is varied. Measurements
d in-line transaction response time. The
age and peak workloads that occur within

ored, including execution flow, data access,

erformance bottlenecks and inefficient

he application can be maintained

s intended on different hardware and software
a system performance test.
ntended on different hardware and software
nsufficient disk space or power interruptions).
ons and systems.
 GENERAL DESCRIPTION
Solution Manager
TASK000134618-SCORE/GTT/SG07/Score vs MF/Issue with Score hours in SAP MF
number:

SAP R/3
Application:

FP2-105
Component name:

FA
Business process:
To be
Performed Number
Levels of Testing (Y/N) If N, please explain why Date Name of tester Test Type(s) of tests
Unit Testing Mandatory Sathish Functional 0

Integration Testing Functional 0

At least one of these

test types must be
performed
System Testing Test team Functional 0

Customer Acceptance (CA) Damien Functional 0

Testing.
 UNIT TEST
Author : Sathish
System: FD2 Client: 105

TEST RESULT
Tester Name : Sathish

Observed
Anomalies/defects
and Requested
update:

TEST CASE TEMPLATE 0

Detail description:
Purpose Test Test steps Expected results Run date Test result OK/ Corrective
Type Not OK action
SK01 update table Functional By using SM30 Tcode we can the table Translation table of
ZFGDS_STCEG ZFGDS_STCEG. VAT Codes between
GDS and SAP will be
updated.
 INTEGRATION TEST
Author :
System: Client: 105

TEST RESULT
Tester Name : 0

Observed
Anomalies/defects
and Requested
update:

TEST CASE TEMPLATE 0

Detail description:
Purpose Test Test steps Expected results Run date Test result OK/ Corrective
Type Not OK action
Functional
 SYSTEM TEST
Author : Sathish
System: FQ2 Client: 105

TEST RESULT
Tester Name : Test team

Observed
Anomalies/defects
and Requested
update:

TEST CASE TEMPLATE 0

Detail description:
Purpose Test Test steps Expected results Run date Test result OK/ Corrective
Type Not OK action
SK01 update table Functional By using SM30 Tcode we can the table Translation table of
ZFGDS_STCEG ZFGDS_STCEG. VAT Codes between
GDS and SAP will be
updated.
 CUSTOMER ACCEPTANCE TEST
Author : Damien
System: FQ2 Client: 105

TEST RESULT
Tester Name : Damien

Observed
Anomalies/defects
and Requested
update:

TEST CASE TEMPLATE 0

Detail description:
Purpose Test Test steps Expected results Run date Test result OK/ Corrective
Type Not OK action
SK01 update table Functional By using SM30 Tcode we can the table Translation table of
ZFGDS_STCEG ZFGDS_STCEG. VAT Codes between
GDS and SAP will be
updated.
 Review (Master Finance)
Transport request Reviewed OK by Date After Office Hours