Multiple Test Executives in ATE

In modern systems there is a desire to create Test Program Sets (TPSs) in multiple languages. However, most Automatic Test Equipment (ATE) is designed with only one test executive in mind and the exclusion of all others. This paper discusses a proven design to allow for Multiple Test Executives (MTE) on a single system. In addition, the test executives are divorced from the operator or maintainer so that they are not directly aware of the underlying test exec. This allows TPS programmers to work in a language of their choice and expertise in order to generate TPSs in the most efficient manner. This also allows for legacy TPSs to be more easily moved to the new system as it is more likely that there is a good fit between one of the legacy test programming languages and one of the many supported by the new system supporting MTE. By allowing MTE under one common operator interface, a consistent look and feel can be enforced while still allowing for MTE. This abstraction of operator interface from the actual test executive is done by taking advantage of several aspects of modern test executives and user interfaces. Most modern test executives actually live as an engine which can be controlled via software. While they may come with a GUI out of the box (Test Stand, Test Studio, ATLAS, etc), most modern test executives are run by an underlying engine which is controllable through similar interfaces. Point in fact, Test Stand, Test Studio, and PAWS ATLAS can (and are) controlled in this manner. By allowing for software control of the test executive, a common GUI can control another common run time engine which communicates with all the test executives and runs TPSs on the corresponding test executive. By also creating a common interface to the GUI and instruments, all of the test executives can communicate through the common software and be controlled by and control a common set of user interfaces and instruments.