The Debug menu in the TestStand Sequence Editor contains the following items, which control how TestStand single steps within an execution:

• Toggle Breakpoint —Sets or clears the breakpoint state for the selected steps.
• Run Mode —Sets the following run-mode values for the step:
  • Force to Pass —The step does not execute. Instead, the step status is set to Passed .
  • Force to Fail —The step does not execute. Instead, the step status is set to Failed .
  • Skip —The step does not execute. Instead, the step status is set to Skipped .
  • Normal —The step executes normally.
• Resume —Continues execution when the sequence execution is in a suspended state.
• Step Into —Enters and suspends within a function, VI, or sequence the step calls. If the step calls a code module TestStand cannot suspend within, TestStand suspends the execution at the next step.
  Note When you step into a VI from TestStand and then select Return to Caller without executing the VI, any values you change in the controls or indicators of the suspended VI are not returned to TestStand.
• Step Over —Executes the step to which the execution pointer points when the sequence execution is in a breakpoint state. If the step is a call to another sequence, the Step Over command executes the entire sequence and enters a breakpoint state on the step following the Sequence Call step. If the TestStand Engine encounters a breakpoint within the Sequence Call step, the Step Over command pauses at the breakpoint. If the Step Over command executes on an End step in a Pre-Step callback sequence , TestStand attempts to step into the code module.
• Step Out —Resumes execution through the end of the current sequence and suspends/pauses on the next step in the calling sequence.
  Note When you use the Step Into, Step Over, or Step Out commands, TestStand does not suspend in Sequence callbacks or step groups where tracing is disabled unless TestStand is already suspended within the sequence.
• Set Next Step to Cursor —TestStand starts from the selected step when you resume execution.
• Break —Suspends the active execution after completing the execution of the current step in all threads of the execution. Because the Allow Break While in Code Modules option on the Execution tab of the Station Options dialog box is enabled by default, TestStand suspends the execution even if some threads are executing code inside a code module. Using the Thread.ExternallySuspended property in a code module results in the same behavior.
• Break All —Suspends all running executions. Each execution suspends after completing the execution of the current step in all threads of the execution. Because the Allow Break While in Code Modules option on the Execution tab of the Station Options dialog box is enabled by default, TestStand suspends the executions even if some threads are executing code inside a code module. Using the Thread.ExternallySuspended property in a code module results in the same behavior.
• Terminate Execution —Terminates a running or suspended execution that is active. A running execution terminates only after completing the currently executing step in all threads of the execution. When you terminate an execution, TestStand runs the Cleanup step groups for all active sequences on the call stack.
• Abort (no cleanup) —Aborts a running or suspended execution that is active. A running execution aborts only after completing the currently executing step in all threads of the execution. When an execution aborts, TestStand does not run any Cleanup step groups.
  Note If a code module waits for user input or does not return quickly for any other reason, the code module can use the Execution class in the TestStand API to monitor for termination or abort requests.
• Terminate All —Terminates all running executions. Each execution terminates after completing the execution of the current step in all threads of the execution.
• Abort All (no cleanup) —Aborts all running executions. Each execution aborts after completing the execution of the current step in all threads of the execution.
• Resume All —Continues all suspended executions.
• Breakpoints/Watches —Launches the Edit Breakpoints/Watch Expressions dialog box, in which you can edit breakpoints and watch expressions associated with the current workspace.
• Sequence Analyzer —Contains the following options for use with the TestStand Sequence Analyzer:
  • Analyze < file or project name > —Starts analysis. If the Current Sequence Analyzer Project window is active, the sequence analyzer analyzes the project. If a sequence file or workspace file is active, the sequence analyzer analyzes the sequence file or workspace file using the rules and settings from the current sequence analyzer project.
  • Stop All Analysis —Stops all analysis sessions in progress. The sequence analyzer waits for the currently executing analysis module to complete before stopping the analysis.
  • Toggle Analyze File Before Executing —Enables or disables the Analyze File Before Executing option in the Sequence Analyzer Options dialog box. When you enable this option, the sequence analyzer uses the rules and settings in the current sequence analyzer project to analyze the active sequence file when you initiate an execution. Enabling this option can help you find errors early during development.
  • Current Sequence Analyzer Project —Shows the Current Sequence Analyzer Project window for the current sequence analyzer project.
  • Sequence Analyzer Options —Launches the Sequence Analyzer Options dialog box, in which you edit settings the sequence analyzer uses to analyze the active sequence file.
    Note The sequence editor requires an enabled ConfigApp user privilege to launch the Sequence Analyzer Options dialog box. The built-in TestStand Developer and Administrator user groups grant this privilege by default.

See Also

Current Sequence Analyzer Project Window

Edit Breakpoints/Watch Expressions dialog box

Execution

Sequence Analyzer Options dialog box

Thread.ExternallySuspended

User and Group Privileges