Test executive system and method including distributed type storage and conflict resolution

• US 6,397,378 B1
• Filed: 02/26/1999
• Issued: 05/28/2002
• Est. Priority Date: 08/21/1998
• Status: Expired due to Term

• Current Assignee: National Instruments Corporation (Emerson Electric Company)
• Original Assignee: National Instruments Corporation (Emerson Electric Company)
• Inventors: Byrd, Ronald, Grey, James
• Primary Examiner(s): Dam, Tuan Q.
• Assistant Examiner(s): Vo, Ted T.
• Application Number:
  US09/259,173
• Time in Patent Office: 1,187 Days
• Field of Search: 717/4,1,11
• US Class Current: 717/175
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A test executive program which provides greatly improved configurability and modularity, thus simplifying the creation, modification and execution of test sequences. The test executive program includes process models for improved flexibility, modularity and configurability. Process models provide a modular and configurable entity for encapsulating operations and functionality associated with a class of test sequences. The process model thus encapsulates a “testing process” for a plurality of test sequences. The process model enables the user to write different test sequences without repeating standard testing operations in each sequence. The test executive program also includes step types for improved configurability. A step type is a modular, identifiable unit configured by the user which defines common properties and/or operations associated with a plurality of steps. Instances of the step type incorporate this common functionality and/or properties from the step type, and thus the user is not required to hard code that functionality and/or properties in each instance or step. The test executive program also provides distributed type storage and conflict resolution. When the user loads a file which includes a stored type, the method performs conflict resolution, including determining if the loaded type conflicts with one or more previously loaded/registered types. If the types do conflict, then the test executive or user selects a type, preferably using the version data associated with each type. The test executive system also performs automatic result collection to automatically collect the results of each step. The user can enable or disable result collection for a particular sequence or for the entire test station.

Claims

1. A method for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), the method comprising:

loading a file with at least one type, wherein the at least one type comprises one of;

     1) a data type or

     2) a step type, wherein the at least one type includes version data;

determining the type being loaded in response to said loading;

determining if the type conflicts with one or more previously loaded/registered types, wherein said determining includes comparing the type being loaded with the previously loaded/registered types in the system;

selecting a type based on the version data in response to determining a type conflict;

registering the at least one type in the system in response to determining that there is no type conflict.

2. The method of claim 1, wherein said determining the type being loaded and said determining if the type conflicts are automatically performed in response to said loading the file.

3. The method of claim 1, wherein said determining the type being loaded, said determining if the type conflicts, and said selecting a type are automatically performed in response to said loading the file.

4. The method of claim 1, wherein said determining if the type conflicts comprises determining if a name of the at least one type conflicts with a name of one of said previously loaded/registered types.

5. The method of claim 1, further comprising:

receiving user input regarding selection of a type in response to determining a type conflict;

wherein said selecting a type is performed in response to said user input.

6. The method of claim 1, wherein said selecting a type is automatically performed in response to determining the type conflict.

7. The method of claim 1, further comprising:

determining that the version data of the at least one type and the one or more previously loaded/registered types are the same after said determining a type conflict;

receiving user input regarding selection of a type in response to said determining that the version data are the same;

wherein said selecting a type is performed in response to said user input.

8. The method of claim 1, wherein the file stores a data type definition of the at least one type.

9. The method of claim 1, further comprising:

creating a step or data of a first type in the file in response to user input; and

automatically storing a type definition of the first type in the file in response to said creating.

10. The method of claim 1, further comprising:

creating the at least one type and assigning a name to the at least one type in response to user input; and

storing a step or data of the at least one type in the file;

wherein said creating and said storing are performed prior to said loading the file.

11. The method of claim 10, further comprising:

automatically storing a type definition of the at least one type in the file in response to said creating and said storing.

12. The method of claim 10,

wherein said creating and said storing are performed in a first computer;

and

wherein said loading the file is performed in a second computer.

13. The method of claim 10,

wherein the at least one type has a first name;

wherein said determining if the type conflicts comprises determining if the first name of the at least one type conflicts with a name of one of said previously loaded/registered types;

wherein said creating and said storing are performed in a first computer;

wherein said loading the file is performed in a second computer, wherein the second computer includes a different type which includes said first name.

14. The method of claim 1, wherein said types comprise a data structure;

the method further comprising;

conforming existing instances of one or more non-selected types with the selected type, wherein said conforming comprises modifying the data structure of the one or more non-selected types to conform to the data structure of the selected type.

15. The method of claim 1, further comprising:

conforming existing instances of one or more non-selected types with the selected type, wherein said conforming includes preserving at least a portion of old data of the one or more non-selected types.

16. The method of claim 1, wherein the version data comprises one or more of:

user-entered version data, or date and time information.

17. A memory medium comprising program instructions for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), wherein, in response to loading a file with at least one type, wherein the at least one type comprises one of:

1) a data type or

     2) a step type and wherein the at least one type includes version data, the program instructions are executable to implement;

determining the type being loaded in response to said loading;

determining if the type conflicts with one or more previously loaded/registered types, wherein said determining includes comparing the type being loaded with the previously loaded/registered types in the system;

selecting a type based on the version data in response to determining a type conflict;

registering the at least one type in the system in response to determining that there is no type conflict.

18. The memory medium of claim 17, wherein said determining the type being loaded and said determining if the type conflicts are automatically performed in response to said loading the file.

19. The memory medium of claim 17, wherein said determining the type being loaded, said determining if the type conflicts, and said selecting a type are automatically performed in response to said loading the file.

20. The memory medium of claim 17, wherein said determining if the type conflicts comprises determining if a name of the at least one type conflicts with a name of one of said previously loaded/registered types.

21. The memory medium of claim 17, wherein the program instructions are further executable to implement:

receiving user input regarding selection of a type in response to determining a type conflict;

wherein said selecting a type is performed in response to said user input.

22. The memory medium of claim 17, wherein said selecting a type is automatically performed in response to determining the type conflict.

23. The memory medium of claim 17, wherein the program instructions are further executable to implement:

determining that the version data of the at least one type and the one or more previously loaded/registered types are the same after said determining a type conflict;

receiving user input regarding selection of a type in response to said determining that the version data are the same;

wherein said selecting a type is performed in response to said user input.

24. The memory medium of claim 17, wherein the file stores a data type definition of the at least one type.

25. The memory medium of claim 17, wherein the program instructions are further executable to implement:

creating a step or data of a first type in the file in response to user input; and

automatically storing a type definition of the first type in the file in response to said creating.

26. The memory medium of claim 17, wherein the program instructions are further executable to implement:

creating the at least one type and assigning a name to the at least one type in response to user input; and

storing a step or data of the at least one type in the file;

wherein said creating and said storing are performed prior to said loading the file; and

automatically storing a type definition of the at least one type in the file in response to said creating and said storing.

27. The memory medium of claim 26,

wherein said creating and said storing are performed in a first computer;

and

wherein said loading the file is performed in a second computer.

28. The memory medium of claim 26,

wherein the at least one type has a first name;

wherein said determining if the type conflicts comprises determining if the first name of the at least one type conflicts with a name of one of said previously loaded/registered types;

wherein said creating and said storing are performed in a first computer;

wherein said loading the file is performed in a second computer, wherein the second computer includes a different type which includes said first name.

29. The memory medium of claim 17, wherein said types comprise a data structure;

wherein the program instructions are further executable to implement;

conforming existing instances of one or more non-selected types with the selected type, wherein said conforming comprises modifying the data structure of the one or more non-selected types to conform to the data structure of the selected type.

30. The memory medium of claim 17, wherein the program instructions are further executable to implement:

conforming existing instances of one or more non-selected types with the selected type, wherein said conforming includes preserving at least a portion of old data of the one or more non-selected types.

31. The memory medium of claim 17, wherein the version data comprises one or more of:

user-entered version data, or date and time information.

32. A method for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), the method comprising:

loading a file with at least one type, wherein the at least one type includes version data;

determining the type being loaded in response to said loading;

determining if the type conflicts with one or more previously loaded/registered types, wherein said determining includes comparing the type being loaded with the previously loaded/registered types in the system;

determining that the version data of the at least one type and the one or more previously loaded/registered types are the same after determining a type conflict;

receiving user input regarding selection of a type in response to said determining that the version data are the same;

selecting a type in response to said user input;

registering the at least one type in the system in response to selecting the at least one type.

33. A method for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), the method comprising:

creating at least one type and assigning a first name to the at least one type in response to user input;

storing a step or data of the at least one type in a file;

loading the file with the at least one type, wherein the at least one type includes version data;

wherein said creating and said storing are performed in a first computer;

wherein said loading the file is performed in a second computer, wherein the second computer includes a different type which includes said first name;

wherein the method further comprises;

determining the type being loaded in response to said loading;

determining that the type conflicts with the different type, wherein said determining includes determining that the first name of the at least one type conflicts with the name of the different type;

selecting a type based on the version data in response to determining the type conflict.

34. A method for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), the method comprising:

loading a file with at least one type, wherein the at least one type includes version data;

determining the type being loaded in response to said loading;

determining that the type conflicts with one or more previously loaded/registered types, wherein said determining includes comparing the type being loaded with the previously loaded/registered types in the system;

selecting a type based on the version data in response to determining the type conflict; and

conforming existing instances of one or more non-selected types with the selected type, wherein said conforming comprises modifying a data structure of the one or more non-selected types to conform to a data structure of the selected type.

35. A memory medium comprising program instructions for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), wherein, in response to loading a file with at least one type, wherein the at least one type includes version data, the program instructions are executable to implement:

determining the at least one type being loaded in response to said loading;

determining that the at least one type conflicts with one or more previously loaded/registered types, wherein said determining includes comparing the at least one type being loaded with the previously loaded/registered types in the system;

determining that the version data of the at least one type and the one or more previously loaded/registered types are the same after determining the type conflict;

receiving user input regarding selection of a type in response to said determining that the version data are the same;

selecting a type in response to said user input;

registering the at least one type in the system in response to selecting the at least one type.

36. A memory medium comprising program instructions for managing types in a test executive system, wherein the test executive system is used for creating test programs for testing one or more units under test (UUTs), wherein, in response to loading a file with at least one type, wherein the at least one type includes version data, the program instructions are executable to implement:

determining the type being loaded in response to said loading;

determining that the type conflicts with one or more previously loaded/registered types, wherein said determining includes comparing the type being loaded with the previously loaded/registered types in the system;

selecting a type based on the version data in response to determining the type conflict; and

conforming existing instances of one or more non-selected types with the selected type, wherein said conforming comprises modifying a data structure of the one or more non-selected types to conform to a data structure of the selected type.

37. A method for managing types in a test executive system, the method comprising:

loading a test executive sequence file including a first data type;

determining the first data type being loaded in response to said loading;

determining that the first data type conflicts with a previously registered data type in the system, wherein said determining includes comparing the first data type with the previously registered data type;

prompting for user input selecting either the first data type or the previously registered data type in response to said determining that the first data type conflicts with the previously registered data type; and

selecting either the first data type or the previously registered data type in response to said user input.