OtfExecution

Introduction

The OTF does not only support design time activities but it also supports runtime very well. Similar to some other IDEs, users can execute a test sequence with or without debugging. There are many ways to execute a procedure such as using shortcut keys, using command buttons in the Ribbon menu or using context menu.

Setting Up before Execution

Setting up before execution relates to  the scopes to be executed  and  the platforms to execute .

Scopes of Execution

Executing a procedure  with shortcut keys  or  with command buttons  depends on which scope selected in the "Execute Of" combo-box in the "Runtime Environment" tab of the Ribbon Menu.

There are 4 scopes of execution:

Scope	Description
Solution	It shall execute the procedure main of the Startup Document in the Startup Project of the Solution.
Current Project	It shall execute the procedure main of the Startup Document in the current Project (of the current opened procedure tab or OTL tab).
Current Document	It shall execute the procedure main of the current Document (of the current opened procedure tab or OTL tab).
Current Procedure	It shall execute the current opened procedure. This scope has no effect when an OTL tab is currently opened.

Platforms to Execute

The OTF runtime supports to execute with Dotnet platform or Java platform. There are many ways to change the execution platform:

1. Use the "Target Platform" combo-box in the "Status Bar"
2. Use the "Target Platform" combo-box in the "Runtime Environment" tab of the Ribbon Menu
3. Use the "Target Platform" combo-box in the "Runtime Environment" settings page of the OTF Settings

Ways of Executing a Procedure

There are 3 ways to execute a procedure: using shortcut keys, using command buttons in the Ribbon menu or using context menu.

Using Shortcut Keys and Command Buttons

Below are the Shortcut Keys with their function descriptions:

Command Button	Shortcut Key	Function
Start	CTRL+F5	Executes the procedure (see execution scopes) without debbuging.
Debug	F5	Debugs the procedure (see execution scopes). Executes from the beginning/current node and suspends the execution at the following node with breakpoint in the test sequence waiting until a debug command/key is clicked/pressed.
Step Over	F10	Debugs the procedure (see execution scopes). Executes from the beginning/current node (it does not step into called procedures) and suspends the execution at the adjacent node followed the current node waiting until a debug command/key is clicked/pressed. If there is a breakpoint inside the called procedure, it steps into the called procedure and suspends the execution at the node having breakpoint.
Step To	CTRL+F10	Debugs the procedure (see execution scopes). Executes from the beginning/current node and suspends the execution at the next selected node waiting until a debug command/key is clicked/pressed. If there is a breakpoint between the current point and the selected node, it suspends the execution at the node having breakpoint. If the selected node precedes the current point, it works the same as Debug button (F5) from the current point.
Step In	F11	Debugs the procedure (see execution scopes). Executes from the beginning/current node and suspends the execution at the adjacent node followed the current node waiting until a debug command/key is clicked/pressed. If the current point is a ProcedureCall, it steps into the called procedure and suspends the execution at the beginning node.
Step Out	SHIFT+F11	Debugs the procedure (see execution scopes). Steps out (executes all remaining nodes of) the called procedure from the current point and suspends at the corresponding ProcedureCall waiting until a debug command/key is clicked/pressed. It is only active if the execution is being suspended at a node in a called procedure.