Testing

Purpose
During the entire life cycle of a SAP solution, it is necessary to test the functions and performance of your solution. With the SAP Test Workbench, SAP provides you with an environment for all test phases, which you can use for testing in the following cases: Implementation of SAP solutions Integration of new components and business scenarios Customer developments Function tests Integration tests with other components Upgrades, regression tests Importing support packages

Integration
The SAP test tools Test Workbench, Extended Computer Aided Test Tool, and Test Tool are part of the SAP Web Application Server. Computer Aided

Features
Test Preparation
Creation of manual and automated test cases Management of manual and automated test cases Creation of test plans Definition and management of test series Execution of mass tests using Extended Computer-Aided Test Tool and Computer Aided Test Tool Integration of test cases and test scripts of non-SAP providers Assignment of worklists (test packages) to individual testers Permanent overview of test progress and test results Complete documentation of test processes in the test plans (test cases, test case descriptions, test results, test case notes, error messages) Detailed tabular and graphical evaluation of all test plans Export of test results to Office applications Message processing

Test Execution

Test Evaluation

The R/3 System Test Workbench

The Test Workbench organizes and manages R/3 System tests. The following graphic illustrates the components of the Test Workbench:

A Test catalog is a set of test cases plus additional information in a hypertext structure. The structure is based on the Business Navigator component or process view. A Test plan is a view of a test catalog. It contains all test cases which are needed at a particular time for a particular purpose. A Test package is a person and period-oriented view of a test plan. It contains all tests which a tester is to perform in a specified period. A Test case is a testable part of the SAP System. It is often a business process or process chain.

eCATT: extended Computer Aided Test Tool (BC-TWB-TSTECA)

Purpose
Use extended Computer Aided Test Tool (eCATT) to create and execute functional tests for software. The primary aim is the automatic testing of SAP business processes. Each test generates a detailed log that documents the test process and results. eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java. In order to offer a complete test solution that covers other GUIs, eCATT has interfaces to third party tools.

Implementation Considerations
Test cases usually make database changes. Therefore, you should not normally run them in productive systems.

In general, do not use eCATT to manipulate data in a productive system: eCATT is a test tool. Instead, use techniques such as Batch Input.

Integration
eCATT can be used with the Test Workbench. You can migrate test cases from Computer Aided Test Tool (CATT) to take advantage of the better features of eCATT. eCATT is also integrated with the Object Navigator (SE80).

Features
You can: Test transactions, reports, and scenarios Call BAPIs and function modules Test remote systems Check authorizations (user profiles) Test updates (database, applications, GUI) Test the effect of changes to customizing settings Check system messages

Constraints
eCATT runs in a system based on SAP Web Application Server 6.20 or higher. However, you can use this system to test systems with Release 4.6C or higher.

Tutorial
You can find a step by step introduction to eCATT in the eCATT Tutorial.

CATT: Computer Aided Test Tool (BC-CAT-TOL)

With Web Application Server Release 6.40, you cannot create new automated CATT test cases. However, you can still create manual CATT test cases. Editing and executing existing automated CATT test cases is still possible. CATT has been superceded by eCATT.

Use
The Test Workbench contains the Computer Aided Test Tool (CATT) to create automatic test cases. Automatic test cases are performed by the SAP system without user dialog, and are most useful for function tests. The result of an automatic test case is a detailed log which documents the test. The use of automatic tests can considerably reduce the test effort. Test cases test individual transactions or whole business transactions.

Integration
The enhanced CATT maintenance mode provides additional test functionality. This mode is intended above all for experienced test creators.

Functions
The transaction test case is recorded with a transaction recorder for the test module. You run the application as in normal dialog operation. You go to a test case editor after the recording. You can make test cases flexible by subsequently defining test case variants. You can pass the results of transactions in a business transaction to subsequent transactions. The chain function does this. You can also define transaction result checks. The results can be in screen fields or system messages.