TestStand 2019 Help
»View Product Info
The Execution tab has options for breakpoints, tracing, and interactive execution.
The Execution tab contains the following options:
- Enable Breakpoints—Enables all breakpoints. When you enable breakpoints, the following additional option is available:
- Honor Breakpoints while Terminating—Honors breakpoints when terminating an execution.
- Allow Break While in Code Modules—TestStand displays an execution as suspended so you can debug it even if one or more threads are executing code inside a code module, which can be useful when code modules take a long time to complete, are blocked waiting for something, or are running continuously in the background. While the execution is suspended, steps with running code modules show a status of Running. If the code module completes while the execution is suspended, the thread suspends immediately after returning from the code module until you resume the execution. Because this option is enabled by default, you do not need to use the Thread.ExternallySuspended property unless you disable this option. When you disable this option, TestStand displays an execution as suspended only when all threads are between steps or in a code module that uses the Thread.ExternallySuspended property.
- Enable Tracing—Enables tracing. When tracing is in effect, the TestStand Sequence Editor or TestStand User Interface application displays each step as it executes. This is useful for debugging but adds significant performance overhead to the execution of the test programs. When you enable tracing, the following additional options are available:
||Note You can also enable this option from the Execute menu using the Tracing Enabled command.
- Speed—TestStand inserts a delay between trace events sent to the sequence editor or any user interface. This delay applies only when tracing is enabled. Use this option to slow down the tracing so you can observe each step as it executes.
- Allow Tracing into Setup/Cleanup—Enables tracing of steps in the Setup and Cleanup step groups of each sequence.
- Allow Tracing into Pre-/Post-Step Callbacks—Enables tracing of steps in any of the Pre-Step and Post-Step Engine callback sequences.
- Allow Tracing into Post Action Callbacks—Enables tracing of steps in Post Action callbacks.
- Allow Tracing into Sequence Calls Marked with Tracing "Disabled"—Enables tracing into all subsequences when tracing for the calling sequence.
On the Run Options panel of the Step Settings pane, you can choose a setting that disables tracing when the step calls a subsequence. When you enable this option, TestStand ignores the step property setting and does not alter the tracing state when it calls the subsequence.
- Allow Tracing While Terminating—Enables tracing of steps that run while execution is terminating. Examples of steps that can run while an execution is terminating are steps in Cleanup step groups that run when you terminate execution in the middle of a sequence.
- Trace into Separate Execution Callbacks—Enables tracing in callbacks that run as executions separate from the top-level sequence execution. Examples include Front-End callbacks and callbacks you execute from the Tools menu.
- Trace into Entry Points—Enables tracing of steps in Process Model entry point sequences, such as the Test UUTs and Single Pass entry points.
- Interactive Executions—Use this section to set options that apply when you run steps interactively.
- Record Results—Records the results of steps you run interactively. When you run steps interactively from an Execution window when suspended in a normal execution, TestStand appends the results to the result list for the active sequence invocation so the results appear in the test report for the normal execution.
When you run steps interactively from a Sequence File window, TestStand accumulates the results in a result list for the interactive execution. If the interactive execution uses a process model that generates a report, the interactive step results appear in the report. You can also access an interactive execution result list from an Engine post-interactive callback.
- Run Setup and Cleanup—TestStand runs the Setup and Cleanup step groups for the sequence that contains the selected steps. This option applies only when you run the steps from a Sequence File window.
- Evaluate Preconditions—TestStand evaluates the preconditions for steps that execute in interactive mode. When you disable this option, TestStand honors the Run Mode settings of steps.
- Branching Mode—Use this option to specify the action TestStand takes when it executes a Goto step or evaluates a post action that specifies a destination step while running an interactive execution. The Branching mode contains the following options:
- Ignore All Branching—The interactive execution ignores all branches. TestStand executes the selected steps in the order the sequence editor or user interface specifies.
- Ignore Branches to Unselected Steps—The interactive execution allows branching within the selected steps. TestStand ignores all branching to non-selected steps.
- Go to End on Branches to Unselected Steps—The interactive execution allows branching within the selected steps. TestStand ignores all branching to non-selected steps and terminates the current pass for the interactive execution instead.
- Raise Error on Branches to Unselected Steps—The interactive execution allows branching within selected steps. Branching to non-selected steps will cause a run-time error.
- Allow All Branching—The interactive execution allows branching to selected steps and non-selected steps. When TestStand executes a selected step and no branch occurs, the next step is the next selected step. When TestStand executes a non-selected step and no branch occurs, the next step is the step after the non-selected step.
||Note Changes to the Branching Mode option affect only currently executing interactive executions.
- Propagate Failures and Errors from Nested Interactive Execution to Calling Execution—When you enable this option, TestStand allows sequence failure, goto cleanup, and error settings from a nested interactive execution to propagate to the invoking execution.
||Note When you enable this option, TestStand propagates the result status of the interactive execution, including results that pass and that do not error or go to cleanup, back to the main execution. Therefore, if the calling execution is currently in a failed state, running a nested interactive execution that finishes in a passed state causes the calling execution to finish in a passed state. Disable this option if you do not want the status of the interactive execution to affect the main execution.
- On Run-Time Error—Use this option to specify the action TestStand takes when a run-time error occurs. The following options are available in the ring control:
- Show Dialog Box—Launches the Run-Time Error dialog box when a run-time error occurs. The Run-Time Error dialog box lists the step and the cause of the error and then prompts you with options for handling the error. Options for handling the error include ignoring the error and continuing execution, retrying the step, jumping to the Cleanup step group, and aborting immediately. You can also choose to break at the current step and to suppress the Run-Time Error dialog box during the remainder of the current execution.
- Run Cleanup—Causes the execution to jump to the Cleanup step group. If the error propagates normally to the calling sequence, the calling sequence also jumps to the Cleanup step group so the cleanup steps run for all active sequences and the execution terminates.
- Ignore—Clears the error occurred flag for the step and execution proceeds at the next step in the sequence.
- Abort Immediately (No Cleanup)—Immediately halts execution without running cleanup steps.
- Immediately Goto Cleanup On Sequence Failure—Causes the execution to jump to the Cleanup step group when a step sets the sequence status to Failed. This option applies only to sequences for which you have set the On Step Failure option on the General tab of the Sequence Properties dialog box to Use Station Option.
||Notice This option applies to all sequence files, including process model files. Therefore, a Process Model entry point can jump to the Cleanup step group if the MainSequence callback step does not disable the Step Failure Causes Sequence Failure setting and if you set the On Step Failure sequence setting for the entry point sequence to either Use Station Option or Goto Cleanup.
- This setting takes precedence over Goto Destination post action settings.
- If this setting and the Branching Mode setting for interactive executions is not set to Ignore All Branching, when a step failure causes the interactive execution to fail, the interactive execution immediately stops executing the selected steps.
- Disable Result Recording for All Sequences—When you disable result recording with this option, the process model does not generate a result report for sequence executions.
Run-Time Error dialog box
Sequence Properties dialog box
Step Settings Pane