The Test Sequencer contains two applications the Test Sequencer which executes and controls the test sequence, evaluates measurements against limits, formats the test report, contains a test sequence editing system, and the Step Engine executes the sequence steps. TCP protocol is used for communication by the applications.
The Step Engine acts as a Step Server while the Test Sequencer is the client. The Test Sequencer initiates communication to the server, and the Step Engine returns a response. There are 3 kinds of step types; Action, Test, and Sub-Sequence. Action Steps perform actions and do not return measurements; Example: Message Prompts, Delay, etc… Test Steps perform tests that return measurements and auxiliary data. Sub-Sequence Steps call other sequence files containing more steps. There is no limit to how many nested sequence files you can use.
Steps are added to a sequence file from user created configuration step files. Users can create their own Action or Test Steps. Modify parameters and limits for each step, rearrange the order of the steps, and launch the Step Engine from the sequence file.
The Test Sequencer supports breakpoints within the sequence file and can single step through the test sequence. This feature can be very useful in debugging your code in the Step Engine. The Step Engine can run from the Labview development environment to aid in debugging, then create an executable for deployment to the target test system.
The Test sequencer supports custom ID Fields and Entry Fields. ID Fields are used to describe the test system and or location of the test system, but can be used for any information. The values for these ID fields are returned by the Step Engine. Entry Fields are descriptions about the device under test. The user enters or scans information into these entry fields before starting a test sequence. The values for these Entry fields are validated by the Step Engine. The Test Sequencer displays and formats all field values into the Test Report.
This page displays the Sequence file and the runtime indicators and other information about the test sequence. This page also suppurts editing of the sequence file via the Parameters Bar under Step Editor, User Interface Configuration, Data Field Customization, and Sequence Configuration submenus.
This page displays the steps loaded by the Test Sequencer. The StepFiles directory is scanned for step configuration files (ini); which contains information about the step and contains parameters and measurement limits. These step files can be edited here to modify parameters and measurement limits only. These step files are created by the test developer following a specified format and adds these files to the StepFiles directory so they can be added to a Sequence File.
This page displays the sequence data results. The results page may consist of several data pages; which are selectable from the “Results Page List” in the “Results Parameters Bar”. There are five types of data results displayed on this page, Summary, Measurements, Steps, Parameters, and Auxiliary Data/ XY Data. The results data is displayed via the “Results List”, but XY Graph Data is displayed via a “Graph Plot” control.
Steps can output auxiliary data that delivers a broader understanding of the results and Test Sequencer supports plotting this data via a XY Graph control. Test Sequecner can export this data as simple text files, or XML markup files.
This page shows the Test Sequencer Users Manual plus any other help pages for steps the developer has created or any other kind of help page.