Automated Test Software

Hands-On with NI TestStand and

LabVIEW

January 2015 Edition

Copyright
© 2010 National Instruments Corporation. All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including
photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of
National Instruments Corporation.
National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by
copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to
others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable
license or other legal restriction.

Trademarks
National Instruments, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section
on ni.com/legal for more information about National Instruments trademarks.
Product and company names mentioned herein are trademarks or trade names of their respective companies.
Members of the National Instruments Alliance Partner Program are business entities independent from National Instruments and have no
agency partnership, or joint-venture relationship with National Instruments.

Patents
For patents covering National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the
patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.
Exercise 1: Design the User Interface for the
Audio Quality Test
Objective: Start building your test application by adding front panel controls and indicators on a new
LabVIEW VI. This exercise is the first step towards building an application that will perform an audio
quality test to determine the sound quality of our handheld device. The following figure shows the results
of this exercise.

Figure 1 Completed Exercise 1

A front panel (shown in Figure 1) is where you will design the user interface. The front panel contains the
user controls and indicators that allow the user to interface with the application. No programming is
included on the front panel.
1. Launch LabVIEW by selecting Start»All Programs»National Instruments LabVIEW [version
number]»LabVIEW.
2. Select Blank VI under New on the welcome screen.
3. To begin designing the front panel, you will create four numeric controls and two numeric indicators.
The four controls will contain the parameters of the audio quality test, including the minimum and
maximum frequency limits and the minimum and maximum amplitude limits. The two indicators will
show the frequency and amplitude of the signal you acquire.
a. Right-click on the front panel to open the Controls palette and select Numeric»Numeric
Control and place the numeric control on the front panel.

Figure 2 Numeric Control

Tip: The Controls palette provides access to many useful front panel controls such as input boxes,
command buttons, and gauges.
b. Double-click on the word Numeric to edit the label. Change the label of the numeric control
to Minimum Amplitude.
c. Click in the control and enter a value of 4.6.
d. Repeat the previous steps (a–c) to create the other three numeric controls. Use the following
chart for the control values.
Tip: Alternatively, you can make copies of the control (or any other object) if you click on the
control, press and hold the <Ctrl> key, and then drag the control to a new location.

Control Name Value

Maximum Amplitude 4.7

Minimum Frequency 99,800

Maximum Frequency 100,100

e. Right-click on the front panel and select Numeric»Numeric Indicator and place the numeric
indicator on the front panel.

Figure 3 Numeric Indicator

f. Change the label of the numeric indicator to Amplitude.

g. Repeat the previous steps (e–f) to create another numeric indicator.
h. Name the numeric indicator Frequency.
i. To save the current values of the controls, selecting Edit»Make Current Values Default.
This will ensure that every time the VI is opened, these values will be stored.
4. Next you will create a Boolean indicator that displays the Pass/Fail result of the test.
a. Right-click on the front panel and select Boolean»Square LED to create a Boolean.

Figure 4 Square LED

b. Resize the LED by clicking on the corner of the LED (the pointer will change to an arrow and
blue squares will appear) and dragging outward to make it larger.
c. Right-click on the LED and select Properties to edit the properties of the LED.
d. From the resulting dialog, select the Appearance tab.
e. Under the Label section, set the label to Pass and then uncheck the Visible checkbox.
f. Under the Colors section, click the dark box next to Off. Change the color to a shade of red.
g. Enable the Show Boolean Text section.
 Type in PASS as the On text.
 Type in FAIL as the Off text.
 Check Lock text in center.
 The updated properties dialog is shown below.

Figure 5 Pass Button Properties

h. Click OK to exit.
5. Place two graphs on the front panel to display the acquired signal and the FFT result.
a. Right-click on the front panel and select Graph»Waveform Graph.

Figure 6 Waveform Graph

Important: Make sure to select the Waveform Graph and not the Waveform Chart. They are
sometimes confused because the icons look similar.
b. Change the label of the graph from Waveform Graph to Audio Input Signal.
c. Right-click on the front panel and select Graph»Waveform Graph.
d. Change the label of the graph from Waveform Graph to FFT.
e. Right-click on the Waveform Graph labeled FFT and select Properties to edit the properties
of the waveform graph. The properties will allow us to edit the scales of the graph.
f. From the resulting dialog, select the Scales tab.
g. Choose Time (X-Axis) from the first drop down menu in the Scales tab.
h. Change the name to Frequency.
i. Uncheck Autoscale and set the Minimum and Maximum input fields to be 0 and 5E+6,
respectively. The resulting Properties dialog should look like the screenshot below.

Figure 7 Filter Response Graph Properties for X-axis

j. Select the Plots tab.

k. Choose Plot 0 from the drop down menu on the Plots tab.

l. Change the name to FFT – (RMS)

m. Click OK to save your changes.

6. Arrange the controls, indicators and graphs so that the front panel looks similar to the image below.

Figure 8 Front Panel

7. Although you will not use the block diagram yet, switch to the block diagram to see the terminals of
the controls and indicators that you have added to the VI.
a. To switch to the block diagram, select Window»Show Block Diagram.
b. Rearrange the terminals so that they are similar to the figure below. The terminals on the left
side are your controls, while the terminals on the right side are your indicators.
Tip: Controls are front panel objects for entering data to a VI interactively or to a subVI
programmatically, such as a knob, push button, or dial. Indicators are front panel objects that
display outputs, such as a graph or LED.
c. If any terminal is missing a label, such as the Boolean indicator, right-click on it and select
Visible Items»Label.

Figure 9 Block Diagram

8. Select File»Save and save your VI as Ex 1 - Audio Quality Test.vi in the D:\Seminars\
HandsOn\Automated Test\Exercises folder.

End of Exercise 1
Exercise 2: Add Simulated Instrument I/O to the Audio
Quality Test
Objective: Building upon the previous exercise, you will add the VIs that will simulate acquiring a signal
from a digitizer (oscilloscope).

Figure 2 Completed Exercise 2

1. Use the following steps to make a working copy of the VI that you created in the previous exercise.
a. If you closed your VI earlier, open Ex 1 – Audio Quality Test.vi from the
D:\Seminars\HandsOn\Automated Test\Exercises folder.
b. Select File»Save As…, select Substitute copy for original, and click Continue….
c. Name the VI Ex 2 – Audio Quality Test.vi and click OK.
2. Now you will add an Express VI to acquire the simulated signal from the handheld device’s audio
output. We can do this in one step using the NI-Scope Simulated Acquisition Express VI.
a. To begin designing the block diagram, navigate to Window»Show Block Diagram.
b. Right-click on the block diagram, and select Express»Input»NI-SCOPE Express.

Figure 2 NI Scope Express VI

c. Place the NI-Scope Express VI on the block diagram.
d. On the resulting configuration dialog, configure the values as shown in the figure below. All
of the other values are left on their default setting. Be sure that channel 0 is highlighted in the
Channels box when making these changes.

Configuration Option Value

Channel 0 Checked

Channel 1 Unchecked

Range (V) 10

Offset (V) 5

Sample rate (S/s) 10M

Record length 1k

Figure 3 Configure NI-SCOPE Express

e. Select the Trigger tab.
f. On the resulting configuration dialog, configure Max time (s) to be 0.1. All of the other
values should be left at their default setting.
g. Click OK to close the dialog and save changes.
3. Left-click the Signal output of the NI-Scope Express VI and then left-click the input connector of the
Audio Input Signal graph. This process is known as wiring two VIs together.
The block diagram should resemble the image below. Check to make sure that your VI is free from
errors by checking that the Run arrow is not broken.

Figure 4 Completed Exercise 2b

If the Run arrow is broken , indicating an error, click on it to see the list of errors. If you double-click
on the error in the resulting Error List window, a moving dashed outline called a marquee will highlight
the error on the block diagram so that you can find and fix it.
4. Save your VI by selecting File»Save.
5. Return to the front panel by clicking Window»Show Front Panel.

6. Click the Run button, , to verify that the VI is working properly. A sine wave should be displayed
on the Audio Input Signal graph.

Figure 5 Sine Wave on Graph

7. Return to the block diagram and click on the Highlight Execution button. This turns on a
debugging functionality that animates VI execution to illustrate the data flow.
8. Click on the Run button and see how the data flows from terminal to terminal.

Figure 6 Highlight Execution

9. Click on the Highlight Execution button again to turn it off.

End of Exercise 2
Exercise 3: Add Analysis Functionality to
Audio Quality Test
Objective: This exercise will finish the VI from the previous two exercises. You will add the FFT and
then test the result to determine if the frequency and amplitude are within the acceptable range. The
following figure shows the results of this exercise.
Note: This exercise includes thorough descriptions of each step to assist you in understanding why each
step is used. Because of this level of detail, you may not have enough time to complete it in the time
allowed. If you are unable to complete the exercise, there is a completed version in the Solutions folder
available for you to use for the next exercise.

Figure 3 Completed Block Diagram of Exercise 3

Exercise 3A: Add an FFT to the Audio Quality Test

Use the following steps to make a working copy of the VI that you created in the previous exercise.
a. If you closed your VI earlier, open Ex 2 - Audio Quality Test.vi in your
Exercises folder.
b. Select File»Save As…, select Substitute copy for original, and click Continue….
c. Name the VI Ex 3 - Audio Quality Test.vi and click OK.
2. To perform an FFT, we will add an Express VI.
a. Right-click on the block diagram and select Express»Signal Analysis»Spectral
Measurements. The Spectral Measurements Express VI will generate an FFT based on the
simulated output from the handheld device.

Figure 2 Spectral Measurements Express VI

b. Place the Spectral Measurements Express VI to the right of the NI-Scope Express VI.
c. On the resulting configuration dialog, leave everything at the default settings and click OK.
d. Wire the Signals output on the NI-Scope Express VI to the Signals input connector of the
Spectral Measurements Express VI.
e. Wire the FFT – (RMS) output from the Spectral Measurements Express VI to the FFT graph.

Figure 3 Block Diagram After 2E

3. To perform analysis of the audio signal to determine the frequency and amplitude, we will add
another Express VI.
a. Right-click on the block diagram and select Express»Signal Analysis»Tone
Measurements.
b. Place the Tone Measurements Express VI to the right of the NI-Scope Express VI and
underneath the Spectral Measurements Express VI.
c. On the resulting configuration dialog, select the check boxes Amplitude and Frequency.

Figure 4 Tone Measurements Dialog Window

d. Leave everything else at the default settings and click OK. The Tone Measurements Express
VI will now appear on the block diagram.

Figure 5 Tone Measurements Express VI

 e. Wire the Signals output connector of the NI-Scope Express VI to the Signals input of the
Tone Measurements Express VI.

Figure 6 Block Diagram After 3A

Exercise 3B: Add Limit Testing to Audio Quality Test

Now that you have the amplitude and frequency of your signal, you need to evaluate whether the values
are within the acceptable range.
4. To check whether the amplitude is within an acceptable range, you will create the LabVIEW code for
this evaluation.
a. Right-click on the block diagram and select Numeric»Conversion»To Double Precision
Float VI.

Figure 7 To Double Precision Float VI

b. Place the To Double Precision Float VI to the right of the Tone Measurements Express
VI.
c. Wire the output of the Amplitude connector of the Tone Measurements Express VI to the
input of the To Double Precision Float VI.
d. Right-click on the block diagram and select Comparison»In Range and Coerce VI.

Figure 8 In Range and Coerce VI

e. Place the In Range and Coerce VI to the right of the To Double Precision Float VI.
f. Wire the output of the To Double Precision Float VI to the x input of the In Range and
Coerce VI.

Figure 9 Connecting To Double Precision Float VI to In Range and Coerce VI

g. Wire the output of the Maximum Amplitude control to the Upper Limit input of the In
Range and Coerce VI.
h. Wire the output of the Minimum Amplitude control to the Lower Limit input of the In
Range and Coerce VI.
Note: Be sure to wire the Maximum Amplitude to the top input and the Minimum Amplitude
to the bottom input of the In Range and Coerce VI. If this is done incorrectly, the
measurements will always fail.
i. Right-click on the block diagram and select Boolean»And VI.
j. Wire the In Range? output of the In Range and Coerce VI to the top input of the And VI.
k. Left-click on an open area of the block diagram and drag to select the To Double
Precision Float VI and the In Range and Coerce VI.

Figure 10 Selecting the Double Precision Float VI and In Range and Coerce VI

l. Select Edit»Create Sub VI. This will create a subVI that packages the functions we just
created. This will allow us to simply reuse the VI rather than recreating the code again.
m. Double-click on the new VI that was created to see the front panel.
n. Double-click on the Maximum Amplitude control label to change the name of the control
to Maximum.
o. Double-click on the Minimum Amplitude control label to change the name of the control
to Minimum.
p. Double-click on the Amplitude label and change the name of the control to Signal.
q. Double-click on the Boolean indicator label and change the name of the indictor to In
Range.

Figure 11 Audio Quality Test Sub VI

By changing the labels of the controls, we have made this VI better for reuse. We can
now pass any signal, minimum and maximum values and check if it is in range. While we
could have done this without changing the labels, changing the labels makes the VI a
more accurate representation of what is actually occurring in the VI.
r. Save the VI as Audio Quality Test Range.VI in your Exercises folder.
s. Close the Audio Quality Test Range.VI and return to Ex 3 - Audio Quality Test.VI.
t. Left-click on the Audio Quality Test Range VI on the block diagram and select Edit»
Copy to copy the Audio Quality Test Range VI.
u. Select Edit»Paste to paste another copy of the Audio Quality Test Range VI onto the
block diagram to the right of the Tone Measurements Express VI.
v. Wire the output of the Frequency connector of the Tone Measurements Express VI to the
Signal input of the second Audio Quality Test Range VI.
w. Wire the output of the Maximum Frequency control to the Maximum input of the second
Audio Quality Test Range VI.
x. Wire the output of the Minimum Frequency control to the Minimum input of the second
Audio Quality Test Range VI.
y. Wire the In Range output of the second Audio Quality Test Range VI to the bottom input
connector of the And VI.
 z. Wire the output of the And VI to the input connector of the Pass indicator.

Figure 12 Completed Sub VIs

5. Connect the Amplitude output of the Tone Measurements Express VI to the input of the Amplitude
indicator.
6. Connect the Frequency output of the Tone Measurements Express VI to the input of the Frequency
indicator.
7. Add a wait to the VI. This will cause the VI to pause before closing so that you can see the VI itself
when called from TestStand.
a. Right-click on the block diagram and select Express»Exec Control»Time Delay.
b. Place the Time Delay Express VI on the block diagram.
c. On the resulting dialog press OK to leave the delay at 1 second.

Figure 13 Time Delay Express VI

8. Your completed block diagram should look like the following figure:

Figure 14 Audio Quality Test Block Diagram

9. Now, run the VI.

a. Switch to the Front Panel.
b. Click the Run button. Run the VI several times until you receive a few passes and a few
failures.
10. Save the VI.

End of Exercise 3
Exercise 4: Add Tests Using NI TestStand Sequence Editor
Objective: To create a TestStand sequence and add steps to the MainSequence that uses the Frequency
test created in the first three exercises.
The TestStand Sequence Editor is a graphical user interface (GUI) for creating and modifying sequence
files. You use the sequence editor to add steps to a sequence file to create a test sequence for the handheld
device.

Exercise 4A: Edit Audio Quality Test VI Properties

1. Follow these steps to make a working copy of the VI that you created in the previous exercise:
a. Open Ex-3 Audio Quality Test.vi in your Exercises folder.
b. Select File»Save As…, select Substitute copy for original, and click Continue….
a. Name the VI Audio Quality Test.vi and click OK.
2. You completed the VI for the filter test and tested it in the previous exercise, but now you will need to
edit the VI so that it will output the result of the Pass terminal to TestStand.
a. With the front panel open, at the top right corner of the window, you will see the
Connector Pane.
b. Click on the top right box of the connector.

c. Then left-click on the Pass Boolean indicator on your front panel. This associates the
Pass Boolean control with the selected terminal of your VI.
3. Now, resize the VI front panel to only show the Waveform Graph for the signal and frequency
analysis and Pass Boolean indicator. If you need to move your controls, indicators or graphs, be sure
to click on the outside of the control, not on one of the resizing squares. When the VI is called as a
popup panel by TestStand, only the waveform graph will be visible.
4. The final change that you need to make to the VI is to change the window appearance.
a. Navigate to File»VI Properties.
b. On the resulting dialog window, select Window Appearance in the Category drop-down
box.
c. Select the Dialog radio button.
d. Select OK to save changes.
 e. Run the VI to see how the window appears.

Figure 4 Audio Quality Test VI Dialog Box

f. Save the VI and then close the VI.

g. Leave LabVIEW open and continue.

Exercise 4B: Create a TestStand Sequence and Add the Frequency Test Step
1. Select Start»Programs»National Instruments»TestStand [version number]»Sequence Editor.
2. After the TestStand Sequence Editor opens, a login dialog will appear. There is no password. Click
OK. Each time you open the Sequence Editor, you will be prompted to login.
Tip: You can control access to specific TestStand capabilities based on the user login level. Using an
interactive user manager environment, you add, remove, and edit users, their passwords, access
levels, and profiles. In this case, when you log in as an administrator, you have access to all TestStand
sequence editor capabilities.

Figure 5 Login Dialog Box

 3. The TestStand Sequence Editor should appear as in the following figure. The areas of the sequence
editor are labeled below.

Sequences Pane Steps Pane

Insertion
Palette

Step
Setting
Pane
Template
Area

Figure 3 TestStand Sequence Editor

4. Now you will confirm that the execution process model is correct for this exercise. In this case, you
will use the Sequential execution process model.
a. Select Configure»Station Options and select the Model tab.
b. Use the Station Model drop-down to select SequentialModel.seq or click the browse
button, to go to C:\Program Files\National Instruments\TestStand
[version number]\Components\Models\TestStandModels and select
SequentialModel.seq.
c. Click OK on the Station Options window to return to the Sequence Editor.
5. To add a new step you will first have to select the LabVIEW adapter which allows you to call and run
LabVIEW VI code modules from TestStand. To select the LabVIEW adapter, simply click the
LabVIEW icon at the top of the Insertion Palette.

Figure 4 LabVIEW Icon on Insertion Palette

6. Now you will insert the first step in the test sequence, which will test the sound quality of the
handheld device. The test will return a Boolean value for the pass/fail result, so the type of test you
want is a pass/fail test.
a. Click the + sign in the Insertion Palette next to the Tests folder.
b. Drag and drop a Pass/Fail Test from the Insertion Palette to the Main step group in the
Steps pane as shown in the following image.

Figure 5 Addition of Pass/Fail Test Step

7. Double-click on the Pass/Fail Test step to edit the test step’s name. Rename the step Audio
Quality Test.
8. Now that you’ve selected the type of step, you will need to specify which LabVIEW VI this step
calls. You will use the LabVIEW VI that you saved earlier in this exercises as the code for this test.
a. When you click on the Audio Quality Test step, the Step Properties pane automatically
updates with the step’s properties.
b. Click on the Module tab in the Step Setting pane. This will allow you to choose the code
module, in this case a LabVIEW VI, that you want to associate with this step.

c. Click the File Browse button on the right to open Select a Pathname for the Step’s
Code Module.

Figure 6 Select a Pathname for the Step's Code Module Dialog Box

d. Select the Audio Quality Test.vi file from your Exercises directory, Automated Test
Software Hands-On\Exercises, and click Open to return to the Edit LabVIEW VI
Call dialog box.
e. If a File Not Found dialog appears, select Use an absolute path for the file you selected
and click OK.
9. Now that you have selected the VI, you will need to define where to store the test result in TestStand.
a. Notice that the Description and Connector Pane now shows the VI icon with a Boolean
output terminal. This output is available to TestStand because of the edit you made to the
connector pane of the VI earlier in Part A of this exercise.
 Figure 7 Description and Connector Pane
b. Click the Value field for Pass Boolean parameter and click the Expression Browse
Dialog Box… button to the right. You can use the Expression Browser Dialog Box…
to interactively build an expression by selecting from lists of variables, properties,
operators, and functions.
c. In this case, navigate the properties of the step and select Step.Result.PassFail. Click
Insert to select that property.

Figure 8 Edit LabVIEW VI Call Dialog Box

d. Step.Result.PassFail is the TestStand property that will now contain the Pass value.
e. Click OK again to return to the sequence editor window.
10. In order to see how the test is executing you will have to show the front panel of the VI.
a. Select the checkbox for Show VI Front Panel When Called.
11. You have finished adding the first step to your test sequence.
Exercise 4C: Run the Sequence
1. Now that you have created your first test sequence, you can execute your test sequence. Select
Execute»Single Pass.
2. Select Yes to save the sequence file. Name the sequence file Ex 4 - Handheld Test.seq in the
Exercises folder.
3. The test sequence will now execute. You should see the Audio Quality Test VI appear on the screen.
If the VI passed, the test step will pass, if the VI failed the test step will fail.
4. A report for your test sequence will automatically be generated.

Figure 9 UUT Report

5. To run another test, click Execute»Restart.

6. Close the Single Pass window by selecting Window»Close Completed Execution Displays when
you are finished.

End of Exercise 4
Exercise 5: Add Tests Using Preconfigured Step Templates
Objective: To complete a TestStand sequence by adding steps to the MainSequence using built-in
TestStand preconfigured step templates. You will build on the sequence file you created in the previous
exercise.
Preconfigured step templates allow you to easily create and store preconfigured templates of the steps you
created in the Sequence Editor. These templates can be used to quickly build sequences based on
commonly used steps.

Exercise 5A: Create Your First Template

5. If you closed the sequence you created in the last exercise, reopen it.
c. Open Ex 4 - Handheld Test.seq in your Exercises folder.
6. In the last exercise, you completed your first test sequence by adding your first step. Now we are
going to use that step to create a step template.
a. In the Templates Area, expand the Steps folder by clicking the + sign. This will reveal
another folder, Multifunction Handheld Device Tests.
b. Expand the Multifunction Handheld Device Tests folder by clicking the + sign. This will
reveal a list of the preconfigured step templates.

Figure 1 Templates Window

 c. In the MainSequence, click and drag your step, Audio Quality Test, into the
Multifunction Handheld Device Tests folder to create a new template.

Figure 2 Creating a Template Step

You have now created your first template. You can drag this template into your sequence file to reuse it
at a later time.

Exercise 5B: Create a TestStand Sequence and Add the Template Steps
12. Create a new sequence file for the complete handheld test.
a. Select File»New Sequence File to create a new sequence file.
b. Select File»Save and save the file as Ex 5 - Complete Handheld Test.seq in
your Exercises folder.
13. Add steps to the Setup step group.
The Setup step group runs before the Main step group. This step group should be used for
initialization steps, such as turning instruments and other devices on. For our example, we will
initialize and configure all of our test machines.
a. Click the + sign next to Setup step group in the Steps pane to expand the Setup step
group.
 b. Drag the Initialize Instrumentation template from the Insertion Palette into the Setup step
group. This will create a step using the template that has been created for you.

Figure 3 Adding a Template Step

14. Add steps to the Main step group.

The Main step group is where the bulk of the work should be performed by your test sequence. For
our example, we will perform all of our tests in the Main step group.
a. Click the + sign next to the Main step group in the Steps pane to expand the Main step
group.
b. Drag the Power Consumption Test step template into the Main step group. The power
consumption test will verify whether the phone stays within an acceptable range for
power consumption. If this test fails, we do not want to run any of the other tests.
c. Under the Insertion Palette, click the + sign next to Flow Control to expand the flow
control steps. Flow control steps allow developers to control the order of execution of
steps in a TestStand Sequence with constructs such as While Loops and If statements.
d. Drag an If step type under the Power Consumption Test. Click the If step. The Step
Settings window will update to show the If step properties. Click the Condition Builder
button on the right to build a condition for the step.
e. Select Power Consumption Test under the Insert Step Status dialog. Click the Insert
Step Pass button to insert a condition in the statement. This will build the condition in
 the If step that is true if the Power Consumption Test passes. If the test fails, nothing
inside of the If statements will run.

Figure 4 Condition Builder Dialog Window

f. Click OK to exit the Condition Builder.

g. Drag the LED Test template into the Main step group, inside of the If block. This test will
test the LED of the handheld device.
h. Drag the Volume Test underneath the LED Test. This will test that the volume of a signal
from the phone is within an acceptable range.
i. Drag an If step type under the Volume Test. This will create a nested If block. Follow
step d to create a Pass condition that checks the Volume Test instead of the Power
Consumption Test.
j. Drag the Audio Quality Test template inside the new If block. Because the test is within
the new If block, TestStand will only run the Audio Quality Test if the Volume Test
passes. The Audio Quality Test step is the step you created previously.
k. Drag the Bluetooth Test template underneath the new End step.
l. Drag the Wi-Fi Test template underneath the Bluetooth Test step.
m. Drag a For step type from the Flow Control menu underneath the Wi-Fi Test. A For step
type will allow you iterate over a group of steps a specified number of times. The step
settings dialog will automatically change to the For Loop parameters.
n. Enter the number 4 in the Number of Loops text box. This will tell the loop how many
times it should iterate.
 o. Click the Expression Browser Dialog Box… button next to the Loop Variable
dialog box. This will show the Expression Browser Dialog Box which allows you to
build an expression. Right-click on word Locals in the tree shown and select Insert
Number. This will create a local number variable. Name the variable
ImpactTestCount.
p. Click the Insert button to build your expression. Locals.ImpactTestCount will now
appear in the expression window.
q. Click OK to insert Locals.ImpactTestCount as the expression. This variable will keep
track of how many times the loop has iterated.
r. Drag the Impact Test template inside of the For Loop.
15. Add steps to the Cleanup step group.
The Cleanup step group runs after the Main step group. As its name implies, it should be used to
provide cleanup for the tests that have been performed in this sequence. For this test, we will turn off
all of our test instruments in this step group.
a. Click the + sign next to Cleanup to expand the Cleanup step group.
b. Drag the Turn Off Instrumentation template into the Cleanup group.
c. Your sequence should resemble the following.

Figure 5 Complete Handheld Sequence

Exercise 5C: Run the Completed Sequence
7. Now that you have completed the entire test sequence, you can execute test your handheld device.
Select Execute»Single Pass. If prompted, select Yes to save the sequence file.
8. View the test results.
9. To run another test, click Execute»Restart.
10. Close the Single Pass window by pressing the Close button on the window or selecting Window»
Close Completed Execution Displays when you are finished.

End of Exercise 5
Exercise 6: Debug Test Sequence Using the NI TestStand
Sequence Editor
Objective: To become familiar with using breakpoints and debugging tools in the sequence editor.
When you create a sequence file, you might want to observe sequence execution to make sure the
sequence behaves as you need. During debugging, you might want to observe execution in some sections
of a sequence but not others. In this exercise, you want TestStand to execute the sequence until it reaches
a section you want to analyze. TestStand allows you to insert convenient stopping points, known as
breakpoints, in the sequence. Like most modern development systems, TestStand allows you to set and
remove multiple breakpoints for every sequence file.

Exercise 6A: The Step Debugging Tools

7. In the sequence editor, select File»Open and open the Ex 5 – Complete Handheld Test.seq
you created earlier.
8. Left-click the space to the left of the LED Test to set a breakpoint on that test. A red stop icon
appears, as shown below, to indicate the breakpoint.

Figure 1 Breakpoint Set

9. Click the Run button on the sequence editor toolbar. This executes the sequence using the Test
UUTs Execution entry point.
10. Enter any number into the UUT Information dialog box and click OK.
11. Notice that the execution pauses at the first breakpoint, in this case, the LED Test, because you
inserted a breakpoint at this step. The step into, step over, and step out debugging tools should be
enabled on the toolbar.

12. Click the Step Over button to move to the next step.

13. Click the Resume button to continue execution.

14. Before the execution completes, click the Terminate button to terminate the execution and
display the results of all steps executed in the report. If your execution reaches the UUT Result dialog
before you have a chance to terminate, start a new UUT and then terminate the execution.
15. Click Terminate in the Testing Terminated for Current UUT dialog box that launches.
16. Close the report and return to the Sequence File window.

Exercise 6B: Stepping into a Code Module

1. Click Run to run the sequence again. Enter any number in the UUT Information dialog box.

2. When the execution pauses at the LED Test step, this time press the Step Into button .
3. Notice how the LabVIEW VI LED Test.vi has now opened. Change to the block diagram by
selecting Window»Show Block Diagram.
4. Right-click on the wire between the Divide VI and the Add VI. Select Set Breakpoint to set a
breakpoint.

Figure 2 Set a Breakpoint in LabVIEW

5. Click the white Run button in LabVIEW to execute the code module. Notice that the LabVIEW
code breaks at the breakpoint you set.
6. Move the mouse cursor over the wire to see the pointer change to a Probe icon. Clicking on the wire
will allow you to see the value at this point during run-time.

7. Click the red button labeled Continue , to continue execution of the code module.
8. Once the LabVIEW code module has finished executing, right-click on the breakpoint you set and
select Clear Breakpoint.

Figure 3 Clearing a Breakpoint

9. To return execution to TestStand, press the black Return to caller button .

10. When the focus returns to TestStand, press the Resume button to finish the TestStand execution.
11. Close the report and the sequence file. Do not save.

End of Exercise 6
Exercise 7: Integrating Switching into the Sequence Using
NI Switch Executive
Objective: To add switching to each step such that the appropriate instruments connect to each
component on each device under test (DUT). In this exercise, you will make use of the integration of NI
Switch Executive in NI TestStand.
Additional Information: NI Switch Executive is an intelligent switch management and routing
application. You can interactively configure and name switch modules, external connections, and signal
routes using a graphical end-to-end route editor. This means you can preconfigure routes or autoroute
signal endpoints on the switch. This exercise illustrates configuring a TestStand step to automatically
perform the switching operations for the step based on a configuration created in NI Switch Executive.

Exercise 7: Add Switching to the Audio Quality Test Step

1. Follow these steps to make a working copy of the sequence that you created in the previous exercise.
a. Open Ex 5 - Complete Handheld Test.seq in your Exercises folder.
b. Select File»Save As….
c. Name the sequence Ex - 7 Switching.seq and click Save.
2. The following steps will show you how you can specify which switch routes to connect when
executing the Audio Quality Test in your sequence.
a. Click on the Audio Quality Test step to highlight it. This will automatically populate the
Step Settings pane at the bottom of the sequence editor
b. Select the Properties tab to open the Step Properties dialog box for the step as shown in the
next figure.

Figure 6 Step Settings Pane

c. Click the Switching option on the properties group list and the Step Setting pane will
populate as shown in the next figure.

Figure 2 Step Settings Pane Showing Switching Properties

d. To set the switching configuration for the step, check the Enable Switching check box.
e. Select HandheldDeviceSwitch from the Switch Executive Virtual Device ring control.
Now that you have selected the HandheldDeviceSwitch virtual device, all of its routes
and route groups are available for you to use. To test ONLY the filter on DUT0, the route
group that you want to use is AudioQualityDUT0. You could simply select that route as
the Route(s) to Connect and this test will work fine for one DUT.
But ultimately this sequence will need to be able to test multiple DUTs, and selecting a
“static” route doesn’t offer the scalability that you need when you want to use this same
sequence to test multiple DUTs. Therefore, with the end result in mind, you will add this
route using an expression so that the route used during the step will change for the DUT
being tested.
f. Click on the f(x) button next to Route(s) to Connect to open the Expression Browser and
type the following expression.
“AudioQualityDUT” + Str(RunState.TestSockets.MyIndex)

Figure 3: Expression for Audio Quality Test Switch Route in Expression Browser Dialog Box

This expression is used because the switch route now depends on one thing: the DUT being
tested. All of the possible path combinations have already been pre-defined in the virtual device:
AudioQualityTestDUT0, AudioQualityTestDUT1, AudioQuailtyTestDUT2, and
AudioQualityTestDUT3.
RunState.TestSockets.MyIndex is the index of the current execution in TestStand which equates
to the DUT to be tested. Remember, this expression is used in anticipation of the next exercise in
which multiple DUTs will be tested.
g. Click OK to return to the Sequence Editor.
h. The Connection Lifetime is set to Manual which means that the route will disconnect
whenever you do so in another step.
i. Set the Connection Lifetime to Step which disconnects the routes when the step completes.
 Figure 4 Audio Quality Test Properties for Switching

j. Observe the changes in the MainSequence. If you receive an Evaluation or Syntax Error,
return to the Expression Browser to determine and correct the problem. Notice that the Audio
Quality Test step now has a “Switch” listed in the Flow Properties column.

Figure 5 Switch Configured for Audio Quality Test

3. Run and save the sequence to guarantee that the sequence is executing correctly.
a. Select File»Save.
b. Click on Execute»Single Pass.
c. The sequence should execute just as it did before. This is because, much like we are using a
simulated digitizer, we are using a simulated switch in this exercise.
d. In future exercises we will see how this switching configuration will be able to scale to test
four different handheld devices.
4. Close the sequence by selecting File»Close.
You have successfully added switching to the Audio Quality Test.

End of Exercise 7
Exercise 8: Performing Auto Schedule Parallel Testing
Objective: To test the handheld device in parallel using the TestStand Batch Process Model and Auto
Scheduling.

Exercise 8A: Add a Subsequence to the Test Sequence

In this exercise, you will add a subsequence. Subsequences allow you to modularize portions of a
sequence into smaller sequences that are easier to manage and maintain. Breaking up a sequence file into
manageable segments is similar to how a program developer breaks up sections of a program into separate
functions. Each smaller segment has a very specific purpose and contributes some basic functionality to
the calling sequence. Like functions, subsequences can be called by any sequence. This reusability and
modularity make subsequences very handy.
1. Follow these steps to make a working copy of the sequence that you created in the previous exercise:
a. Open Ex 5 - Complete Handheld Test.seq in your Exercises folder.
b. Select File»Save As….
c. Name the sequence Ex 8 - Autoschedule Handheld Test.seq and click Save.
2. Now you will create a subsequence to contain the Volume Test and Audio Quality Test steps. Adding
a subsequence to this exercise isn’t necessary to test multiple handheld devices; however, it is
included to provide you with a better understanding of how subsequences can help you create
modular, reusable sequences.
a. You can view all of the sequences that are included in the sequence file in the Sequences
pane in the TestStand Sequence Editor.
b. To create another sequence, right-click in the sequence pane and select Insert Sequence from
the context menu.
 Figure 7 Insert Sequence
c. Name this sequence Audio Test Sequence.
Now that you have created the subsequence, you will need to move the Volume Test and Audio Quality
Test steps from the MainSequence into the subsequence.
d. Select MainSequence in the Sequences pane.
e. To move the desired steps to the subsequence, click on the Volume Test step, press and hold
<Shift> and then select the End step below the nested If block. Release the <Shift> button
and right-click on the highlighted group and select Cut.

Figure 8 Cut Audio Steps from MainSequence

 f. Select Audio Test Sequence in the Sequences window.
g. Right-click on <Insert Steps Here> in the Main step group and select Paste from the context
menu. This will insert the steps into the Main step group. When this subsequence is called by
other sequences, it will execute the Volume Test and the Audio Quality Test.

Figure 9 Paste Audio Steps in Subsequence

3. Now that the Audio Test Sequence is finished, you will need to call this new subsequence from the
MainSequence.
a. Select MainSequence from the Sequences pane.
b. Drag and drop a Sequence Call step from the Insertion Palette into the MainSequence under
the LED Test and rename it Call Audio Test Sequence.
 Figure 4 Selecting Sequence Call
c. Click on Call Audio Test Sequence. The step properties pane will update and allow you to
specify a sequence to call.
d. Click on the Module tab and enable the Use Current File checkbox and change Sequence to
Audio Test Sequence.

Figure 5 Edit Sequence Call

4. Now that you have successfully added a subsequence for the Audio Test Sequence to your main test
sequence, select Execute»Single Pass to run your test sequence.
Note: You may be asked if you want to “Save all the sequence files before running?” Click Yes.
Exercise 8B: Add Auto Scheduling and Configure the Batch Process Model
In this exercise, you will add the Auto Schedule step type to the MainSequence. When you add the Auto
Schedule step type, it includes an Auto Schedule Resource. An Auto Schedule Resource performs two
functions. First, it provides a lock around the included steps. This means only one thread can execute the
steps at a time. Second, it identifies a blocks of steps that can be executed in any order to increase the
utilization of instrumentation and throughput of the test system.
1. Configure the Audio Test Sequence as an Auto Scheduled Resource.
a. Drag and drop an Auto Schedule step from the Insertion Palette under the Synchronization
folder to the MainSequence under the LED Test step.
b. Rename the Use Auto Scheduled Resource step to Auto Schedule Scope Resource.
c. Select the Audio Test Sequence sequence call step and drag it between the Auto Schedule
Scope Resource step and its corresponding End step to insert this step as an Auto Scheduled
Resource. You can tell the step each End corresponds to by matching the line that runs from
the step to the end step.

Figure 6 Adding Auto Scheduled Resource

 d. Click the Auto Schedule Scope Resource step again. The step settings pane should update and
the Auto Scheduled Resource Settings tab should appear. Click the Auto Scheduled Resource
Settings tab.
e. In the Resource Lock Alternatives field, enter the following string including quotes: “Scope”

Figure 7 Configure Use Auto Scheduled Resource Step

2. Configure Bluetooth Wi-Fi as an Auto Schedule Resource.

a. Drag and drop a Use Auto Scheduled Resource step from the Insertion palette to the
MainSequence under the end from the Auto Schedule Scope Resource.

Figure 8 Adding Second Auto Scheduled Resource

b. Rename the Use Auto Scheduled Resource step Auto Schedule Bluetooth RF
Resource.
c. Select the Bluetooth Test step and drag it between the Auto Schedule Bluetooth Resource
step and its corresponding End step to insert this step as an Auto Scheduled Resource.
d. Click the Auto Schedule Bluetooth RF Resource step again. The step settings pane should
update and the Auto Scheduled Resource Settings tab should appear. Click the Auto
Scheduled Resource Settings tab.
e. In the Resource Lock Alternatives field, enter the following string including quotes:
“Bluetooth RF”
3. Configure the Wi-Fi RF and the Audio Test subsequence as Auto Scheduled Resources.
a. Drag and drop a Use Auto Scheduled Resource step from the Insertion palette to the
MainSequence under the end from the Auto Schedule Bluetooth Resource.
b. Rename the Use Auto Scheduled Resource step Auto Schedule Wi-Fi RF Resource.
c. Select the Wi-Fi Test step and drag it up to the End step directly below the new Use Auto
Scheduled Resource. This will insert it into the Auto Scheduled Resource resource.
d. Click the Auto Schedule Wi-Fi RF Resource step again. The step settings pane should update
and the Auto Scheduled Resource Settings tab should appear. Click the Auto Scheduled
Resource Settings tab.
e. In the Resource Lock Alternatives field, enter the following string including quotes: “Wi-Fi
RF”
4. The result should match the following figure. The following figure shows the results.

Figure 9 Completed Exercise 8 MainSequence

5. Now you will change the process model to the Batch process model.
d. Select Configure»Station Options and select the Model tab.
e. Use the Station Model drop-down to select BatchModel.seq.

Figure 10 Select Batch Process Model

f. Click OK to return to the sequence file.

6. Now that you have selected the Batch Process model, you will need to specify the total number of test
executions that will be performed in parallel on multiple sockets as a group.
a. Select Configure»Model Options.
b. Set the Number of Test Sockets to 4.
Note: Later you can try 1, 2, or 3 Test Sockets to see the results.

Figure 11 Model Options Dialog Box

c. Click OK.
7. Select File»Save.
8. Maximize the TestStand Sequence Editor window by clicking the Windows maximize button .
9. Select Execute»Single Pass to run the sequence file.

Figure 12 Batch Model Execution

10. You will see four windows pop up. TestStand will test the sockets in parallel. Each socket tests a
different handheld test.
11. When the test has finished, examine the Batch Report. To run another test, click Execute»Restart.
12. Close the Single Pass window by pressing the Close button on the window or selecting Window»
Close Completed Executions when you are finished.

End of Exercise 8
Exercise 9: Verify Requirements are Implemented in the
Test System Using NI Requirements Gateway
Objective: In this exercise, you will verify that all requirements of the test are implemented, add any
missing requirements and generate traceability reports.
Requirements traceability is a critical piece of verifying the implementation of requirements in a test
system. The process of requirements traceability can be very time consuming and error prone. A
requirements management and traceability can significantly facilitate the implementation of requirements
traceability and its accuracy. The Requirements Gateway interface is shown below.

Figure 1 Requirements Gateway Interface

Exercise 9A: The Requirements Document

17. Browse to the Exercises folder where you have been saving your exercises. Open the file Ex 9 -
Requirements Document.docx in Microsoft Word.
18. The requirements document lists all the customer’s requirements for testing your handheld device.
Look through the document and identify which tests you created and which steps you used code
templates.
Note: There are 10 requirements; however, you have only included 9 code module steps in your code.
19. Close the requirements document. Do not save.

Exercise 9B: Requirements Gateway

12. If you closed TestStand and the sequence you created in the last exercise, reopen it.
a. Open Ex 8 - Autoschedule Handheld Test.seq in your Exercises folder.
b. Select File»Save As and save a copy of the sequence file. Name the copy Ex 9 -
Final Handheld Test.seq.
13. Open Requirements Gateway by clicking on Start»Programs»National Instruments»
Requirements Gateway [version number]»Requirements Gateway.
14. Create a new Requirements Gateway project by selecting File»New. Name the new project Ex 9 -
Handheld Test.rqtf.
15. Add the requirements document to the project.

a. Click the Add a Document button

b. Add the document to the project by clicking in the Traceability Description Zone.

Traceability
Description
Zone

Figure 2 Adding a Requirements Document

c. Click in the Name category and rename the document Requirements Document.
d. Under the Type of Analysis category, select WordX from the drop-down list.
 e. Under the File or Directory category, browse to the Exercises folder where you have
been saving your exercises. Open the file Ex 9 - Requirements Document.docx.
This is the requirements document we opened earlier.
16. Add the TestStand sequence to the project.
a. Click the Add a Document button.
b. Add the document to the project by clicking the traceability description zone.
c. Click in the Name category and rename the document Handheld Test.
d. Under the Type of Analysis category, select TestStand from the drop-down list.
e. Under the File or Directory category, press the browse button. This will make the Select
Files to Include in Document dialog appear.
f. Click the Add Sequence File button to add the sequence file we created in the last
exercise to the project. Requirements Gateway will automatically place you in your
current project directory. Browse to the Exercises directory and select Ex 9 - Final
Handheld Test.seq.

Figure 3 Add a Covering Document

g. Click OK to add the sequence file to the project.

17. Select the Add a Cover tool . Draw the cover arrow from the TestStand document to the
requirements document, by clicking on the TestStand document and then on the requirements
document. Adding a cover document creates a link between the TestStand sequence file and the
Requirements Document. By dragging the arrow from the TestStand document to the Requirements
 document, we are saying that the Handheld Test implements the requirements from the Requirements
Document. The result is shown in the figure on the next page.

Figure 4 Add a Cover

18. Click OK to exit the configuration dialog. Select Yes if Requirements Gateway asks you to reanalyze
the project.
19. Look at the requirements in the Requirements Gateway Management View to learn more about the
requirements coverage in your project.

Figure 5 Requirements Gateway Management View

a. Click the + sign next to Requirements Document to see the sections of the document.
b. Click the + sign next to 2 Handheld Test Requirements to see all of the requirements that
have been loaded into the Requirements Gateway through the requirements document.
 Note: The black requirements are covered while the red requirements are not covered.
Note that one of the uncovered steps is the Audio Quality Test which you implemented in
an earlier exercise. To update this list, we must link our test to a requirement.
Note: The requirements for the other TestStand steps were added to the template
previously.
20. Insert the requirement into TestStand.
a. In Requirements Gateway, left-click on the REQ_Audio : Audio Quality Test. Then
right-click and select Copy For»TestStand Requirements List.
b. Switch to the TestStand Sequence Editor. Right-click in the main sequence window on
the Step column header and select Step List Configurations»Requirements. This will
add a Requirements column in the Sequence Editor.
c. Select Audio Test Sequence in the Sequences pane. Then select the Audio Quality Test
step.
d. The Step Settings pane will automatically update with the Audio Quality Test’s
properties. Select the Properties tab and the Requirements property.
e. Click on <insert new item> to edit the Requirements list. Select Edit»Paste to paste the
requirement ID in the field.

Figure 6 Adding Requirement to Audio Quality Test

f. Save the sequence file.

g. Observe that all other tests in the Sequence have requirements coverage information
documented under the Requirements field of the Step pane.
h. Switch back to Requirements Gateway.
21. Requirements Gateway will automatically analyze which requirements are covered by the sequence
file and which requirements are not covered. Select Yes if Requirement Gateway asks you to reload
the file.
22. The total percentage of coverage is shown in the top right corner of the main window in the
Management View. Currently the coverage is at 90%.
23. In the Rules Check dialog, you will be able to see all of the uncovered requirements.
a. Click the + next to Rule Check to expand the rules.
b. Click the + next to Uncovered requirement to expand the list of uncovered requirements.
c. Requirements Gateway analyzes all of the requirements and automatically filters the list
of requirements to display Uncovered requirements. Uncovered requirements are
requirements that are not met in their covering document. In this case the REQ_LCD
requirement is not covered.
24. Implement the LCD Test to cover the missing requirement.
a. Switch to the TestStand Sequence Editor. Select MainSequence in the Sequences dialog.
b. Drag the LCD Test template underneath the Audio Test Sequence Call.
c. Select Requirements under the Step Settings dialog. Verify that REQ_LCD is listed.
d. Save the sequence file.
25. Switch back to Requirements Gateway and click Yes if Requirements Gateway asks you to reload the
file. Notice that you now have 100% coverage.
26. Click the Coverage Analysis View tab. This view shows how each requirement is met both upstream
and downstream.
a. Click the + next to Requirements Document to expand the requirements document
sections.
b. Click the + next to 2 Handheld Test Requirements under the Requirements Document to
expand the requirements listed in the document.
c. Select the first requirement, REQ_Initialize, to see the downstream coverage information
in the Downstream Coverage Information window. You can see that the step Initialize
Instruments in the Setup step group meets this requirement.
d. Click the + next to Handheld Test in the Selection window to expand the TestStand
sections.
e. Click the + next to Ex 9 – Final Handheld Test.seq to expand the sequence file properties.
f. Click the + next to MainSequence to expand the step groups in the main sequence.
g. Click the + next to Main Steps to expand the steps within the main group.
h. Click on the LED Test step to see the upstream coverage information pointing to the
requirement that this step meets in the Upstream Coverage Information window.
27. Switch to the Graphical View to visually see how the requirements map to the tests within TestStand.
The lines between the requirements document and the coverage document show when requirements
are covered by tests in the sequence file.
28. Create a Traceability Matrix report using Requirements Gateway.
a. Switch back to the Management View tab.
b. Select Reports»Library Reports»Traceability Matrix.
c. In the main window, <Ctrl-Click> Requirements Document and Handheld Test. Then
press the Continue button.
d. In the resulting Save As dialog, save the file as Ex 9 - Traceability Report.rtf
in your Exercises folder.
e. A new Microsoft Word document will appear with the Traceability Matrix created.
f. When you are finished looking at the document, close Microsoft Word and return to
Requirements Gateway.
Save the Requirements Gateway project and close Requirements Gateway.
End of Exercise 9
Exercise 10: Test Handheld Device Using an NI TestStand
Run-Time Operator Interface
Objective: To run a test sequence file from the operator interface and view reports that TestStand
generates.
In addition to the sequence editor application to execute a test in the previous exercise, you can also use
the operator interface to execute tests. The operator interface in this exercise is built with LabVIEW and
is the interface the operator uses on the production floor. The operator interface is similar to the sequence
editor because it has most of the same functionality. The operator interface and the sequence editor have
the following differences:
 The sequence editor can modify or create sequence files. The operator interface cannot modify or
create sequence files.
 You cannot modify the sequence editor because the source code is not provided. Because the
source code for the operator interface installs with TestStand, you can modify the code and create
a customized operator interface for every user.
20. Browse to Automated Test Software Hands-On\Exercises\Operator Interface\
Ex 10 - Custom OI.exe to open the operator interface.
21. After the LabVIEW Operator Interface loads, the Login dialog box displays. Select the default,
administrator, from the User Name control and leave the Password text box empty.
22. Click OK in the Login dialog box.
23. The Sequence File window opens in the operator interface. Select Open Sequence File and open the
Ex 9 - Final Handheld Test.seq file from the Exercises folder. Figure 1 shows the
sequence file displayed in the operator interface.

Figure 1 LabVIEW Operator Interface

24. Click Single Pass to execute the sequence.

25. The Sequence File and Execution windows are separate views of the same program in the operator
interface. The Sequence File window displays all information related to the sequence file(s) currently
loaded into memory including the sequence filename, the current logged-in user, and the steps in the
sequence. The Execution window displays all the information related to the execution of a sequence
file including the status of each step in the sequence file, which sequence is running, and the sequence
report contents. Click the name of either view in the left pane of the operator interface to bring it to
the front and display its contents.
26. Click the Report tab in the Execution window to display the report.

Figure 2 Operator Interface Report

27. Select Close Execution.

28. Select Exit to close the operator interface.

End of Exercise 10