Tuesday, February 1, 2011

Differences between CATT and eCATT

Till date, CATT could only be used with the R/3 system. eCATT (which is available with SAP Web Application Server 6.20) covers the automatic testing in SAPGUI for Windows and SAP GUI for Java. For other GUIs and Applications, eCATT provides an interface for external tools. This allows companies to perform automated tests from an SAP system in a complete IT solution landscape across system boundaries. These new options enable complete automation of solution landscapes under standard Windows and Web-based user interfaces- resulting in low-cost operation of an IT Solution.

You might also be interested in:

What is eCATT?

eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.

eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.

Features of eCATT:

Following functions can be performed using eCATT:

  • Test transactions, reports and scenarios.

  • Call BAPIs and function modules.

  • Test remote systems.

  • Check authorizations (user profiles).

  • Test updates (database, applications, GUI).

  • Set up customizing tables.

  • Test the effect of changes to customizing settings.

  • Perform load testing.

  • Check system messages.

  • Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.

  • Supports CATT migration to eCATT.

  • All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.

  • eCATT Objects can easily download & upload in XML with XSD format.

  • There can be several versions of Test Scripts, which allows different implementations with different releases.

  • The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.

Why eCATT?

CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:

  • Due to automation, testing time is reduced to a large extent.

  • Due to automation, less manpower is required for testing. This helps financially.

  • Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.

  • Proved to be extremely useful in implementation projects.

In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.

eCATT requisites

  • Web Application Server (WAS) 6.20 or more.

  • SAPGUI 6.20 or more.

  • R/3 4.6C or more. (Target system must have sufficient support package level (Details available in SAP Note 519858) or SAP R/3 Enterprise Release 4.7).

Before creating Test Scripts using eCATT, some system settings need to be done:

Maintain table T000.

1. Go to transaction SM31

2. Enter T000 and chose MAINTAIN.

3. In the Change View “Clients”: Overview screen, select the relevant client and choose “Details”

4. In the “CATT and eCATT Restrictions” field, select “CATT and eCATT allowed”.

5. Click on SAVE.

Enabling scripting at the Front-end

1. On any SAP GUI screen, choose “Customizing of Local Layout”.

2. Choose Options

3. Choose “Scripting Tab”

4. Select “Enable Scripting”

5. Click Apply and then OK.

Enabling Scripting on the Application Server

1. Go to transaction RZ11.

2. On the Maintain Profile Parameters screen, enter sapgui/user_scripting.

3. Choose Display.

4. If the Current Value is not set to TRUE, then click on Change Value:

5. Enter TRUE in the “New Value”.

6. Click on SAVE.

No comments:

Tutorials on SAP-ABAP

Adobe Interactive Forms Tutorials

Business Server Pages (BSP)

Userexits/BADIs

Web Dynpro for ABAP (Step by step procedure for web dynpro,Tutorials on Web Dynpro,)

ALV Tutorials

Blog Archive

goodsites