TEST PROGRAM FLOW CONTROL

• US 20180313891A1
• Filed: 04/28/2017
• Published: 11/01/2018
• Est. Priority Date: 04/28/2017
• Status: Active Grant

• Current Assignee: Advantest Corporation
• Original Assignee: Advantest Corporation
• Inventors: Nahum, Rotem, Toy, Rebecca, Phan, Boilam, Liu, Jungtsung, Chen, Leon
• Granted Patent: US 10,451,668 B2
• Time in Patent Office: Days
• CPC Class Codes: G01R 31/2834 Automated test systems [ATE]; using microprocessors or computers G01R31/317 takes precedence; ATE for detection of defective computer hardware G06F11/2736
• CPC Class Codes: G01R 31/287 Procedures; Software aspects

Abstract

A system for performing an automated test is disclosed. The system comprises a user computer operable to load a test program from a user to a control server, wherein the test program comprises a plurality of test flows. The system further comprises a tester deploying a plurality of primitives. Further, the control server is communicatively coupled to the user computer and to the tester, wherein the control server is operable to download the test program to a primitive from the plurality of primitives, and wherein the control server is further operable to execute a first test flow from the plurality of test flows on a first DUT within the primitive and concurrently execute a second test flow from the plurality of test flows on a second DUT within the primitive.

Claims

1. A method for performing tests using automated test equipment (ATE), said method comprising:

loading a test program to a control server from a user computer, wherein the control server communicates with a plurality of primitives in a tester, and wherein the test program comprises a plurality of test flows;

downloading the test program to a primitive from the plurality of primitives;

executing a first test flow from the plurality of test flows on a first DUT within the primitive; and

concurrently executing a second test flow from the plurality of test flows on a second DUT within the primitive.

2. The method of claim 1, further comprising:

executing a different test flow on each DUT within the primitive concurrently.

3. The method of claim 1, wherein the test program comprises a standard interface language (STIL) file, and wherein the plurality of test flows are defined within the STIL file.

5. The method of claim 1, wherein each program sequence comprises a plurality of segments, wherein each of the segments is operable to be tagged and identified using an identification number, wherein the identification number is used to perform execution order numbering for the plurality of test flows.

6. The method of claim 1, wherein the plurality of test flows can be edited by a user using a graphical user interface (GUI) running on the user computer.

7. The method of claim 1, wherein the plurality of test flows can be edited by a user using a GUI running on the control server.

8. The method of claim 1, wherein the plurality of test flows can be executed by a user using a GUI running on the user computer.

4. The method of claim 4, wherein each test flow comprises a plurality of program sequences, wherein steps for the plurality of program sequences can be selected from the group consisting of:

pre-processing steps, testing steps, post-processing steps and debugging steps.

9. A system for performing an automated test, said system comprising:

a user computer operable to load a test program from a user to a control server, wherein the test program comprises a plurality of test flows;

a tester deploying a plurality of primitives; and

the control server, wherein the control server is communicatively coupled to the user computer and to the tester, wherein the control server is operable to download the test program to a primitive from the plurality of primitives, and wherein the control server is further operable to execute a first test flow from the plurality of test flows on a first DUT within the primitive and concurrently execute a second test flow from the plurality of test flows on a second DUT within the primitive.

10. The system of claim 9, wherein the control server is further operable to execute a different test flow on each DUT within the primitive concurrently.

11. The system of claim 9, wherein the test program comprises a standard interface language (STIL) file, and wherein the plurality of test flows are defined within the STIL file.

12. The system of claim 9, wherein each test flow comprises a plurality of program sequences, wherein steps for the plurality of program sequences can be selected from the group consisting of:

pre-processing steps, testing steps, post-processing steps and debugging steps.

13. The system of claim 12, wherein each program sequence comprises a plurality of segments, wherein each of the segments is operable to be tagged and identified using an identification number, wherein the identification number is used to perform execution order numbering for the plurality of test flows.

14. The system of claim 9, wherein the plurality of test flows can be edited by a user using a graphical user interface (GUI) running on the user computer, wherein the user computer is communicatively coupled with the control server using a standard IP connection.

15. The system of claim 9, wherein the plurality of test flows can be edited by a user using a GUI running on the control server.

16. The system of claim 9, wherein the plurality of test flows can be executed by a user using a GUI running on the control server.

17. A system for performing an automated test, said system comprising:

a user computer operable to load a test program from a user to a control server, wherein the test program comprises a plurality of test flows;

a tester deploying a plurality of tester slices; and

the control server, wherein the control server is communicatively coupled to the user computer and to the tester, wherein the control server is operable to download the test program to a tester slice from the plurality of tester slices, and wherein the control server is further operable to concurrently execute a different test flow on each DUT within the tester slice.

18. The system of claim 17, wherein the test program comprises a standard interface language (STIL) file, and wherein the plurality of test flows are defined within the STIL file.

19. The system of claim 17, wherein each test flow comprises a plurality of program sequences, wherein steps for the plurality of program sequences can be selected from the group consisting of:

pre-processing steps, testing steps, post-processing steps and debugging steps.

20. The system of claim 19, wherein each program sequence comprises a plurality of segments, wherein each of the segments is operable to be tagged and identified using an identification number, wherein the identification number is used to perform execution order numbering for the plurality of test flows.

21. A method for performing tests using automated test equipment (ATE), said method comprising:

loading a first test plan to a control server from a graphical user interface on a first user computer, wherein the control server communications with a plurality of primitives in a tester, wherein the plurality of primitives are deployed within a single rack in the tester;

downloading the first test plan to a first subset of primitives from the plurality of primitives, wherein the first test plan comprises a plurality of test flows;

loading a second test plan to the control server from a graphical user interface of a second user compute;

downloading the second test plan to a second subset of primitives from the plurality of primitives;

executing the first test plan and the second test plan concurrently;

executing a first test flow from the plurality of test flows on a first DUT within the first plurality of primitives; and

concurrently executing a second test flow from the plurality of test flows on a second DUT within the first plurality of primitives.

22. The method of claim 21, further comprising:

while the first test plan is operating and the second test plan has completed execution;

loading a third test plan to the control server from a graphical user interface of a third user computer;

downloading the third test plan to a third subset of primitives from the plurality of primitives; and

executing the first test plan and the third test plan concurrently.