Execution Control

Use

If you are executing a lengthy test and would like information about the progress of the test during its execution, you have the following options:

  • You can open a parallel session and look at what has happened in the log.

  • You can start execution control.

Execution control not only gives you information about the test's progress, you can also intervene in its execution. The function allows you to pause or cancel the execution of a running test. You can also jump into the debugger. If you do interrupt the execution, this is marked at the highest level in the log (with an icon and "WITH INTERRUPTION") and also at the relevant place in the log (icon and type of interruption).

Activities

You can call execution control in the start options ( General tab) or from the log. If the control dialog window is hidden by the executing session, you can call the dialog window to the foreground by using the Windows key combination CTRL+TAB. Of course, the test must last long enough for you to be able to use execution control. If the test is too short, it would be closed again immediately. In this case, you should look at the status bar, which also contains various status messages.

At the start of execution control, the most important administration data is displayed, such as the procedure number, title, current status, and start time. You can use the icons at the bottom edge of the screen to select various functions. To see the current status of the test procedure, for example, you can jump directly to the log. You can also pause the execution, jump to the debugger, or cancel the execution. These actions are recorded in the log.

If you want to cancel a long-running test, but have not selected Execution Control in the start options, you can open the log in another session and choose Start of the navigation pathUtilities Next navigation step Execution ControlEnd of the navigation path. With appropriate authorization (S_DEVELOP, activity 70 (administration) for script or configuration), you can stop the execution of tests started by other users.

Result

After the test run, the statistics data on the test execution (for example, the number of test cases and which are in process or contain errors) is displayed in the log or in the execution control window itself. To view this statistics data in the execution control window straight after the test procedure, the window must not be closed straight away. To ensure the window stays open after execution, you have the following options:

  • In the execution window, choose the option Do Not Close Window At End of Procedure.

  • Activate the option Do Not Close Window At End of Procedure as the default for a user. The parameter EC_EXECCTRL_STAYALIV in the user transaction SU01 must have the value X.