Sei sulla pagina 1di 7

SAP Testing Strategy

387847188.doc Praktiker - SAP Competence Page 1 of 7 22-May-


Center 2018
Document Control

Author Bogdan Cotirta - Praktiker SAP Competence Center, Praktiker Group


File Name 387847188.doc
Path
Created 2010/08/03
Last Edited 8/3/2010 09:36:00 AM
Number of Pages 7

Version Revision Date Revision Description Author Sign-off


1.1 2010/08/03 Version created base on the Bogdan Cotirta
extras from the other
documents

Target Readership

Project Team Members

Table of Contents

387847188.doc Praktiker - SAP Competence Page 2 of 7 22-May-


Center 2018
1 PURPOSE...................................................................................................................................................4

2 TESTING STRATEGY / PLAN..............................................................................................................5


2.1 TESTING PREPARATION........................................................................................................................5
2.1.1 Unit Testing.................................................................................................................................5
2.1.2 Integration Testing......................................................................................................................5
2.1.3 User Acceptance Testing.............................................................................................................6
2.1.4 System Testing.............................................................................................................................6
2.1.5 Security Testing...........................................................................................................................7
2.1.6 Regression Testing......................................................................................................................7
2.2 TEST CERTIFICATION...........................................................................................................................7
2.3 PROBLEM LOGGING.............................................................................................................................7
2.4 Error Correction..................................................................................................................................7

387847188.doc Praktiker - SAP Competence Page 3 of 7 22-May-


Center 2018
1 Purpose

This section describes the Test Strategy for the SAP projects.

This document represents the repository of all the important Praktiker strategies and decision
regarding this project.

387847188.doc Praktiker - SAP Competence Page 4 of 7 22-May-


Center 2018
2 Testing Strategy / Plan

The success of a good implementation is dependent on the testing and problem resolution process
adopted. The system cutover is also a key factor in the Acceptance Test process. A t esting
protocol for each test will be drawn up according to the testing plan of the
system.

Several types of testing activities will be employed to confirm that the configured business
processes meet design requirements and that the technical environment is prepared for
production. These different types of tests are performed to address the integrated nature of the
system and to cover all aspects of system configuration and development.

The customer staff will be fully involved in the Testing Phases and will assist Implementation Team
in providing test data, test scenarios and validation of test results.

The system areas relevant for testing are:


 Configured business processes;
 Development objects, including user exits, conversions, interfaces, forms, reports, and other
enhancements;
 Technical system components, including hardware, connectivity, and system administrative
support processes (such as backup and recovery and transport tools).

2.1 Testing Preparation


Testing preparation involves planning, the creation of test scripts and the creation of test data. The
templates for the test scripts are available in the project folder directory and will be provided to the
customer Key Users by the implementation team.

Test Implementation Customer


scripts and Team Team
Test Data
Lead Assist Lead Assist
Unit X X
Integration X X
User Acceptance X X
System X X
Security X X
Regression X X

1 Unit Testing
The purpose of the unit testing activity is to verify that the system’s components are functioning as
expected and to confirm that no errors exist. Unit testing is typically the first test performed during
the configuration and development efforts. Unit testing focuses on self-contained functions rather
than integration. Unit testing for both configuration and development objects is performed in a
development environment using a small subset of representative data. Some string testing may
also be performed before integration testing if this is deemed necessary.

2 Integration Testing
Integration testing focuses on cross-functional integration points, as well as end-to-end business
processes. A well-defined integration test plan starts with the testing of the cross-functional
integration points (touch points) and ends with the end-to-end testing of critical business processes
identified within the Business Blueprint. Integration testing should also include testing the
organizational flow, i.e. how the several organizational units are involved in one process, how they

387847188.doc Praktiker - SAP Competence Page 5 of 7 22-May-


Center 2018
communicate, how the information and document transfer is handled. Including personnel from all
functional areas involved in the process may accomplish this.

Development Testing. Unit interface/ forms/ reports/ enhancement testing will be performed in the
development environment. All the required data conversion programs need to be written and tested
prior to going live. Testing will be performed in the development environment. Data will be
required from the existing legacy systems. A reconciliation process will follow to verify balances,
derived fields and other values. The technical team and ABAP programmers will be responsible for
running the data conversion testing.

3 User Acceptance Testing


Integration testing provides the environment for User Acceptance testing. User Acceptance testing
ensures that designed processes and functions meet the stated requirements and that the system
will support the requirements (functional, system, and information requirements). The user
acceptance process also involves a test certification process where the business processes are
signed off as meeting the requirements of the customer staff in ensuring that the functionality is
met and data integrity across the enterprise is maintained.

Key users should be involved with the integration testing as well as the user acceptance test. The
Project Managers will determine the number of extended team members or other end users that
need to be involved with testing.

User acceptance test results are documented on the test scripts, and these documents compose
the user acceptance test results. All problems encountered during testing are documented and
tracked to resolution. The compilation of these problems and the associated resolutions make up
the user acceptance test software problem log.

4 System Testing
System testing consists of technical tests and performance related tests. The technical tests aim to
validate that the technical components of the production environment are working properly. These
tests include validating the system administration procedures, failure recovery, and disaster
recovery. The performance related tests include volume and stress testing of business transactions
and business transaction input / output using printer and fax devices.

Technical Test
 Failure Test
 Disaster Recovery Test
 Backup and Restore Test
 System Administration Test
 Printing and Fax Test
 Go-Live Check

Performance Test
 Volume Test
 Stress Test
 Batch cycle test
 Month/quarter/year end processing

Technical tests are basis oriented, whereas performance tests cover basis and application aspects.
Performance tests should concentrate on stress test, i.e. stressing the system with all components
involved in certain scenarios until it performs to predefined values (throughput). Volume testing is
needed for some processes or transactions, if the throughput of one orders, daily interfaces, etc.)

387847188.doc Praktiker - SAP Competence Page 6 of 7 22-May-


Center 2018
5 Security Testing
Security testing involves cross functional testing of user roles created for the user groups to
perform various functions. The testing is focused on verifying that the necessary access to
screens, data and reports is available for each of the user roles defined in the system.

6 Regression Testing
Regression testing will be planned and conducted as necessary to verify that changes made to the
system or technical environment have not adversely affected the functionality of the system (non-
change testing). The need to perform this testing activity becomes more likely and larger in scope
as these types of changes are made in the later stages of the project. The scope of testing will
depend on the impact of the changes precipitating the regression test. Regression testing may be
conducted to perform:
 Support pack upgrades
 Development and configuration changes made after functional testing activities have been
completed

The activities and deliverables for regression testing will be determined based on the size and
scope of the regression test.

2.2 Test Certification


Test certification occurs after the completion of the User Acceptance testing. It would indicate the
enterprise readiness of the system in meeting its desired functionality. Sign-offs are also initiated at
each testing phase and packaged with the User acceptance testing to form the test certification
package.

2.3 Problem Logging

All errors or deviations from expected results will be documented and the normal issue resolution
procedure will be followed.

2.4 Error Correction

The results of error correction can have one of the following effects:

1. Scope Change: These will be documented according to the Change Management


Procedure.

2. Business Process change: These will be documented and communicated to the relevant
parties.

387847188.doc Praktiker - SAP Competence Page 7 of 7 22-May-


Center 2018