Execute Menu

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

Each process model defines a set of Execution entry points. Each entry point is a sequence in the process model file that invokes a test sequence file.

Execution entry points appear at the top of the Execute menu in the TestStand Sequence Editor. For example, the default process model provides the Test UUTs and Single Pass Execution entry points. When you select an Execution entry point, you invoke an execution using the active sequence file as the client sequence file.

The Execute menu contains the following options:

  • Test UUTs—Initiates an execution using the active sequence file as the client sequence file for the Test UUTs Execution entry point in the process model. The first Execution entry point defined in the process model specifies the display name for the command.
  • Single Pass—Initiates an execution using the active sequence file as the client sequence file for the Single Pass Execution entry point in the process model. The second Execution entry point defined in the process model specifies the display name for the command.
  • Run <Sequence>—Initiates an execution of the active sequence without using a process model.
  • Restart—Initiates a restart of the execution in the active Execution window. The TestStand Sequence Analyzer does not reanalyze sequences when you restart an execution.
  • Run Selected Steps—Executes selected steps in a sequence interactively. When you execute steps in a Sequence File window, you initiate the interactive execution as an independent, top-level execution. When you execute steps in an Execution window for a suspended sequence execution, you initiate the interactive execution as an extension of the suspended execution.
  • Run Selected Steps Using—Interactively executes selected steps using the entry point you select. When you execute the steps using an Execution entry point, such as Single Pass, the process model generates a report and logs the results to a database. The Run Selected Steps Using command is available only in a Sequence File window.
  • Loop On Selected Steps—Interactively loops on the selected steps without a Process Model entry point. The Loop on Selected Steps command is available only in a Sequence File window.
  • Loop On Selected Steps Using—Interactively loops on the selected steps using the entry point you select. When you loop on steps using an Execution entry point, such as Single Pass, the process model generates a report and logs the results to a database. The Loop on Selected Steps Using command is available only in a Sequence File window.
  • Break on First Step—Suspends execution on the first step TestStand executes whenever you initiate execution in the active sequence. When enabled, this command has a checkmark beside it in the menu.
  • Break on Step Failure—Suspends execution on steps that result in a step status of Failed. When enabled, this command has a checkmark beside it in the menu. If a step in a process model sequence file causes the sequence to which the step belongs to fail, TestStand only suspends the execution if tracing for the sequence or if a previous suspend occurred within the sequence context.
  • Break on Sequence Failure—Suspends execution on steps that cause the sequence to fail. When enabled, this command has a checkmark beside it in the menu. If a step in a process model sequence file causes the sequence to which the step belongs to fail, TestStand only suspends the execution if tracing for the sequence or if a previous suspend occurred within the sequence context. TestStand also suspends an execution if the SequenceContext.SequenceFailed property is set during the execution of a step even when the step does not fail.
  • Tracing Enabled—Highlights each step as it becomes the active step during execution. When you disable this feature, updates to the Execution window only occur when execution is suspended. When enabled, this command has a checkmark beside it in the menu.

See Also

SequenceContext.SequenceFailed

WAS THIS ARTICLE HELPFUL?

Not Helpful