Since its introduction in R/3 3.0, SAP customers have come to rely on the Computer Aided Test Tool (CATT) to test their centralized SAP installations and standard UIs. Testing distributed systems, controls-based UIs, and web applications, which are now commonplace in most installations, is a different story. To support these developments, SAP released the extended Computer Aided Test Tool (eCATT) as part of SAP Web Application Server 6.20. But what about all your existing CATT test procedures and modules? This article shows you how to safeguard your current CATT investment and leverage eCATT’s new capabilities by migrating your CATT objects to the new eCATT environment, leaving your CATT objects as-is in 4.6C and calling them remotely from eCATT, or doing both.
Jonathan Maidstone
Jonathan Maidstone is a Product Manager within the SAP NetWeaver organization with overall responsibility for test tools. After graduating from the University of Bristol (UK) in 1996 with a degree in modern languages, he joined SAP as a translator for the ABAP Language and ABAP Workbench departments. His association with the eCATT team began in 2001, following a spell as a technical writer working on the SAP Control Framework and DCOM Connector projects.
You may contact the author at
jonathan.maidstone@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the
editor.
