At Easy 8 Test Executive

ATEasy Test Executive, Profile & Fault Analysis

User's Guide Generated: Feb 13, 2012 (v8). Copyright 2012 Geotest Marvin Test Inc. All rights Reserved.

v

Table of Contents Test Executive On-Line Help ........................................................................................................................ 1

Getting Started .............................................................................................................................................. 3

Getting Started .......................................................................................................................................... 3

Overview .................................................................................................................................................... 3

TestExec Modes, Modal and Modeless .................................................................................................... 5

Starting the Test Executive Application ..................................................................................................... 6

Touch Panel Support ................................................................................................................................. 6

Main Window - Modeless and Modal TestExec Mode .............................................................................. 7

Selecting a Program or a Profile ............................................................................................................. 10

Running ................................................................................................................................................... 12

Setting Conditions for Run....................................................................................................................... 12

Test Log ................................................................................................................................................... 13

Customizing the Test Executive Main Window ....................................................................................... 14

Example : Run Selection Level ............................................................................................................ 14

Working with Multiple Users .................................................................................................................... 15

Working with Profiles ............................................................................................................................... 15

Using the Fault Analysis .......................................................................................................................... 17

Maintaining Log Files ............................................................................................................................... 18

External Program Executables Support .................................................................................................. 20

TestExec Driver Shortcut - ExternalProgramINI Parameter ................................................................ 21

External Programs Configuration File Format ..................................................................................... 21

Example for External Programs Configuration File ............................................................................. 22

External Program List Editor dialog - create/edit/view the External Programs Configuration File ...... 22

Multiple UUTs and Parallel Testing Support ........................................................................................... 24

ATEasy Test Executive, Profile & Fault Analysis User's Guide

vi

Multiple UUT program Selection Examples ......................................................................................... 24

Example 1: Sequential Mode UUTs ................................................................................................. 24

Example 2: Mixed Mode UUTs ........................................................................................................ 24

New Features in the Test Executive to Support Multiple UUTs........................................................... 24

Steps Requires to Support Multiple UUTs in the Test Executive ........................................................ 25

Changes to Your Application Code to Support Multiple UUTs ............................................................ 25

Menus, Commands.., and Dialogs .............................................................................................................. 27

Test Executive Menu, Commands and Dialogs ...................................................................................... 27

Commands .............................................................................................................................................. 27

Test Executive Commands .................................................................................................................. 27

Program Commands ............................................................................................................................ 28

Program Commands ........................................................................................................................ 28

Select... Command (Program Command) ....................................................................................... 28

Program Selection Command (Program Command) ....................................................................... 28

External Programs... Command ....................................................................................................... 29

Edit Profile... Command (Program Command) ................................................................................ 29

Select Profile... Command (Program Command) ............................................................................ 30

Open Profile Command (Program Command) ................................................................................. 30

Edit Faults... Command (Program Command) ................................................................................. 31

Analyze Faults... Command (Program Command) .......................................................................... 31

Perform Fault Analysis At End Command (Program Command) .................................................... 31

Exit Command .................................................................................................................................. 31

View Commands .................................................................................................................................. 32

View Commands .............................................................................................................................. 32

Menu Command (View Menu) ......................................................................................................... 32

Table of Contents

vii

Log Command (View Menu) ............................................................................................................ 33

ToolBars Menu Commands (View Menu) ........................................................................................ 33

Lines Bar (View Command) ............................................................................................................. 34

Tests Command (View Menu) .......................................................................................................... 34

Test Properties Command (View Menu) .......................................................................................... 34

Run Commands ................................................................................................................................... 35

Run Commands ............................................................................................................................... 35

Start Command (Run Command) .................................................................................................... 35

Start UUT Command ........................................................................................................................ 35

Reset Command (Run Command) ................................................................................................... 36

Abort Command (Run Command) ................................................................................................... 36

Abort UUT Command ....................................................................................................................... 36

Pause/Continue Command (Run Command) .................................................................................. 36

Current Task Command (Run Command) ....................................................................................... 36

Skip To Next Task Command (Run Command) .............................................................................. 36

Loop On Task Command (Run Command) ..................................................................................... 37

Current Test Menu Command (Run Command) .............................................................................. 37

Skip To Next Test Command (Run Command) ............................................................................... 37

Loop On Test Command (Run Command) ...................................................................................... 37

Conditions Commands......................................................................................................................... 38

Conditions Commands ..................................................................................................................... 38

Continuous Command (Conditions Command) ............................................................................... 39

Task By Task Command (Conditions Command) ............................................................................ 39

Test By Test Command (Conditions Command) ............................................................................. 39

Repeat Run Command (Conditions Command) .............................................................................. 39


viii

Repeat Task Failure Command (Conditions Command) ................................................................. 39

Repeat Test Failure Command (Conditions Command) .................................................................. 40

Select All Tests Command (Conditions Command) ......................................................................... 40

Clear All Tests Command (Conditions Command) .......................................................................... 40

Pause On Task Failure Command (Conditions Command)............................................................. 40

Pause On Test Failure Command (Conditions Command) ............................................................. 40

Prompt On Pause Failure Command (Conditions Command) ......................................................... 40

Pause At End Task Command (Conditions Command) ................................................................... 41

Pause At End Test Command (Conditions Command) ................................................................... 41

Pause Immediately Command (Conditions Command) ................................................................... 41

Log Commands .................................................................................................................................... 42

Log Menu Commands ...................................................................................................................... 42

Clear Command (Log Command) .................................................................................................... 42

Open... Command (Log Command) ................................................................................................. 42

Print Command (Log Command) ..................................................................................................... 42

Save As... Command (Log Command) ............................................................................................ 42

Log Freeze Command (Log Command) .......................................................................................... 43

Unfreeze Log At Start Command (Log Command) .......................................................................... 43

Serial Number Command (Log Command)...................................................................................... 43

Failures Only In All Log Command (Log Menu) ............................................................................... 44

Failures In Summary Command (Log Command) ........................................................................... 44

New Log Window Command (Log Command) ................................................................................ 45

Log Message Command (Log Command) ....................................................................................... 46

Close All Windows Command (Log Command) ............................................................................... 46

Log Files... Command (Log Command) ........................................................................................... 47

Table of Contents

ix

Tools Commands ................................................................................................................................. 49

Tools Commands ............................................................................................................................. 49

Users Command (Tools Command) ................................................................................................ 49

Change Password... Command (Tools Command) ......................................................................... 50

Change User... Command (Tools Command) ................................................................................. 50

Custimize... Command (Tools Command) ....................................................................................... 50

Options... Command (Tools Command) .......................................................................................... 50

Help Commands .................................................................................................................................. 51

Help Commands ............................................................................................................................... 51

Contents Command (Help Command) ............................................................................................. 51

Search... Command (Help Command) ............................................................................................. 51

Index... Command (Help Command) ............................................................................................... 51

About Test Executive Command (Help Command) ......................................................................... 51

Miscellaneous Commands ................................................................................................................... 51

Test Executive Options ............................................................................................................................ 52

Name ................................................................................................................................................ 52

Default Value .................................................................................................................................... 52

Possible Values ................................................................................................................................ 52

Description ....................................................................................................................................... 52

Dialogs ..................................................................................................................................................... 55

Test Executive Dialogs ........................................................................................................................ 55

Menus, Toolbars and Forms.................................................................................................................... 57

Menus .................................................................................................................................................. 57

Test Executive Menu ........................................................................................................................ 57

Program Menu .................................................................................................................................. 57


x

View Menu Popup ............................................................................................................................ 57

Run Menu Popup ............................................................................................................................. 58

Conditions Menu Popup ................................................................................................................... 59

Log Menu Popup .............................................................................................................................. 59

Tools Menu Popup ........................................................................................................................... 60

Help Menu Popup ............................................................................................................................. 60

Forms ................................................................................................................................................... 61

Test Executive Forms....................................................................................................................... 61

Test Executive Main Form ............................................................................................................... 62

Program Selection Form .................................................................................................................. 63

Program Form .................................................................................................................................. 64

View Form ........................................................................................................................................ 64

Run Form ......................................................................................................................................... 65

Conditions Form ............................................................................................................................... 66

Log Form .......................................................................................................................................... 67

Tools Form ....................................................................................................................................... 67

Help Form ......................................................................................................................................... 68

Run Log Form .................................................................................................................................. 69

Test Executive Tool Bars ..................................................................................................................... 72

Programming ............................................................................................................................................... 78

Programming the Test Executive Drivers ................................................................................................ 78

Adding the Test Executive drivers to your Project .................................................................................. 78

Test Executive ......................................................................................................................................... 79

Programming using the Test Executive Driver .................................................................................... 79

Test Executive Options ........................................................................................................................ 80

Table of Contents

xi

Test Executive Driver Parameters ....................................................................................................... 83

Adding Multiple Users Support (TestExec driver) ................................................................................ 84

Users file (.usr) ................................................................................................................................. 84

Test Executive Users File Data ........................................................................................................... 85

Touch Panel User Interface ................................................................................................................. 86

Test Executive Driver Commands ....................................................................................................... 87

Test Executive Driver Commands .................................................................................................... 87

Execution Commands (TestExec driver).......................................................................................... 87

Log Commands (TestExec driver) ................................................................................................... 92

Customize Commands (TestExec driver) ........................................................................................ 94

Utility Commands (TestExec driver) ............................................................................................... 103

Data Types ......................................................................................................................................... 108

Test Executive Data Types ............................................................................................................ 108

TestExec.enumAllowRunSelectionLevel Enum ............................................................................. 109

TestExec.enumBtnView Enum ....................................................................................................... 109

TestExec.enumCommandId Enum ................................................................................................ 110

enumCommandMember Enum ...................................................................................................... 114

TestExec.enumCommandShow Enum .......................................................................................... 115

TestExec.enumCommandType ...................................................................................................... 115

TestExec.enumHelpId Enum ......................................................................................................... 116

TestExec.enumLogFormat Enum .................................................................................................. 117

TestExec.enumLogType Enum ...................................................................................................... 117

TestExec.enumLogView Enum ...................................................................................................... 118

TestExec.enumOptionsMember Enum .......................................................................................... 118

TestExec.enumOptionsMember Enum .......................................................................................... 123


xii

TestExec/Profile.enumProfileActions Enum .................................................................................. 128

TestExec/Profile.enumProfileConditions Enum ............................................................................. 129

TestExec.enumRepeatTaskFailureLevel Enum ............................................................................. 130

TestExec.enumStatusLinePanes ................................................................................................... 130

TestExec.enumTestLogStyle Enum ............................................................................................... 131

TestExec.structCommand Struct ................................................................................................... 132

Profile ..................................................................................................................................................... 134

Programming using the Profile Driver ................................................................................................ 134

Profile Files ........................................................................................................................................ 135

Commands ......................................................................................................................................... 136

Profile Driver Commands ............................................................................................................... 136

Edit Command (Profile Driver) ....................................................................................................... 137

Select Command (Profile Driver) ................................................................................................... 139

Execute Commands (Profile Driver) ............................................................................................... 139

Get Commands (Profile Driver) ...................................................................................................... 139

Set Commands (Profile Driver) ...................................................................................................... 140

Utility Commands (Profile Driver) ................................................................................................... 140

Data Types ......................................................................................................................................... 142

Profile Data Types .......................................................................................................................... 142

Profile.structProfileItem Struct ........................................................................................................ 142

TestExec/Profile.enumProfileConditions Enum ............................................................................. 142

TestExec/Profile.enumProfileActions Enum .................................................................................. 143

Creating a Profile Programmatically .................................................................................................. 145

Fault Analysis ........................................................................................................................................ 146

Fault Analysis Driver Programming ................................................................................................... 146

Table of Contents

xiii

Condition Files ................................................................................................................................... 147

Example for condition file ............................................................................................................... 147

Commands ......................................................................................................................................... 150

Fault Analysis Driver Commands ................................................................................................... 150

Open Commands (Fault Analysis Driver)....................................................................................... 150

Close Commands (Fault Analysis Driver) ...................................................................................... 150

Analyze Commands (Fault Analysis Driver)................................................................................... 150

Dump Commands (Fault Analysis Driver) ...................................................................................... 151

Option Commands (Fault Analysis Driver) ..................................................................................... 152

Show Commands (Fault Analysis Driver) ...................................................................................... 153

Import Commands (Fault Analysis Driver) ..................................................................................... 154

Error Commands (Fault Analysis Driver) ....................................................................................... 154

Utility Commands (Fault Analysis Driver)....................................................................................... 154

Adding support to ATML Test Results ................................................................................................... 155

Index .......................................................................................................................................................... 157


xiv

1

Test Executive Users Guide

ATEasy applications can add Test Executive functionality by simply adding the TestExec.drv driver that is provided with ATEasy to the application system. The ATEasy test executive provides complete and customizable test executive that lets the test engineer run and debug a single or multiple test programs or profiles (test sequences). The user can also view, save and print test results to a test log in text or HTML format. The test executive driver is fully customizable using programming or its Customize dialog that offers support for customizing the menus and toolbar and user interface of the test executive. Refer to the Overview topic for a complete description of the TestExec.drv and its add-on drivers : Profile.drv, FaultAnalysis.drv and ATML.drv that provide test sequences, fault analysis to identify and recommend faults and solutions and ATML to export test results to ATML (xml) format.

This online help provides information on how to operate, use, program and customize the test executive, profile, and fault analysis drivers. This manual is for both audiences: the test station operators and the application programmers. It is divided into the following parts: Getting Started Provides basic information on how to operate the Test Executive to select a

program or select a profile, and to run and debug, and to view, save and print the test results. It also includes how to use Tools menu to customize its User Interface.

Menus, Commands, and Dialogs

Provides a reference to the Test Executive, Profile and Fault Analysis dialogs and the Test Executive menus and commands.

Programming Information regarding how to use these drivers from your application and how to change and customize the behavior of the Test Executive using programming statements (commands) exported by these drivers.

Copyright 19912012 Geotest - Marvin Test Systems, Inc. All Rights Reserved. Last Updated Jan 24, 2012.

3

Getting Started

Getting Started

The Getting Started help provides basic information of how to operate the test executive to select a program or a profile, run, debug it, then, view, save and print the test results in the log window and use the tools menu to customize its UI. The following topics are available:

Overview Modal and Modeless Modes Starting the Test Executive Application Touch Panel Support Main Window Selecting a Program Running Setting Conditions for Run Test Log Customizing the Main Window Working with Multiple Users Working with Profiles Using the Fault Analysis Maintaining Log Files External Program Executables Support (v7.0) Multiple UUT Support (v8.0)

To learn more see the Programming the Test Executive Drivers and the Menu and Dialogs books.

Overview

The Test Executive driver provides a complete and flexible user interface for ATEasy test applications. It allows you to select a program, display its tests in a tree view and let you select and run these tests. The Test Executive main window displays the test results of each program/task/test in the Log window. These results can be displayed in text format or HTML. They are displayed in two tab pages: one for all the test results and the other for the summary results. Optionally you can only display Failures in All Log window or include Failures to Log Summary. Optionally (v 7.0), you can hide the Log Summary. Clicking on individual test displays detailed test properties and scrolls the test log to display the results of that test.

Test Executive runs in two modes: Modal or Modeless. In the Modeless mode, the main window is the main TestExec window that includes all the menus and the rest on a single window and the user operates with mouse and keyboard. In the Modal mode, Test Executive supports Full Touch Panel User Interface environment where the user expects to operate without mouse or keyboard, but with 'Touch'. With this mode turned on, the user can use the TestExec driver in the Touch Panel UI environment: every window displayed in full screen with controls, mostly buttons, appropriately created and resized so that they can be operated with 'touch' instead of mouse/keyboard. For this, most of windows in the Modal mode are buttons' windows (forms), containing mostly button controls. The Modal main window starts with buttons that associate the top level TestExec menus. However, the buttons can be redefined and modified by


4

administrators via Tools, Customize, Forms (Single user) or via Tools, Users, Forms (Multi users) commands. Through a TestExec option, the user can freely move one mode to the other mode.

Test Executive also provides various run and debugging commands, options, and various run conditions commands (similar in ATEasy). For an example, Test Executive has a command (under Conditions) called Prompt On Pause Failure, which will prompt and allow to select one of four options: re-test or re-task, abort, continue or pause. You can choose which level, task or test, you want to check for failure (Pause On Task Failure, Pause On Test Failure). If the user makes a pause from running, TestExec allows to pause at the end of test or at the end of task, or immediately. You can also repeat the run continuously, or repeat test if fails and repeat task if fails. Many more debugging features are available.

The Test Executive main window (in Modeless mode), toolbar, menus and forms (for Modal Buttons' windows) can be customized using the Customize dialog (or Users dialog) or programmatically. Support for Touch Panel User Interface (the Modal mode) can also be enabled via an option - this option displays all windows in full screen with mostly button controls, allowing the user to operate the controls by touching with hands instead of using mouse and keyboard.

Test Executive provides support for multiple user environment. This provides more than one user privilege levels. If the multiple users support is activated, initially there are three default user groups defined, based on different levels of responsibility and different roles: Administrators, Supervisors, and Testers. Each group has a different level of privileges which can only be modified by an Administrator (who belongs to the Administrators group). The administrator can define a new user group, its privileges and its own custom user interface. Administrators can set the group user interface mode (Modal or Modeless), toolbar buttons, menus and options and what commands are available for each group and initial state or value of commands. User groups can be configured to provide different privileges for users across the network for multiple test stations or on a single test station.

Test Executive (v7.0) also supports a way to run External Programs. Unlike a typical project where all of your programs reside in one project, in this support, you create many individual projects, each including one or more programs, common system with a test executive in. The External Program Configuration INI file contains all relevant information necessary to run under this support. It starts with one executable and upon a program selection Test Executive loads the executable that containing the program and so on. Running programs under this support has valuable benefits, it allows you to send/add additional test programs in a modular manner without recompiling the exiting one, and this is extremely important for release management and will not require you to recertify existing programs every time a new program is added.

Test Executive (v8.0) support executing multiple program and profile at the same time. The user can set the number of UUT s he intend to run, assign a program or a profile to each and execute the programs / profiles. See the Multiple UUT Support for more information.

Three optional test executive add-on drivers: Profile.drv, FaultAnalysis.drv and ATML.drv can also be added to your application system for providing additional functionality. The Profile driver provides ways to create a profile which is a set of test sequences that are created from the application programs' tests and saved to a profile file. By selecting a profile from a file, you can run programs' tests in that particular sequence. The Fault Analysis driver allows you to create conditions that describe test results pattern identifying faults. Later, when the user runs the program, the results are analyzed and faults (if occurred) are displayed to the user, as well as the description of the problem and the repair instructions to fix the UUT. The ATML driver allow you to export your test results to ATML (xml) format.

Above all, Test Execute provides an easy-to-use, completely flexible user interface and powerful tools that facilitate effective testing environment for your ATE and functional test systems' applications.

Getting Started

5

TestExec Modes, Modal and Modeless

Test Executive supports two modes - Modal and Modeless. You can switch the mode by selecting the Modal or Modeless radio button using Tools\Customize\Options menu command (for single user) or Tools\Users\Options menu command (for multiple users).

By default, the test executive will start with Modeless Mode in which the main window will show a menu and a toolbar which will be used to select commands and operate the user interface with a keyboard and mouse. Once you switch to Modal mode, the main window will no longer displays a menu or a toolbar and instead a full screen forms that contains large buttons will be used to operate the test executive. These large buttons invoke commands similar to the menu or too bar commands however they are also convenient to operate by tapping on the screen with your fingers since they are larger as shown here:

The Modal mode supports the touch panel user Interface. This user interface is also simpler to operate since the user is presented with a small number of commands/buttons at a time. In this mode every operation can be performed with tapping on controls (mostly buttons) with your finger. That is, you can operate everything without ever needing to use keyboard and mouse. Since the user expects to use fingers in this mode, TestExec runs in a series of Buttons forms utilizing full screen where each control sized and created appropriately. The user can scroll using an enlarged scrollbar. When text need to be input the test executive will automatically displays an on screen virtual keyboard. Refer to the Touch Panel Support for more information.


6

The form buttons used by the Modal mode can be defined or modified via Tools\Customize\Forms in a single user Test Executive. In Multi Users case, an administrator can define or modify them for a group of users via Tools\Users\Forms.

By default, the main window in the Modal mode consists of mostly top level menus of buttons controls. If you select one of top level menus, it displays the next level buttons form, and so on. Each level form includes navigational buttons that allows you to go back to previous form or go back to main form or exit the Test Executive. They are located at the bottom part of the form. Refer to the Main Windows topic to learn about the different areas of the buttons form. Among the bottom buttons there is also a button called View Run/Log which allows you to view test results at any time in the log window, which is the main window of the modeless Test Executive.

Starting the Test Executive Application

With (Build\) Build of ATEasy menu command you can build the current active project that includes Test Executive drivers and other application files. An ATEasy application executable (.exe) will be created. When you execute (Build\Execute), the main window of with Modal or Modeless Mode will appear. If the application has support for multiple users the first window displayed before main the window is the Log In Dialog. If current user is the default user, the log In process will be bypassed. The default user can be set to a particular user through Tools\Users\Users dialog.

Touch Panel Support

Through Test Executive Modal mode, Touch Panel User Interface is available. Touch Panel Support means you can operate Test Executive in Touch Panel mode under which all the operations are performed via your finger by tapping on the screen and without using mouse or a keyboard.

The Touch Panel UI is accomplished via Test Executive Modal mode which employs a series of buttons forms. Button Forms are created during run according to their definitions. They start in the default settings. Their default settings can be changed and modified via Tools, Customize, Forms menu command (in Single User) or Tools, Users, Forms (for Multi Users). With these tools an ATEasy application programmer (and/or an administrator) can create a Touch Panel application for a group of users to run on the Touch Panel environment.

All the Test Executive and common dialogs are resized appropriately under this mode. Furthermore, the user input is accomplished by ATEasy AVirtualKeyboard class. Whenever a user input is desired (for example edit box has the focus), a virtual keyboard will appear as shown here and the user to enter input by tapping on the screen keyboard.

Getting Started

7

To activate the Touch Panel UI, open the Customize dialog, Options Page and check the Mode to Modal from Modeless.

Main Window - Modeless and Modal TestExec Mode

The TestExec main window in the modeless mode is as shown below. During this mode the main window will be displayed at all time and every operation is performed through this window. (In the modal mode of Test Executive, this window is called View Run\Log of which main windows are Log and Buttons Bar.) It contains many window panes. Except Log window and Status bar, they are optional; they can be set to Hide or Show (through View Menu or through changing mode, etc.) and at the end each state of windows (options) will be remembered so that it can be restored next time around. The full Modeless main window will include the following panes and windows:

Main Menus and Toolbar Pane - The menu and toolbars can be customized using the Customize(or Users)\Commands Dialog and the Customize(or Users)\Toolbar Dialog. In addition, if Touch Panel User Interface option is selected, then the large toolbar buttons will be displayed.

Lines Bar Pane - This pane contains up to two lines of information, which can be defined by the user. For example, by default the first line contains the current program (or profile) name and the second line displays the test status of the current program after its run. They can be set to other information via Customize(or Users)\Forms Dialog.

UUTs Tabs (v8) - When running Multiple UUTs, multiple UUTs tabs will be displayed one for each UUT. Each UUT hold the test pane and log window. Each tab will display the UUT name and a small image displaying the state of the UUT, Ready, Pause, Run. The images are colored to indicate the UUT status: None (black), Pass (green) or Fail (red).

Tests Tree View - displays the current Program or Profile tests to run. Check boxes next to each program/task/test indicate whether the item is included in the run or not. Unchecked item will be skipped. Check boxes can be disabled if they are not required (see Run Selection Level in the Customize(or Users) Options Dialog). During the run, the tree items are colored according to the status of the program/task or test. Clicking on a test or a task item in the tree will scroll the log window to the area where its test result is being displayed.

Test Properties Pane - displays the current test properties and status. The current test is the test highlighted in the tree view or one that currently being executed.

Log Window - Two pages of Logs: one for All and the other for Summary. This window contains the test results in text or HTML format (see Options Log Dialog).

Buttons Bar Pane (only in Modal) - contains buttons that can be defined or modified (as the Lines Bar pane) via Tools\Customize(or Users)\Forms Dialog. They can be any commands for


8

running or viewing. By default there are four different set of buttons displayed based on the state of run: Pre-run, During Run, Pause Run, and Post Run. In most cases, it should include one of buttons that allows to go back to previous or main form such as "Back", "Main".

Status Bar Pane - The status bar contains information regarding the active UUT tab. It contains the following fields:

o Status message, or selected menu item or toolbar button description. o Progress bar showing the progress of tests running. o Conditions mode image (Test by Test, Task By Task or Continuous) o Pause mode image (pause on Task failure or Pause on Test Failure) o UUT Status and number of fails (e.g. 'Fail (4)'). Color also indicates the status. o Run state: Ready, Run or Pause o Current Task/Test number o Elapsed time since start (Optional)

The following window shows a typical Modeless TestExec main window where every pane shown except Lines Bar Pane:

Getting Started

9

The TestExec main window in the modal mode is as shown below. It is a buttons form which mainly containing all the Test Executive top level menu available as buttons. It contains also several window parts and panes.

Lines bar - this contains up-to two lines of information. They can changed via Tools\Customize(or Users)\Forms.

Main buttons - they are main buttons. They can be also changed via Tools\Customize(or Users)\Forms.

Buttons Bar - These buttons consists of those that are used by all buttons forms: "Back", "Main", "Run Log", "Exit", "Help". These can be also changed via Tools\Customize(or Users)\Forms.


10

Status bar - they are used the same way as Modeless mode - please refer to the above.

Selecting a Program or a Profile

The test executive application can be setup with multiple programs, folders and profiles. Program Folders of ATEasy allow you to create tree structure of programs. The test executive have several ways of selecting programs or profiles:

Form the Program menu , select the Select... menu item. this will open the Select Program/Profile Dialog allowing you to select program or a profile from a list.

From the Program menu, select one of the programs or profiles (v8). This will select and load the selected menu program or profile.

When using touch panel/modal user interface, clicking on the Programs... button from the Main Form will open the Program Selection Form. The Program Selection Form display a list of available program and folders and in addition in the button you can also click on the Program... button to open the Select Program/Profile Dialog (sized for touch panel UI).

You can use the Select Profile Command or the Edit Profile Command also to select a profile. These commands are also available for modal UI using the Program Form.

Getting Started

11

The test executive also support loading and executing programs and profiles from within you code. See the Execution Commands for more information.

Once a program or profile is selected, the main window caption will display its name and the tree view will be filled with the program or profile tasks and tests. At this point the selected program or profile is ready to run.

The following dialog displays the Select Program/Profile Dialog with UUT1 program selected to run twice in parallel (separate threads):

The following dialog shows the Select Profile Dialog. The Open button allows you to browse existing profiles and open one profile file (.prf).


12

Running

Running a program and running a profile are similar. First select a program or profile (see Selecting a program or profile), then its tree view will display the contents of selected (profile file's) program(s), tasks, or tests.

Test Executive provides numerous conditions commands that you can set before run. See the Setting Conditions for Run topic for more information. Or you might want to input the UUT serial number in the start of the run (see Serial Number Command under Log command) . You can also check or un-check in the tree view the tasks/tests that you wish to run. By default, all the program or profile tests are checked.

To start the run, use one of the Run Commands.

In the most cases, to start run, you can select the Start Command. While the program is running, the test executive fills the current test properties in the Tests Properties pane and outputs the formatted test results to the test log. The status bar of the main window also displays the colored accumulative status of the UUT, the number of failures and optionally the time elapsed since you started the run. At any time you can select Abort Command or Pause Command. Pressing Abort will execute the OnAbort sequence of your application. Pressing the Pause button will pause the application and display "Pause" in the status bar. There are three types of Pause one of which you can select from: Pause at the end of Test, or at the end of Task, or immediately. If you select Pause at the end of Task, Test Executive will run all the tests of the current task, then honors the Pause. This will allow the user to adapt a specific user's testing environment.

In the Pause mode you can execute many of the Run menu commands to troubleshoot your UUT: you can run the current task or test in a loop, you can select the Current Test Command to repeat the current test again, you can skip a task or a test, you can change the condition of the run, un-check or check some tests you want to exclude or include in the run and many more.

Setting Conditions for Run

There are various Run time conditions you can set before or during the execution. You can have the Test Executive run continuously but pause when a test or a task failed using the Pause On Test Failure Command or the Pause On Task Failure Command. When a test or a task failed, the test executive will pause at the end of the task or test and the operator can issue many of the Run Commands to debug the UUT or abort the test.

You can also turn on the condition flag Prompt On Pause Failure which only takes effect when you select one of pause failure flags on: Pause On Test or Task Failure. This command will give the user the following options: Run Again, Continue (Ignore), Pause, and Abort.

The test executive also supports three modes of pause when the user selects the Pause Command: Pause At End Test, Pause At End Task, or Immediately. If you select the Pause Immediately Command the test executive will pause immediately no matter where it is. If you select Pause At End Task, the test executive will continue to run the current task and pause at the end of task.

You can also set the test executive to stop at the end of each task or test, once a task or a test is complete the test executive will pause and the operator can then examine test log and repeat the last task or test again using the Current Task Command or the Current Test Command.

Other conditions command lets you to set the run mode so the selected program or profile will be repeated endlessly (Repeat Run Menu Command). Furthermore, you can set conditions so that when a

Getting Started

13

task or test failed, it will be repeated second time: Repeat Task on Failure and Repeat Test on Failure. Optionally, you can set to run a maximum number (set Retry Failed Task option via Users\Options dialog) until it fails again.

Test Log

The test executive main window displays a test log in two Log Windows: All and Summary. They are filled by ATEasy and the application print statements. The test log window supports two file formats HTML and Text. In HTML mode you can embed graphics, colors and different font sizes, while in text format only text in one font is displayed.

By default the ATEasy test log contains the following sections:

Header Information - Company name and user name. Project name and Version Number and company logo image.

Program Information - Program name, its UUT name, Version number, Serial Number, and Start time.

Test information - task and test information: their number and name and test requirements (e.g. Min/Max), Test result, Test Status: None, Pass, Fail, and Error. If you select to choose the Failures Only In All Command Option for All Log window, then only failed tests will be logged - only those test status being Fail or Error.

End Information - Stop time, Elapsed time, UUT Status including the number of test failures. Optional Fault Analysis - the test log may also contain fault analysis if selected to be included at

the end of the run - see Conditions Editor Dialog.

However, application can modify this behavior and change the format of the test log.

The Summary Log window will only include Header, Program and End information. But if you select the Failures in Summary Command Option under Log, then failed tests will also be included.

Optionally, you can hide Summary Log - setting option Display Log Summary Tab to False (via Tools\users\Options dialog).

The following image shows the test executive with HTML test log:


14

Customizing the Test Executive Main Window

The test executive provides various ways to customize the main window layout and look:

The View Commands provides a way to control the layout of the main window. You can use the Customize... Command (for Single User) Users... Command (for Multi Users) to

customize the test executive menu commands, options, and toolbars. You can use the Options... Command to modify the options for the test executive. If the Multiple Users Support feature is on, an administrator can divide users to groups such as

testers, supervisors, etc and for each group he can set the options, menus, and toolbars and main window layout. See Users Dialog for further details.

More customization can also be done programmatically using the Test Executive Commands

Example : Run Selection Level

Getting Started

15

Sometimes you want the test program to be debugged only on a task level by disabling the individual test selections and allowing only the selection of a complete task. To accommodate this, Test Executive provides the Run Selection Level option from the Customize Dialog - Options Page. You can preset the option to be task only. If the Multiple Users Support feature is on, the administrator can force this option to be disabled (to protect this option from changing) through the Users Dialog - Options Page.

Working with Multiple Users

The test executive offers a way to customize the main menu commands, toolbars and options per user groups. The customization is saved to an ATEasy Users File. This feature is called Multiple Users Support. When activated, the test executive identifies the current user by asking the user to log in using the Login Dialog. Once the user successfully logs in, the test executive retrieves (if previously saved) the user's group settings that include: menu, forms, toolbars, options and privileges as configured by the administrator and applies them to the test executive. Administrator can create new user group and its various setting using the Users Dialog accessed from the Users... Command.

By default, the Multiple Users Support feature is not used, all users will share the same customization and option as set by the Customize Dialog. For Multiple Users, all the customization is being done through Users Dialog.

See the TestExecUsers.prj in the ATEasy Examples.wsp for example of multiple users support.

For more information how to setup the application to use the multiple users support see the Adding Multiple Users Support topic.

Working with Profiles

ATEasy is provided with a Profile driver (Profile.drv). If the driver is inserted in your Test Execute system (optional) it provides ways to create, modify profiles (test sequences) and select profile to run:

1. Using the Edit Profile... Command that opens the Profile Editor Dialog. 2. Using Profile's Edit Commands, create profiles programmatically. 3. Using the Select Profile... Command to open a profile file and select a profile using the Select

Profile Dialog. 4. Using the Test Executive Select...Command to open a profile file and select profile or select a

profile from previously opened profiles using the Select Program/ Profile Dialog.

The profile allows to create multiple profiles and store them into a single file(.prf file). Each profile contains an ordered list of tests to run. Tests can be selected in any order and from any program included in your application; that is, a profile list can contain programs, tasks and tests.

There are two ways to create (and modify) profiles : first using the Profile Editor Dialog (see below) and second using Profile Edit Commands. The dialog allows to enter new profile name and add tests and at the end save to a specific file. With Commands, the driver provides commands to open a new profile file and to insert items and save the file.

Once the profile was defined and saved to a profile file (.prf file), you can select the profile to run using the Select Profile... Command. The command opens the Select Profile Dialog that displays a list of the profiles stored in the file. When the user selects a profile from the list, the test executive then loads the profile displaying its tests in the main window tests view tree. At this point the profile is ready to run.


16

The following dialog shows the Profile Editor Dialog. The dialog displays a TestExec.prf profile with the SelfTest+UU1 profile name that, when selected, will run the SelfTest and then followed by the program called UUT1:

See the TestExec.prj and the Profile.prj examples for further example of profiles.

Each of the profiles stored inside a profile file contains a test sequence. A test sequence is a list of program, tasks and test node. Each node can have a conditions, an action, a label and parameters that can be used by the tests code at run-time.

See the Profile Driver Programming for more information of how to prepare your application to use the profile.

Getting Started

17

Using the Fault Analysis

ATEasy is optionally provided with a FaultAnalysis driver (FaultAnalysis.drv). If the driver is included in your system, it provides a way to define faults using the Edit Faults... Command that opens the Conditions Editor Dialog. Once the conditions are defined and saved to a condition file (.cnd file), you run the program and analyze the test results against the faults using the Analyze Faults... Command. The command opens the Faults Analysis Dialog that displays a list of conditions that were met. The dialog can be displayed by the test executive automatically if the check box, Display Analyze At End of Program Run, is checked from the Edit Faults Dialog. In that case it will be displayed if the program status is not PASS. Alternatively you can choose to dump the fault analysis to the log.

The faults that are defined using the Conditions Editor Dialog are created by building conditions that describe the fault. A condition is actually a test results pattern used to identify a fault. Each condition contains a condition name, expression and description. Condition expression identifies the fault and looks like 'testABC=PASS and testXYX=FAIL'. The expression can contain operators (AND, OR, NOT) and parentheses. Status fields can PASS, FAIL, NONE and ERR. Conditions expression uses test or task ID to identify the test; this ensures that even if the test is renamed the condition will still work. Once results are analyze against the conditions the user is displayed a list of conditions that where met with their description that usually describe the fault and suggest the user actions used to fix the UUT.

The following dialog shows the fault analysis dialog as shown at the end of the run. Several conditions were met and the top one U1 defective is displayed with it expression and description:


18

See the FaultAnalysis.prj example for an example of Fault Analysis.

See the Fault Analysis Driver Programming for more information about how to prepare your application for fault analysis.

Maintaining Log Files

As a part of Log Utility, Test Executive driver provides a way to save log automatically as it generates its test results.

The user is to enter Auto Save and Auto Archive Log specifications through Tools\Customize(or Users)\Log Files dialog. The following Auto Save specifications can be entered for a particular program or for all programs (the default setting):

A Specific Program Setting or Default Setting

Getting Started

19

Log File Name Specifications

Auto Save On/Off

Log to Save: All or Summary or Both or None

Auto Save Path and Backup Path

Next the user can enter Auto Archive Log information for the current project:

Log File Maintenance Information - how often to run and during run what to do with expired files, and when to perform the maintenance, etc...

Log File Name Specification You can imbed into the log file name the following specific information in addition to user defined string:

Program Name - %[n]p UUT Name - %[n]u Serial Name - %[n]sn Date and Time (YYYYMMDDHHMM) - %[n]dt Computer Name - %[n]c

Each field will delimit with "~", for example, %p~%sn~%dt. You can specify a specific length for a field. If the length is less than the real length, the string will be truncated and if the length is more than what it is necessary, the string will be filled with '_' (underscore characters).

As Auto Save Log has been turned on, log files will be saved in the specified path. You can save All log or Summary log or both. To distinguish Log files, the following suffix words will be added to the Log file name:

"~a" - for All Log :~s" - for Summary Log - 's' means short

For example, if the name specification is "%p~%sn~%dt" and you want to save both log files: all and short. When a program called 'SystemBit' ran, the following two files will be generated. Notice that there was no serial number.

When Auto Archive is on and the user specified when to do it, Auto Archive would be performed. First it checks any expired files exist, if it does, processes as directed by its specifications. Once it is done, it remembers its Time Date so that it know the next time to run Archive or maintenance. Auto Archive is being performed on all files in the auto save path directory

Lastly, you can manually manage these saved log files through Log Files dialog which allows you to view\delete\print\backup the log files.


20

External Program Executable Support Version 7

In a typical ATEasy Application, all of your programs are contained in one project. With this feature you can create many (mini) projects, each containing one or more programs. You begin with the start application and be able to switch to any of other applications - back and forth. In an INI file, External Programs Configuration File, you specify each program with its executable path and how each program is configured as in a tree structure. When the user selects a program and if it resides in another application (.exe) according to the External Programs Configuration File, then the new application is loaded with current test conditions... and so on. Thus with this feature, there are a set of ATEasy Executables and they run one after the other in a seamless fashion.

This support provides the following benefits:

Programs can be shipped to the customer as they are completed. Customer just needs to add to the external program list and copy the EXEs. ( It is also possible to ship the External Programs Configuration File.)

Re-certification of old programs is not required when new programs are added.

Modular approach to program development. This allows users to develop programs with same system/driver but in smaller and independent projects.

You enable this feature by setting External Programs Configuration File to TestExec driver parameter called ExternalProgramINI - see below the driver's shortcut properties window. You can enter a full path of the INI file, or a relative path, or just a file name. If the path is relative, then it will be based with the App EXE path (in Project\Project property window.) If just a file name entered, then the file is expected to be in c:\Windows directory. If the file does not exist in the specified directory, TestExec will create the file.

The External Programs Configuration file contains some global information: Project Key, its Caption, and the number of programs/folders and information about each program item: type (program or folder), ID (unique identification - program name or folder's id), Caption (to be displayed in forms or menus), its parent ID (if exists), its Executable Path (Full) - this only applies Program. Please see the detailed External Programs Configuration File Format below.

The External Programs Configuration File can be created, edited, and viewed using NOTEPAD Windows application. TestExec also provides its Editor via a command called External Programs... - when you select this through a menu or a form button, External Programs dialog is displayed.

When you specify the External Programs Configuration File in the driver parameter, the entire TestExec will run in the mode. The following items you can expect to be different from normal 'one project' application:

1. Modeless: Program Select dialog will include all programs in the file and Menus will reflect programs and folders in the file

2. Modal: Program Select form and its contents will reflect Programs\Folders in the file 3. Whenever you create a program with its own project, you must modify the INI file via External

Programs Dialog editor. 4. Auto Save and Auto Archive Log Files specifications are saved under a key called ProjectKey -

thus be aware of its consequences of changing ProjectKey; that is you have to re-create the Log

Getting Started

21

File specifications.

TestExec Driver Shortcut - ExternalProgramINI Parameter

External Programs Configuration File Format

The INI file consists of two main sections: one is the main section describing the multiple-executable project and the other containing each program section with program\folder information.

Programs section - Main Project Section has three entries:

Name Description Required/Optional

[Programs] Main Project Section Name Required

ProjectKey Unique Project Key Name Required

ProjectCaption Project Caption Optional

Count Program List Item - either program or folder Required

For each program or folder item, Program section is defined as:

Name Description Required/Optional

[Programx] xth program list item name Required

Type 'program' or 'folder' Required

ID Unique ID - that identifies within the 'ProjectKey' project Required

Caption caption to be displayed in menu or form buttons - this can be multiple lines' caption - its delimiter is "\r\n" - used for form buttons - only first line displayed for menus.

Optional

Parent If the program is not Top level one, then parent ID is needed

Optional for Top Level Item and Required for subsequent level items.

EXE ATEasy Executable Path that contains this program - only applies to programs

Required for Program


22

Example for External Programs Configuration File

The following is an example INI file containing 79 program items - here shown only 7 first items:

[[Programs] ProjectKey=TS217 ProjectCaption=TS-217u Count=79 [Program1] Type=folder ID=MAVERICK Caption=MAVERICK Parent=

[Program2] Type=folder ID=LAU88AA Caption=LAU88AA Parent=MAVERICK

[Program3] Type=folder ID=LAU88AA_LRU Caption=LAU88AA LRU Parent=LAU88AA [Program4] Type=folder ID=LAU88AA_LRU_FUNC Caption=LAU88AA LRU Func Parent=LAU88AA_LRU [Program5] Type=program ID=LAU88AA_LAU_FUNC Caption=LAU88AA\r\nFunctional Test EXE=C:\TS217\PRJ\TS217u_Lau88aaLAU_Func.exe Parent=LAU88AA_LRU_FUNC [Program6] Type=folder ID=LAU88AA_LRU_SELFTEST Caption=LAU88AA LRU Selftest Parent=LAU88AA_LRU [Program7] Type=program ID=LAU88AA_LAU_ST Caption=LAU88AA Selftest EXE=C:\TS217\PRJ\TS217u_Lau88aaLAU_ST.exe Parent=LAU88AA_LRU_SELFTEST

External Program List Editor dialog - create/edit/view the External Programs Configuration File

Getting Started

23

For its detailed description, please refer to the External Programs dialog:


24

Multiple UUTs and Parallel Testing Support Version 8

Starting with v8.0 the test executive supports running of multiple UUTs in sequential, parallel or mixed run modes. The user can set how many UUTs he wishes to run, the run mode (parallel or sequential) and a program or a profile for each UUT. The test executive then displays a tab for each UUT. Each UUT tab display the program or profile tests, a log window and a test properties pane.

Selecting the Start button will start running the UUTs in the sequential mode pool (running under the same main thread) and according to the UUT Switch Level (set by options or using App.UutSwitchLevel property). In addition, UUTs that where set to parallel will also start at the same time and will be executed in their own thread.

Multiple UUT program Selection Examples

Example 1: Sequential Mode UUTs

Two Sequential mode UUTs with two different programs as follows:

UUT count is set to 2 Run mode of both UUTs is sequential UUT1 was assigned to Program1 (3 tasks), UUT2 was assigned to program2 (2 tasks) UUT Switch level (set from the Customize Option dialog) was set to switch every task

then selecting the Start will run as follows:

Program1 Task1, Program2 Task1, Program1 Task2, Program2 Task2, Program1 Task3. All the UUTs will run in the same thread as the main application thread.

Example 2: Mixed Mode UUTs

Four UUTs, the first two as the first example, UUT 3 and 4 are parallel. In this example when you select Start to run the UUTs, 3 threads will be created. The main thread will run UUT1 and UUT2 in sequential mode as described in Example 1. UUT3 and UUT4 will run the program or profile assigned to them independently each in its own thread (UUT switch level will not be used for these UUTs).

New Features in the Test Executive to Support Multiple UUTs

Support for selecting one or different programs or profiles for UUTs Support for setting Program, Task and Test UUT switch level Multiple UUT tabs each with program tests, test properties and test logs. UUT tab are status

based colored, display image of program or profile and run state mode (ready, paused or run). New Commands: Start UUT and Abort UUT were added to the Run menu, the Start, Abort and

Reset commands were enhanced to start or abort all selected UUTs. New options: Enable Multiple UUTs, Enable UUT Count Setting, Default UUT Count, Default

UUT Switch Level, Allow Different Program/Profile per UUT, Activate UUT tab on UUT Switch. See the Customize Dialog - Options Page for more information.

Getting Started

25

Support for entering Multiple Serial numbers for multiple UUTs. See the Serial Number Dialog for more information.

Steps Requires to Support Multiple UUTs in the Test Executive

1. Set the Enable Multiple UUTs option to True using the Customize Dialog - Options Page. 2. Set the other UUT options as required by your application using the Customize Dialog - Options

Page. 3. Select a program or a profile using the Select Program Dialog. Depends on the options you set

the dialog will allow you to override and set the UUT count, select one or more program/profile for your UUTs and select the run mode for each UUT (parallel or sequential).

4. To test all UUTs, select the Start Command from the Run menu, to test single UUT, select the UUT tab for your UUT and select the Start UUT Command.

Changes to Your Application Code to Support Multiple UUTs

1. For Sequential run mode, You may add code in OnInitSwitchUut, OnEndSwitchIUut module events (driver, system or program). The code will be executed when ATEasy switches from one UUT to another as set by the App.UutSwitchLevel.

2. Modify your test code to use the App.UutIndex to perform switching and other UUT index based instrumentation access.

3. For parallel run mode, synchronize access to resources, test and procedures using the Semaphore property of the module (Driver, system or program) you are trying to lock. Use the Task, Test and Procedure Synchronize flag to allow access to code only from a single thread.

4. If you need to enforce run mode for specific programs in your project create a program parameter UutRunMode from the program properties window and set the parameter to specific run mode (0=sequential, 1 parallel) in the program shortcut properties window.

27

Menus, Commands.., and Dialogs

Test Executive Menu, Commands and Dialogs

This book provides a reference to the Test Executive menu commands and User Interfaces: menu, toolbar, options, and dialog boxes. The following topics are available:

Dialogs Commands Options Menus Forms Toolbar

Commands

Test Executive Commands

We have the following Test Executive Command categories - each group includes a list of commands that can be used by Menu, Toolbars, or Forms.

Program Commands View Commands Run Commands Conditions Commands Log Commands Tools Commands Help Commands Miscellaneous Commands User Defined Commands

User Defined Commands are those that Test Executive users will create using Users\Commands or Customize\Commands. Once you create a user defined command, it can be used as a menu item, or a toolbar button, or in a form.


28

Program Commands

Program Commands

Test Executive has the following Program Commands: Command Description

Programs... This is used by Forms\Menus to display its programs and folders.

Select Opens Select program dialog with all programs and allows you to select one program.

Edit Profile Create a new or modify a profile from a profile file (*.prf).

Open Profile This command exits inside of Select Profile dialog.

Select Profile Select a profile.

Edit Faults Create a new or modify conditions in a condition file (*.cnd).

Analyze Faults Analyze Faults - open selected condition file, perform Faults Analysis, and display faults.

Perform Fault Analysis At End

Perform Fault Analysis at the end of program run - results will be dumped to Log.

Exit Exits TestExec.

External Programs Opens External Programs dialog and allows you to modify External Program INI file.

Select... Command (Program Command)

This menu command displays the Select Program/Profile Dialog which lists all the programs in the application and profile previously opened for this project (v8). The user can select one of programs or that profile (v8) he wish to run and the selected program or profile will be shown on the tree view.

Shortcut: CTRL+O

Program Selection Command (Program Command)

This command displays each level's Programs and Folders.

If this command is used by Forms, upon selection of this command, a form will display with all the programs and folders of top level. If you select one of folders, then the programs and folders that belong to the folder will be displayed in another form, and so on. In v8, the menu also shows recent profiles selected by the user for this project/application.

For menus, this will create each program menu and folder menu as shown below. The Test Executive will display programs, each by either program name or its UUT name (either in Forms or Menus).


29

The user can select one to run and the tree view of the current UUT will display the selected program or profile tests and tasks.

For example, the following shows menus with programs and a folder:

External Programs... Command Version 7

This command opens the External Programs Dialog. This command becomes enabled only when the TestExec driver parameter ExternalProgramINI is defined in the Test Executive Driver Shortcut properties Misc page. With this dialog, the user can create (if the INI file does not exist), insert new program items, modify existing ones - the contents of INI file can be view and modified.

See the External Program Executables Support (v7) for more information.

Edit Profile... Command (Program Command)

This command displays the Profile Editor Dialog. This dialog will allow you either to create a new profile or to modify an existing profile.

After opening a profile (.prf file) and selecting the profile with Select Profile command, the user can run a profile instead a program.

Note: This command will be visible only if the Profile.drv was inserted in your system.


30

Select Profile... Command (Program Command)

This command opens the Select Profile dialog. Select this command after Edit Profile command. Edit Profile and Select Profile commands are used for running a profile instead a program.

This dialog also contains the "Open" button, so that you can select already existing profile without going through Edit Profile menu command.

Note: This command will be visible only if the Profile.drv was inserted in your system.

Open Profile Command (Program Command)

This command allows you to open a profile file to select one of profiles. This command is found in the Select Profile dialog.

If you select Open, the windows' open common dialog will allows you select a profile and fill the combo box its profiles.

You can choose to disable this command - then it will not allow to open:


31

Edit Faults... Command (Program Command)

This command allows you to open Conditions Editor Dialog. This dialog will allow you either to create a new condition file or to modify an existing one.

After opening a condition file (.cnd file) and selecting an appropriate condition set for a program to be run, the user can set to see its fault condition analysis at the end of the test log or in the Analyze Faults Dialog.

Note: This command will be visible only if the FaultAnalysis.drv was inserted in your system.

Analyze Faults... Command (Program Command)

This command opens the Analyze Faults dialog. Select this command after selecting a condition file via Edit Faults command. The dialog displays the results of Faults Analysis.

This menu will be enabled only after the program or profile run and the status of the last program run was not PASS.

Note: This command will be available only if the FaultAnalysis.drv is present in your system.

Perform Fault Analysis At End Command (Program Command)

If this command is checked or On, Test Executive will perform Fault Analysis at the end of program run and its results will be dumped to Log.

We have similar flags in the Fault Analysis driver. When Fault Analysis driver is used with Test Executive, we will not honor the Fault Analysis driver flags unless the user checked this command.

Exit Command

Use this command to exit TestExec.


32

View Commands

View Commands

The View Commands contains the following: Command Description

Menu Hide/Show menu bar

Log Activates the Log window

Toolbars Shows four different toolbars' views:

small buttons

small button with labels

large buttons

large buttons with labels

no toolbars

Lines Bar Activates two lines of information - e.g. Program, Status, ...

Tests Activates tests tree view

Test Properties Activates test properties view

Menu Command (View Menu)

This menu command allows you to turn on (Show) and off (Hide) the main menu bar.

Before the main menu bar turned off, make sure necessary menu commands are available via toolbar or other means.

If you find you are stuck without menus, check the INI file and change its options value to True - "OptionsShowMenu".


33

Log Command (View Menu)

This menu command allows you to turn on and off the Log Window where test results are to be displayed. If you turned off the Log Window, the tree view and test properties view will be expanded.

ToolBars Menu Commands (View Menu)

This command allows to view/hide toolbars in five different ways:

1. Small Buttons

2. Small Buttons with Labels

3. Large Buttons

4. Large Buttons with Labels

5. No Toolbar - toolbar will be hidden

Small Buttons:

Small Buttons with Labels:

Large Buttons:

Large Buttons without Labels:


34

Lines Bar (View Command)

This menu displays two lines of information. It toggles between Show and Hide.

By default, the first line contains Program Name or Profile Name, and the second line contains the program status.

You can define these two lines of info via Tools\Customize\Forms( for Default User case) and Tools\Users\Forms ( for Multiple Users case).

You can provide your own text or you can specify "No Text".

Tests Command (View Menu)

This command allows you to turn on or off test tree view of a program or a profile.

If one might choose to view only test results in the Log Window, then you can toggle off this command.

Test Properties Command (View Menu)

This command allows you to view test properties.

In order to view a certain test properties, you can select a test in the tree view.

Unless the tree view is turned on, this view will not be displayed.

You can turn off this which will cause Test tree view to be expanded.


35

Run Commands

Run Commands

The Run main command contains the following commands:.

Command Description

Start Starts the execution of all UUts program or profiles.

Start UUT Starts the execution of the current active UUT tab program or profile.

Reset Resets the system to its initial state.

Abort Aborts all currently running UUTs program or profile execution.

Abort UUT Aborts the current active UUT tab program or profile execution.

Pause/Continue Pauses program execution or Continues execution from a pause.

Skip To Next Task Skips the current task and jump to the next task

Loop On Task Performs an endless loop on the current task

Current Task Executes the current task once (once)

Skip To Next Test Skips the current test and jump to the next test

Loop On Test Performs an endless loop on the current test

Current Test Executes the current test again (once)

Start Command (Run Command)

Use this command to start execution of a program or a profile according to the checked list of tree view and testing/debugging conditions selected from the Conditions Menu. If more than one UUT is available than all selected programs/profile will start run according to their UUT Switch Level option.

You can select the Start command only if the program/profile is not already running.

Shortcut: F5

Start UUT Command

Starts running the active UUT tab program or profile. Use this command to start execution of a program or a profile according to the checked list of tree view and tes

Documents

At Easy 8 Test Executive