eCATT

jason_au — Wed, 14 Aug 2013 00:22:57 GMT

My question is really a clarification/confirmation around the eCATT tool. My client is looking for something official in regards to:

There are two scripting options available for recording eCATT scripts: SAPGUI and TCD. TCD is faster than SAPGUI. SAPGUI must be used on the “enjoy” controls functions in SAP as TCD has an issue with these items. TCD can be run in background mode where SAPGUI is run in foreground. Is there an SAP official recommendation on when to use SAPGUI over TCD and the limitations associated to each type?
One of SAP's partners at my client said SAPGUI has less issues at the time of upgrades than TCD recordings. I am trying to determine if this is really the case. We had TCD recordings that had to be “re-recorded” at the time of our upgrade to EHP6. However, not all TCD
recordings had to be re-recorded. (Note at this time we did not have any SAPGUI recordings.) My thought was that this seemed more of an issue with the new SAPGUI log on as we upgraded that as well, rather than TCD scripts being broken due to EHP6. We are trying to determine something official on this as well.

Thanks,

Jason Au

Re: eCATT

AjayHS — Mon, 19 Aug 2013 17:23:23 GMT

There
are two scripting options available for recording eCATT scripts: SAPGUI and
TCD. TCD is faster than SAPGUI. SAPGUI must be used on the “enjoy” controls
functions in SAP as TCD has an issue with these items. TCD can be run in
background mode where SAPGUI is run in foreground. Is there an SAP official
recommendation on when to use SAPGUI over TCD and the limitations associated to
each type?

As you rightly mentioned
eCATT has different drivers (commands) like TCD, SAPGUI, FUN etc., each
specialized for a particular task. With new SAP technologies like Web Dynpro
etc new drivers are created to enable automation of application based on these
technologies. Following flow chart helps to determine most appropriate driver
to be used to automate.

To summarize if the
SAPGUI screens are control intensive (Enjoy transactions) then please use SAPGUI,
else for conventional transactions use of TCD driver is recommended.

Note: No single driver provides the best solution for every
application, several drivers can be used within the same script.

One
of SAP's partners at my client said SAPGUI has less issues at the time of
upgrades than TCD recordings. I am trying to determine if this is really the
case. We had TCD recordings that had to be “re-recorded” at the time of our
upgrade to EHP6. However, not all TCD recordings had to be re-recorded. (Note
at this time we did not have any SAPGUI recordings.) My thought was that this
seemed more of an issue with the new SAPGUI log on as we upgraded that as well,
rather than TCD scripts being broken due to EHP6. We are trying to determine
something official on this as well.

Test Script will not
normally fail whether its recorded using TCD or SAPGUI as long as
the GUI element id’s of the controls are intact to what was during the
recording of automated script and the expected control objected is available on
the screen where the execution control is at the runtime. I feel the change in
GUI element id’s of the recorded control object has resulted in the failure of
the script.

topic Re: eCATT in Application Development and Automation Discussions

eCATT

Re: eCATT