In-Depth Analysis: Test Scripts, Configurations, and e-CATT in SAP

This document provides a detailed exploration of testing methodologies within SAP environments, focusing on test scripts, test configurations, and the e-CATT automated testing tool. It defines test scripts as preventative measures encompassing data information and test configurations as broader system testing methods. The analysis includes error handling, the differences between manual and automated testing, and the application of test drivers. Parameterization in SAP is explained, detailing import, export, and local parameters. The document further discusses the maintenance of test script versions, the advantages of using e-CATT for automated testing, and a comparative analysis of test scripts and test configurations. It concludes by referencing relevant literature on SAP testing techniques.

Table of Contents
Task 1......................................................................................................................................................1
Task 2......................................................................................................................................................1
Task 3......................................................................................................................................................1
Task 4......................................................................................................................................................2
Task 5......................................................................................................................................................2
Task 6......................................................................................................................................................2
Task 7......................................................................................................................................................2
Task 8......................................................................................................................................................3
Task 9......................................................................................................................................................3
Task 10....................................................................................................................................................3
List of reference.......................................................................................................................................4
Task 1
Kirtkow (2010) defined test scripts as testing platform in SAP aimed at preventing future
problems in the model by encompassing data information. All the steps in the model are tested
and the same test script will be used again should a testing need arise. It possible to create and
maintain different versions of test scripts to scripts with the same functionality and same validity
area but it is not possible to scripts with similar functionality and different validity area.
Task 2
Larab (2011) defined test configuration as a wider method of testing systems and application
underdevelopment with other systems that have varied hardware and software configurations,
test configuration includes a test script, a test and system data containers. It is mainly done to
check compatibility abilities and optimality such that the system can operate without bugs. It is
possible to maintain different version to a test configuration.
Task 3
It shows that there is an error on the screen number and is transportable. The screen number
should be a unique four digit number. The screen number should be edited to start with
transaction codes beginning with a Z or Y letters as its primary transaction code.
1

Task 4
According to Wieczorek (2009), e-CATT is an automatic testing tool in SAP. It a computer
aided testing which is perform important task systematically such checking for authorization and
testing transactions.
 The major difference between manual and automated testing is that the automated testing
is computerized while manual testing is human centered.
 Other minor differences are based on their performance in that manual testing is
inaccurate, slow and that it based on test cases while the automated testing is accurate,
fast and also recurrent.
 They also have different functionality; manual testing is best used for ad-hoc and
exploratory kinds of tests while automated testing is best when testing performance, load
and regression abilities of the system.
Task 5
 Test drivers are special snippets of codes that are used to call other modules. It is aimed
at checking the functionality of modules which are interdependent. For instance, test
drivers will be used to call module Z when one has to pass through A-Z systematically. A
successfully call of module Z shows that the system is okay. TCD test drivers have been
used in the tutorial.
 SAPGUI test drivers could also have been used.
Task 6
 Kurbel (2013) defined Parameterization is the use interfaces which are visible both
internally and externally by variables in script which can take at least thirty characters. It
is useful in transaction recording to minimize potential errors and also to enable
reusability of the recording.
 There are three types of parameters available; import parameter which inputs values to
the script editor, export which outputs values from the script editor and local parameters
which are used in the script editor for calculations and to input output values.
 Import and export variables parameters are used in the tutorial done.
Task 7
 We can maintain varied versions of a test script when there is a potential of the system
implementations varying from time to time. This is to allow user to use only a specific
script for a transaction despites its dynamic nature.
 Also developing and maintaining different version of scripts best fits scripts with same
functionality but different implementation for each validity point.
2

Task 8
I would use an automated tool specifically eCATT to test system and application on SAP
simply because it is fast in execution which saves time, the executions done are of a higher
quality and it is a data driven system fitted to modify test report.
Task 9
According to Wieczorek (2009), eCATT is advantageous because
 Is it fast hence saves times that could have been spent on loading and execution of
transaction and testing.
 Since eCATT is automatic, it is efficient and effective in processing of transactions
execution. This would result in a no error situation or minimized error condition.
 Also due to automation, manually testing of algorithms, modules and transaction is
erased and thereby also reducing the manpower. This saves money
 In regression testing automatic testing have proven better than the manual testing since it
has the ability to conduct recurrent testing on variables and transaction.
Task 10
Test script and test configuration are almost the same in SAP since both are types of testing.
However configuration testing is much wider than test scripts. Test scripts are testing platform in
SAP aimed at preventing future problems in the model by encompassing data information while
test configuration is a method of testing systems and application underdevelopment with other
systems that have varied hardware and software configurations, test configuration includes a test
script, a test and system data containers.
3

List of reference
Kirtkow, S., Kohler, M. and Schwab, H., SAP SE, 2010. Techniques for generating a reusable
test script for a multiple user performance test.
Kurbel, K. and Nowak, D., 2013. Customization of on-demand ERP software using SAP
business ByDesign as an example. In Innovation and Future of Enterprise Information
Systems (pp. 289-297). Springer, Berlin, Heidelberg.
Larab, B.A., Arteaga, H.A., Solis, O.F., Riojas, G.E., Cuandon, M.A., Horton, R.C., Chiou, M.K.
and Paladin, V.A., SAP SE, 2011. System and method for generating business process test
elements.
Wieczorek, S., Stefanescu, A. and Schieferdecker, I., 2009, September. Model-based integration
testing of enterprise services. In 2009 Testing: Academic and Industrial Conference-Practice and
Research Techniques (pp. 56-60). IEEE.
4