Writing a test software for the ATE is a very challenging part. You have to consider a lot of variables including the UUTs' behavior at the same time your equipment itself. Usually, some test equipment manufacturers provide ATE System solutions also. They have there own system in running the hardware. Usually the system only covers standard test parameters but it will not cover for any custom test which usually happens. You can write an external code or you can write a custom test by your own to satisfy the product requirement. Most of the common languages use that will adapt to manufacturer's ATE system is Visual Basic , Quick Basic.
Some test professional prefer to write there own code for the whole ATE function, this means you have to write every test routine associated on each of the test you want to perform. The advantage for this is that you have the full control of the setup both hardware and software.
These are the common tools use as a programming tools for the ATE:
- Visual Basic
- National instruments Lab View
Here are some pointers and reference in writing a test program for a specific test:
- Understand how the test should be perform, you have to simulate manually the actual test and record the result. Record each step you have done and make sure that you are getting the right result that you have expected.
- From the data gathered, write a step by step code to automate the test . You have to put some delay on each of the step to make sure that the test will be duplicated.
- Compare the results done manually and the automated test. Both result should correlate.
- Then try to reduce or remove the delays you have added and make sure same result is achieved otherwise dont remove the delays.
Test Programming Notes and Techniques:
- Naming Test routines - When you are starting to develop test software and test routine, you have to bare in mind that you have to assign file name for each of the test routines or test vi. Make sure that the naming scheme of the test program and test routines properly orgarnized. One important thing to consider is that, from the filename itself, you can identify whats the test routine for.
Example: OverCurrentTest.Vior OverCurrentTest.bas ---- from the filename itself, any user can identify which test is the routine for.
- Selecting Variable name - variables use inside the test routines and test program are very critical, either local variables or global variables. Make sure that when you select a name of the variable this should coincide on what the variable for. Also, this should be on the right data type (string, integer, double, single ...arrays).
Example:
Visual Basic Global Variables naming recomendations: glb_sgDelaytoRead as single, glb_strParameterName as string.
Visual Basic Local Variables:naming recommendations: sgDelay as single, strOutputName as string.
From the variable name itself, you can identify if its global or local and the data type.
Deciding either a variable should be local or global?
Set your global variables to those variable that will not change the value for the entire run time, such as Test Program Name, Start Time, Equipment address...etc..
Set local variable to those variables that will constantly change during run time, like readings, Load conditions, counters...etc.
 | 
