Have the flexibility of using multiple ATE systems for a given product.
Verify the tests executed on either platform are really identical, or easily spot any difference.
EDA to ATE
Verify pattern conversion accuracy. Avoid expensive customer returns due to test pattern mismatch
When a test fails on ATE easily analyze and compare the source EDA formatted test to the one used on the ATE.
EDA to EDA
If part of the process involves cyclization and translating an event driven format to cycle driven one, the conversion results typically are different, and the user needs to understand and validate the results in an efficient way!
The tool internally translates any format to an event stream. It then compares the two tests and highlights any differences.
The actual signal behavior is compared and identified.
The view shows the differences in the waver, but allows any diff to be tracked down to the source syntax. Thus the user can see the cause and location of each test data difference.
The user can customize the tool activity and make it only compare certain sections or certain signals
The tool is command line executed, just pointing to the two test sources.
The diff results are displayed in the waver which pops up once executed and displays only the differences with the different signals displayed.
The text report structure is cycle based, hence it will only indicate each difference type once.
As a result, the report clearly shows repeated differences and the repetition nature which decreases the report size and helps understand the results in a more intuitive way.