Show TOC

Start OptionsLocate this document in the navigation structure

Definition

You can enter start options on the corresponding tab. The tabs displayed depend on the context.

Parameters Tab

This is for test scripts. The import parameters of the test script are displayed. You can enter values to be used for execution.

Variants Tab

This is for test configurations.

You can select to execute the test configuration using either external variants or internal variants.

External Variants

To use external variants, the checkbox External Variants must be selected. The default folder for the file containing the external variants is specified in the user-specific settings . The default file is specified in the test configuration.

Internal Variants

To see and use internal variants, the checkbox External Variants must be deselected.

The variants to be executed are flagged in the Execute Variant field. The default setting for each variant is defined in the test configuration editor. You can override the defaults. You can do this individually for each variant.

In the Special, Generic field, you can define restrictions for the variants to be executed:

  • By entering an asterisk ( * ), all variants except ECATTDEFAULT are executed.

  • By entering a string followed by an asterisk, all variants whose names start with the entered string are executed. Example: TEST* .

  • By entering a string, only that variant is executed.

You can also overwrite the values for the ECATTDEFAULT in the ECATTDEFAULTRUN row.

General Tab

Execution

Error Behavior

You can specify how eCATT is to react to an error in a test.

You can choose from the following:

  • Termination: Continue with next test configuration. Execution continues with the next variant.

  • Termination: Continue with next test configuration. Execution continues with the next test configuration.

  • Termination of the start process: Execution does not continue.

  • No termination: Continue with next script command. Execution continues with the next script command.

Debugging Mode

You can specify if and when eCATT is to call the eCATT debugger .

You can choose from the following:

  • Normal Breakpoint Handling, Stop at BREAK

  • Execution with Immediate Debugging

  • Stop When an Error Occurs

  • Ignore Breakpoints (Default for Collective Execution)

Execution Control

If you select execution control , a dialog is available during replay in which you can pause or stop the script, or jump into the debugger. Any such user interaction will be recorded in the log.

System Data

Before you start a test, you can choose to use a system data container other than the one specified in the test configuration or test script.

You can also choose a different target system instead of the default target system . The default target system is:

  • The maintenance system when executing a test script alone from within the eCATT development environment.

  • The target system of the test configuration when executing a test configuration. The maintenance system of the test script is not relevant.

  • Commands having a specific target system will be executed in that system. If the system is neither physically available nor in the system data container, an error will result.

Logs

If you want the log to be displayed automatically at the end of a test, select Display Log .

If you want the archive flag to be set for the generated log, select Archive .

Log Details

This setting defines which test execution data is written to the eCATT log.

The option "Complete Log" is required for a comprehensive and easy-to-follow automated test.

If there is a large number of automated tests and frequent test execution, a complete logging can require considerable storage space in the databases for eCATT logs. To avoid the logging of unnecessary details, you can use the simplified log version: As long as the test result is positive, logging is skipped for many eCATT commands. If the test result is negative, the system switches automatically to "Complete Log" for the test in question.

If tests have positive results and, therefore, only simplified logs in their test procedure, the eCATT log may no longer be traceable.

You can choose between:

Key

Description
 

Complete Log

This is the default setting.

S

Short log - Block and selected commands only

A complete log is written in the background. If the test case runs successfully, everything not mentioned in the option in the drowpdown list is deleted (that is, everything apart from block commands and selected commands).

If an error occurs, the complete log is available with all details.

T

High level log - Test configuration and test script only

A complete log is written in the background. If the test case runs successfully, everything not mentioned in the option in the drowpdown list is deleted (that is, everything apart from test configuration and test script information).

If an error occurs, the complete log is available with all details.

X

Short log - No complete log for errors

In the case of a positive test result, this option works like option S.

Unlike with option S, the eCATT log data is not buffered in the transaction SECATT at runtime, therefore it is not possible to write a complete log in the case of an error.

The error itself is also logged in this case, but no details about the preceding steps.

Y

High level log - No complete log for errors

In the case of a positive test result, this option works like option T.

Unlike with option T, the eCATT log data is not buffered in the transaction SECATT at runtime, therefore it is not possible to write a complete log in the case of an error.

Y only contains information about the configuration and the script, and the information that an error has occurred.

The abbreviation S , T , X , or Y is displayed in the log overview beside the respective operation number and displayed in the log tree in the title in full.

RFC

You can specify that RFC connections be closed after a script or variant has been executed. For more information about closing RFC connections, see RESCON .

You can specify whether synchronous or asynchronous RFC should be used for remote access.

Message Processing

Here you can use eCATT to log messages from the application log and to process them according to the rules of the MESSAGE-ENDMESSAGE command.

Enterprise Services Framework

Select ESF Debugging if you want to debug the provider code rather than the ESF itself.

UI Control Tab

Start Mode for TCD

You can override the TCD mode of test scripts.

You can choose from the following start modes for TCD commands:

  • Display all (process in foreground), synchronous local

  • Error (display errors only), synchronous local

  • Display nothing (process in background), synchronous local

  • Display nothing (process in the background), asynchronous update

  • (Empty) Use the default

  • Display nothing (process in background), synchronous not local

For information about database updates, see SAP Transaction Concept .

Start Options for SAPGUI

Execution of all SAP GUI commands in a single session per destination. Select this option to overwrite the SessionId and ConnectionId in all command interfaces. They must have the same value. An example use is when you have rerecorded sections of a script and you suspect that an error in the replay is due to a wrong SessionId or ConnectionId .

Highlight GUI Elements . This marks the GUI elements that are currently being controlled during replay. It makes it easier to see what is happening on the screen. You can specify the duration under Start of the navigation path Utilities Next navigation step Settings Next navigation step eCATT Next navigation step Execution End of the navigation path.

Minimize eCATT GUI . Minimizes the eCATT GUI when SAPGUI commands are being replayed.

The playback modes are:

  • Optimized Performance . Automation calls are placed in the automation queue.

  • Synchronous GUI control . Automation calls are not queued.

You can choose from the following error modes:

  • Terminates on any error.

  • Continue Value (Continue even if field values are not specified) . Terminates for most errors but continues if a field value could not be delivered.

  • Continue after every error.

In the Stop When field, you can select points where playback should pause - for example, at each SAPGUI command. This option is used for debugging. Normally the debugger is not called. If you want to spring to the debugger when the playback stops, select Stop in Debugger .

You can choose to close generated sessions. In the Close GUIs field, you can choose:

  • Close Generated Session After Script . All GUIs will be closed at the end of the execution of the test script.

  • Close Generated Session After REF . At the end of each REF command, all sessions started with REF are closed.

  • Do Not Close Generated Sessions . Use this option if you are interested in the final state of a GUI after the execution of a test script.

Screenshots

  • Save Screenshots . Select this to automatically take screenshots during replay. You can select the following positions for the screenshots:

  • In case of error (mode 1)

  • Before user input (mode 2)

  • After user input (mode 3)

  • After each property/method call (mode 4)

  • The screenshot name contains the mode so you can tell where it was taken in relation to a command.

  • The screenshots are saved to the path specified in the field Screenshot Path . You can temporarily override the default path by choosing Change . The default path for the file containing the external variants is specified in the user-specific settings .

  • Separate Directory for this Activity . If you select this, all the screenshots taken during a replay will be stored in a new folder. The folder name contains the system name and the eCATT log number.

Web Dynpro

You can specify foreground or background processing. In addition, you can start in background mode and automatically change to foreground when an error occurs. You can choose from the following:

  • Background Processing

  • Foreground Processing

  • Foreground Processing (Parallel Display of Recorded Screens)

For foreground processing and foreground processing with parallel display, you can specify how long screens should be displayed.

Start Options for External Tools

You can select from the following start modes:

  • Normal run without debugging or the user interface of the external tool.

  • Debugging session with the user interface of the external tool.

  • Runs with the user interface of the external tool. No debugging.

You can enter the user name and password for the external tool, if required. If you do not enter these here, you will need to enter them the first time a REFEXT or SENDEXT command is called.

Breakpoints Tab

Here you specify breakpoints for the eCATT debugger.

The entries on this tab do not disappear after each execution. You can deactivate a breakpoint by selecting Inactive , or you can permanently delete a breakpoint.

Script Line

You can set script-specific breakpoints. For each breakpoint that you want to set, you specify the test script name, the version, and the line number. You can set several breakpoints in the same or different test scripts. If you view a script in the test script editor, you will see the lines with breakpoints highlighted in color.

Command and Object

You can set breakpoints at eCATT commands. Breakpoints that you specify here are valid for all test scripts. You can further restrict the breakpoints by specifying an object for the command. For example, if you only specify LOG , the debugger will stop at all LOG commands, but if you further specify A for the object, the debugger will only stop at LOG ( A ) .