Elements of an eCATT Log

An eCATT log consists of the following elements:

  • Header record

    • Caller data

    • Start options
    • Log blocks

      • Log lines

        • Data lines

        • XML

        • Messages
    • Error list

Header Record

The header record of a log contains general data for running the test, for example:

  • Log number

  • Description
  • Status (e.g. successful, with errors)
  • Start and end date and time
  • Number of test cases contained (for example, total, successful, with errors)
  • Expiration date
  • Archiving flag

Caller Information

This section contains information about the call sequence of a test run. Examples of this are:

  • Test workbench objects (for example, test catalog, test plan, test package)

  • Entities of SAP Solution Manager (for example, branch, solution, view)
  • Tracing tools (for example, Performance Trace, Business Process Change Analyzer)
  • Foreground scheduler
  • Internal eCATT references (for example, restart from log)

Start Options

Here are the settings that were used for executing a test run.

Log Blocks

eCATT logs are ogranized in blocks. This enables a structured and readable display, as well as fast data processing.

A block is a group of related log lines. In the classic log display (transaction SECATT_LOG) you can identify a block on the icon for expanding (>) at the beginning of the line.

Precisely one higher-level block is assigned to each block At the same time, each block can have an unlimited number of sub-blocks. In this way, a hierarchical tree-like structure is formed. At the highest hierarchy level there is always one root block.

Log Lines

A log line contains data for a single step of the test run, for example:

  • Current test case number

  • Current step number
  • Reference to higher level
  • Status
  • Step type / eCATT command
  • Time of execution

Data Lines

Some log lines have further data lines that are stored as strings in the database. The semantics of this data is derived from the step type or eCATT command of the protocol line. For example:

  • eCATT command *

    → data row contains comment

  • eCATT command ABAP

    → data row contains ABAP code

  • Step types IMPORT, LOCAL, EXPORT

    → data row contains information about the parameters of the test script

XML Data

Complex data exists for some log lines, and this must be saved in XML format. For example:

  • Complex (structured / table-type) parameters

  • Command interfaces
  • Communication with external test tools

Messages

Messages are all those messages that were logged during the test execution. For example:

  • Error messages of the tested application or the test environment

  • Status messages of the test framework.