Because of the popularity of instrument drivers and the flexibility of the user interface, many developers are using LabWindows/CVI to build automated test systems. The Test Executive Toolkit is an add-on product for these users that can save significant development time for these developers.
The Test Executive Toolkit is a ready-to-run test management system for creating and executing test sequences, logging test results, and setting test-run dependencies. When you use the Test Executive, you can concentrate on developing test sets, and leave the test management details to the Test Executive.
!
BEGIN_TEXT
!
Test Executive Overview
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
1
1875
3360
5160
2070
0
0
0
0
BEGIN_TEXT
The Test Executive has three-level, password-protected access - developers have complete access for creating test sequences and setting test-run conditions, while operators have limited access to load and run test sequences.
!
BEGIN_TEXT
!
Test Executive Overview
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
2
4605
4110
5160
2070
0
0
0
0
BEGIN_TEXT
The Test Executive Toolkit is shipped with source code so you can customize portions of the program to fit your particular needs. Common areas that users customize include the login procedures, the report generation format, and the operator interface.
!
BEGIN_TEXT
!
Test Executive Overview
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
3
2280
4320
5175
2430
0
0
0
0
BEGIN_TEXT
The Test Executive is currently in operator mode - you are limited to loading and running test sequences only. A sample test sequence for testing a computer has been loaded at left. As an operator, the only control that is active for you to use is the Test UUT button.
Press the Test UUT button to execute the computer test sequence.
!
BEGIN_TEXT
!
Running a Test Sequence
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
ARR_U1R.BMP
ARR_U1_.BMP
389
37
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
5
4680
345
5310
2025
0
0
0
0
BEGIN_TEXT
When you test a UUT, the Test Executive runs the test sequence continually and prompts you for serial numbers for each UUT tested.
Press the arrow and we will assign a UUT serial number.
!
BEGIN_TEXT
!
Running a Test Sequence
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
6
4680
345
5205
1575
0
0
0
0
BEGIN_TEXT
Press the OK button to run the test sequence for UUT number 2133.
!
BEGIN_TEXT
!
Running a Test Sequence
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
8
4680
345
5475
2100
0
0
0
0
BEGIN_TEXT
The test sequence passed! As you can see behind the pass banner, each test was executed and a pass indication has been displayed in the Sequence Display.
Press the OK button to continue.
!
BEGIN_TEXT
!
Running a Test Sequence
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
10
4680
345
5475
2100
0
0
0
0
BEGIN_TEXT
Each time you execute a test sequence, the Test Executive automatically stores the sequence results in a report file. At any time you can review the report file.
Pull-down the Report menu and select View.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
14
2010
600
3810
3030
0
0
0
0
BEGIN_TEXT
The report file has been displayed in the Test Display box to the right. The report is a simple ASCII text file showing each test and its results. Many customers customize the report file to fit their own company formats or to add additional information about each test, sequence, or UUT.
Press the arrow to continue.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
16
1425
3450
5160
2490
0
0
0
0
BEGIN_TEXT
Now you are logged in to the Test Executive as a technician. As you can see, technicians have access to more test execution and debugging tools. As a technician, you can run an entire sequence once to test it, run a single test, or loop on a test for debugging purposes.
Press the arrow to continue.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
17
1425
3450
5205
2325
0
0
0
0
BEGIN_TEXT
As a technician, you can tune the Test Executive to store or display specified test information only. For example, you may not want to see any test results on the screen or in the report file for tests that pass - you may want to only save test information for tests that fail.
Pull down the Report menu and select Screen.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
21
2985
495
5160
1605
0
0
0
0
BEGIN_TEXT
From the Report menu, you can select which test results are displayed on the screen or sent to the report file.
Now select the Test menu.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
23
1935
3810
5145
2505
0
0
0
0
BEGIN_TEXT
Many times, you may need to force tests to pass or fail to test different branches in your test sequence. As a technician, you can force tests to pass, fail, or skip from the front panel of the Test Executive using the Test menu. This makes sequence testing and debugging much easier.
Press the arrow to continue.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
26
2160
570
5295
2715
0
0
0
0
BEGIN_TEXT
Now you are logged in as a Developer. The operator interface for developers is the same as for technicians - you can run individual tests, loop on tests, control the information displayed or stored, and force tests to pass or fail. The difference between developer and technician status is that developers can edit or create new test sequences.
Pull-down the Sequence menu and select Edit Sequence.
!
BEGIN_TEXT
!
Viewing the Report File
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
ARR_U1R.BMP
ARR_U1_.BMP
49
104
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
30
3165
1230
5295
2715
0
0
0
0
BEGIN_TEXT
This is the sequence editor. From the sequence editor, you can build or edit test sequences. The window above shows each test in your sequence. You can cut, copy, and paste tests using the buttons on the right to rearrange your test sequence. Each test is actually a C function created in LabWindows/CVI. In this example, all of the computer tests are stored in the computer.obj file.
!
BEGIN_TEXT
!
The Sequence Editor
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
31
675
600
5295
2715
0
0
0
0
BEGIN_TEXT
You can add tests to the sequence by entering information in the controls below. As you can see, each test has a name, a C function name, and a file in which it is located. The test executive dynamically loads each test from the test systems hard drive during sequence execution. Therefore, you can store hundreds of test files on a particular test station, and each test sequence simply specifies which files to load and run for a particular UUT.
!
BEGIN_TEXT
!
The Sequence Editor
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
32
1185
1710
7035
2850
0
0
0
0
BEGIN_TEXT
For each test, you can specify setup and cleanup routines to be executed before and after the test is run. You may have to configure hardware setups or clear memory locations before and after running a test. You can do these operations in your setup and cleanup routines to keep your test code pure.
You can also set run options for each test to determine what should happen when after the test runs. The default action is to continue on to the next test. However, you can specify that a test loops a certain number of times if it fails, or to halt sequence execution if a test fails.
!
BEGIN_TEXT
!
Test Setup/Cleanup and Run Options
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
ARR_D1R.BMP
ARR_D1_.BMP
299
293
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
33
1185
1710
7035
2850
0
0
0
0
BEGIN_TEXT
Each test is designed to return a measured value to the test executive. You can use the test executive to evaluate the result and determine if the test passes or fails. For more complex tests, you can make the evaluation in the test itself and pass back a PASS of FAIL result to the test executive.
Press the Set Limits button to see some of the different ways that you can evaluate test results using the test executive.
!
BEGIN_TEXT
!
Test Limits
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
ARR_L1R.BMP
ARR_L1_.BMP
309
254
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
35
4605
3570
5250
2160
0
0
0
0
BEGIN_TEXT
From this dialog, you can specify values to determine if a test passes or fails. In this example, the test will pass if the measured result returned is equal to zero.
Click on the Comparison Type to see the different test evaluation criteria available in the test executive.
!
BEGIN_TEXT
!
Test Limits
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
37
2190
6135
2685
1950
0
0
0
0
BEGIN_TEXT
Choose GTLT to setup a range of values that the test result must fall between to indicate a PASS.
!
BEGIN_TEXT
!
Test Limits
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
39
3420
6045
2685
1950
0
0
0
0
BEGIN_TEXT
Now the test must return a value between zero and one to be evaluted as a PASS.
Press the OK button to continue.
!
BEGIN_TEXT
!
Test Limits
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
41
2595
4605
4125
2865
0
0
0
0
BEGIN_TEXT
From the Sequence Attributes section of the sequence editor, you can specify setup and cleanup routines to be run before and after each sequence is executed. You can also specify a description for the sequence, which is placed into the report file, and you can specify a file name and attributes for the Report file.
Press the arrow to continue.
!
BEGIN_TEXT
!
Sequence Attributes
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
-1
3
0
0
TESTEX.AVI
0
42
2685
525
4125
2865
0
0
0
0
BEGIN_TEXT
Once you have specified a sequence of tests in the sequence editor, you then must specify test-run dependencies. A test dependency is a set of conditions that must be true in order for the test to be executed.
Press the Test Preconditions to setup some test-run preconditions.
!
BEGIN_TEXT
!
Test Preconditions
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
ARR_D1R.BMP
ARR_D1_.BMP
368
61
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
-1
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
44
2535
2880
4125
2865
0
0
0
0
BEGIN_TEXT
Your test sequence is shown at the right in the Tests display. The preconditions for each test is shown in the Preconditons display above. In this example, the Power On test has no preconditions; therefore, it will always run.
Click on the ROM Diagnostics test to view its preconditions.
!
BEGIN_TEXT
!
Test Preconditions
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
ARR_L1R.BMP
ARR_L1_.BMP
155
144
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
46
2535
2880
4125
2865
0
0
0
0
BEGIN_TEXT
The ALL OF indicates a logical AND in the condition statement. Therefore, before the ROM Diagnostics test will run, the Power On test must PASS AND the ROM test must FAIL. You can also add logical OR statements to your conditions.
Press the Add Any Of button to add an OR condition to your preconditions statement.
!
BEGIN_TEXT
!
Test Preconditions
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
48
2850
3480
4215
1560
0
0
0
0
BEGIN_TEXT
Now press the Add Condition... button to add some test conditions under the ANY OF entry.
!
BEGIN_TEXT
!
Test Preconditions
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
50
5040
3030
4215
1920
0
0
0
0
BEGIN_TEXT
You are presented with a list of the tests in your sequence. Choose the Video and Keyboard tests by clicking on them with your mouse.
!
BEGIN_TEXT
!
Test Preconditions
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
54
5040
3030
4320
1560
0
0
0
0
BEGIN_TEXT
Now change the condition for the Keyboard test from PASS to FAIL with the Type switch and press the OK button.
!
BEGIN_TEXT
!
Test Preconditions
0
0
0
0
255
255
255
255
0
0
0
0
0
0
255
255
255
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
8
~~
~~
0
0
0
0
0
3
3
0
3
0
-1
TESTEX.AVI
0
58
2880
2220
5130
3720
0
0
0
0
BEGIN_TEXT
Now the conditions for the ROM Diagnostics test to run are as follows: Power On must PASS, ROM must FAIL AND either the Video must PASS OR the Keyboard must FAIL. As you can see, you can set up very complex test sequences and preconditions with the test executive.
The Test Executive Toolkit gets you a long way toward a complete test management system. Since the source code is provided, you can customize the ready-to-run test executive application to meet your specify needs and finish the job. In addition, database storage options for the test executive are available through the SQL Toolkit. Refer to the SQL Toolkit section for more information.
