Sap Network Blog_ Ecatt Logs (Part Vi

7/23/2019 Sap Network Blog_ Ecatt Logs (Part Vi

1/8

Subscribe

Print

Permalink

Share

Blogs

eCATT Logs (PART VI)Sapna Modi

Business Card

Company: Larsen &Toubro Infotech Ltd.

Posted on Apr. 18, 2006 08:18 PM in Emerging Technologies,Application Server

The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. In Part II, the creation of

eCATT scripts using TCD mode of recording is explained in detail. In Part III, SAPGUI recording mode of recording is explained in

detail. In Part IV chaining, parameterization, creation of Test Configuration, Test Data Container, and System Data Container are

explained in detail. In Part V, the management of eCATT Scripts via Testworkbench is explained. In Part VI, the eCATT Logs will be

explained in detail & in the subsequent parts other details of eCATT will be covered.

What Are eCATT Logs:

eCATT Logs are generated every time a test script or test configuration is executed either by SECATT or SCAT transaction.

The log is hierarchically structured according to the test script used, and displayed as a structure with nodes. Each test script inturn may contain one or many recorded transactions. This also includes any inline ABAP code or any other eCATT commands ifused.

Each of the eCATT log shows the execution status of each of the step executed for the given test script along with necessarydetails like unique log ID, executed variants details, Import/Export/Local parameters details, Target System details, Source Systemdetails, Test Data container, time taken for each step of automated steps as well as total execution time in seconds, executionmode like With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption (Background forTCD & without user intervention for SAPGUI) etc.

Advantages Of eCATT Logs:

eCATT log stores all the steps of the test case along with lots of other useful information about systems, variants etc.

These logs help in analysis of the business process. As all the system messages are stored in the logs, which are generated duringexecution of the given script, it becomes simple to analyze the result set.

The expiry date of logs can be changed. So they can be maintained for the defined time frame. And hence the results of oneregression testing can be used as reference for next regression testing. This helps in rollout projects.

In case of errors, system prompts the relevant messages, which help in understanding of the process that has gone wrong. Afternecessary corrections, the script can be again executed and the new log will be generated. The success, error or execution status isdepicted by colors in logs. So it becomes much more user friendly to analyze.

How To Look In eCATT Log From Log ID:

P Network Blog: eCATT Logs (PART VI) http://weblogs.sdn.sap.com/pub/wlg/3489

8 08/07/2011 21:33


2/8

Transaction SECATT.

Click on Logs (Ctrl+F12)icon from the application toolbar.

Under the Log Selectionsection, in Currt. Procedure No.Input field give the log ID.

Remove the values from the Starter & Start date input fields. They are not necessary in this case, as Log ID is known. In case logID is not known & one wants to analyze all the logs generated on a particular date by a particular tester then give these inputfields. Other input fields include Test Configuration, Test Script, Expiry date, which in this case are not mandatory. Different inputcombinations can be made for eCATT logs depending on what kind of input is in hand. In absence of eCATT Log ID, thecombination of other input fields becomes useful.

Click on Execute (F8)button.

eCATT Log with the Log ID in title appears in next window. By click on Expand All Nodes (F5)button, all the nodes will be drilleddown till end. And the detailed view of log will be displayed.

How To Look Into eCATT Logs From Test Workbench:

With the assumption that test package is executed, logs from test package will be analyzed here.

Transaction SCAT.

Menu Environment -> Manage Test Plan.

Give the name of test plan. Click on Status Analysisbutton from the application toolbar.

The execution status of the package is in terms of traffic lights under the Statuscolumn with description under Status Textcolumn.


8 08/07/2011 21:33


3/8

Click on the traffic light of the required test configuration. After click, Status Maintenancewindow appears. This window containsTest Case details, Status of execution etc. Click on Log (Shift+F1)button from the application toolbar.

Detailed eCATT Log is displayed against that test configuration with unique log ID.

Analysis Of eCATT Logs:

Top Level Information: The first line of the log displays the log identification number. Depending on the tests, other information isalso displayed:

The number of test configurations executed. (This information appears if the execution happens from the test workbench viaSCAT).


8 08/07/2011 21:33


4/8

The name of the test script or test configuration executed via SECATT.

The version number of the test script.

The execution mode i.e. With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption(Background for TCD & without user intervention for SAPGUI) .

After the top line following information is displayed in one line: System, Client, User, Language, Release, ApplicationServer,Operating System, Database System, Date of exeuction, Time of execution.

Script Details:After the detailed systems information, the test script details like test script name, version, description & execution time taken bythe complete script is displayed in seconds. The system Data Container as well as Test Data container are also displayed. Thestatus of execution of scripts is depicted by colors either green background color for success or red background color for error.

Successful Script

Script in Error

Maintenance System:If a test script has a maintenance system, the RFC destination is displayed and the detailed component information is shown belowit.

Comments, Duration, IF-ENDIF structure:To display comments, duration time in seconds in the log, click on Settings(Shift+F7)icon from the application toolbar. Select thecheck boxes of Disp. Duration, Display Comments. Press Enter.

The log with the comments, duration time will be displayed. If the IF-ENDIF structure is executed, it is displayed with green color


8 08/07/2011 21:33


5/8

otherwise not.

Errors, Multiple Variants, Messages, Navigation:

Error: If a script contains one or more errors, it is in error with background red color. If a node is marked as containing anerror, the node above it in the hierarchy is also marked as containing an error with red color. Error message is immediatelydisplayed after that step and even after the script details.

Messages: Messages during the execution are displayed in the log under messages node. Messages can also be seen in XMLdata.

Multiple Variants: Script can be executed using multiple variants. The variant names appear one after the other in the log.

Navigation: By clicking on the hyperlinks from the log, one can navigate to the test script, system data or test data etc. When arecorded transaction uses a print function that sends a document to the spool, a message is recorded in the log.

XML Data:XML data is generated when testing function modules and transactions. To view XML data, click the hyperlink name of the XML

data in the log.

Here is an extract of XML-DATA-01 from the log shown above.


8 08/07/2011 21:33


6/8

How To Change Expiry Dates/Deletion/Archiving Of eCATT Logs:

Transaction SECATT.Click on Logs (Ctrl+F12)icon from the application toolbar.

Under the Log Selectionsection, in Currt. Procedure No.Input field give the log IDs by clicking on the Multiple Selectionbutton.Multiple Selections For Currt. Procedure No.window appears. The entire log IDs should be given here. Click on Execute (F8)button.

On the Log Selectionwindow, the multiple selection button will show green status for having multiple values of Log Ids. Click onExecute (F8)button.

Logs from the selection screen are displayed in the tabular format with the details like status, start date, end date, starter, expirydate, test script, test configuration etc.

Select all the logs by clicking on Select Allicon on left top of the grid. Click on Change Expiry Date (Ctrl+F8)button from theapplication toolbar.

Date changewindow appears. Set the required expiry dates to the logs. Click on Enter. The Expiry date will change for the all theselected logs to this new value.


8 08/07/2011 21:33


7/8

When the expiry date reaches for any log, the log is automatically deleted. If the automatic deletion is not required, explicitly alsothe log can be deleted from the menu Log Selection->Delete (Shift+F2).

Also the logs can be archived. Select the log from the list, from the menu Log Selection -> Archiving On/Off (Ctrl+F7).

How To Find Database Tables For eCATT Logs:

Transaction SARA.

In the Object Nameinput field give value ECATT_LOG.

Click on Database Tablesbutton from the application toolbar.

On the Tables & Archiving Objectswindow, in the Tables from which data is archivedsection, tables are displayed for eCATT Log.These are the tables in which the log is stored in the database. Select the All Tablesradio button.

Sapna Modi is a Software Engineer.

eCATT - Future Of Testing

Comment on this weblog

Showing messages 1 through 1 of 1.

Titles Only Main Topics Oldest First

A small change

2009-05-18 04:43:21 Rajendra Nagisetty Business Card[Reply]

Every blog u had given is clear but if it can be mentioned in particular way that even a functional guy can also understand, for each

application.


8 08/07/2011 21:33


8/8

as per the links u mentioned little bit confusion is there that which particular link can be reffere at which point.

if u upload the details in such a way that if this is an error then the solution is this.

that would be help ful for all.

Regards

R

Showing messages 1 through 1 of 1.


Documents

Sap Network Blog_ Ecatt Logs (Part Vi