SYSTEM AND METHOD FOR GENERATING DATA SETS FOR TESTING EMBEDDED SYSTEMS

• US 20080016498A1
• Filed: 06/26/2007
• Published: 01/17/2008
• Est. Priority Date: 03/23/2001
• Status: Abandoned Application

• Current Assignee: S2 Technologies, Inc.
• Original Assignee: S2 Technologies, Inc.
• Inventors: Howell, Robert, Underseth, Mark, Fertitta, Kirk
• Application Number:
  US11/768,853
• Publication Number:
  US 20080016498A1
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 2209/546 Xcast
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A system and method for providing seamless communication with threads executing on an embedded computer. Using a DAT system, a programmer can test the communication interfaces of a thread via either a scripting program, any COM-compliant program, or a graphical test utility. The DAT system automatically formats a block of data that is transmitted between the embedded computer and a host computer and accounts for machine specific enumeration sizes, machine specific pointer sizes, machine specific structure alignment boundaries, machine specific integer sizes, and machine specific byte ordering.

Claims

1. A method for testing a routine, the method comprising:

receiving identifications of a plurality of communication data paths to be traced;

monitoring data transmitted across the plurality of received communication data paths;

storing the monitored data in a plurality of persistent data objects;

determining a thread to receive data from one of the persistent data objects; and

transmitting the data from the one of the persistent data objects across one of the communication data paths.

2. The method of claim 1, wherein the communication data paths comprise communication between a host device and an embedded device.

3. The method of claim 1, further comprising receiving user input to determine a thread to receive data from one of the persistent data objects.

4. The method of claim 1, wherein the receiving identifications of a plurality of communication data paths to be traced comprises receiving identifications of a plurality of one or more of messages and remote function calls.

5. The method of claim 1, further comprising receiving a persistent data object identification to indicate which of the plurality of persistent data objects is the one of the persistent data objects.

6. The method of claim 1, further comprising receiving a communication data path identification to indicate which of the plurality of communication data paths is the one of the communication data paths.

7. The method of claim 1, further comprising displaying one or more of the communication interfaces.

8. A method for testing a routine, the method comprising:

displaying a plurality of communication interfaces between a host device and an embedded device;

receiving user input to identify a selected communication interface from the plurality of communication interfaces;

displaying a communication window comprising remote function calls of the selected communication interface;

receiving user input for instructions to store data generated from a displayed remote function call; and

receiving user input for instructions to load the stored data.

9. The method of claim 8, further comprising determining whether the remote function call is a two-way call;

and displaying a command and a response window including one or more data set fields upon determination that the remote function call is a two-way call.

10. The method of claim 8, further comprising displaying at least one parameter field associated with the remote function call.

11. The method of claim 10, further comprising receiving user input to set values of one or more parameters from the at least one parameter field, wherein the stored data is data generated using the set values of the one or more parameters.

12. The method of claim 8, further comprising a graphical user interface configured to receive at least one of the user inputs.

13. The method of claim 8, further comprising a graphical user interface configured to receive all of the user inputs.

14. The method of claim 8, further comprising receiving user input for one or more interface definition files that define the selected communication interface.

15. The method of claim 14, further comprising generating a code template of a thread for handling a message in one of the selected interface definition files.

16. The method of claim 15, further comprising indicating to the user to add to the generated code.

17. The method of claim 14, further comprising generating a code template of a thread for handling each of the messages in one of the selected interface definition files.

18. A system for testing a routine, the method comprising:

means for receiving identifications of a plurality of communication data paths to be traced;

means for monitoring data transmitted across the plurality of received communication data paths;

means for storing the monitored data in a plurality of persistent data objects;

means for determining a thread to receive data from one of the persistent data objects; and

means for transmitting the data from the one of the persistent data objects across one of the communication data paths.

19. The system of claim 18, wherein means for receiving identifications of a plurality of communication data paths to be traced comprises a graphical user interface.

20. A system for testing a routine, the method comprising:

means for displaying a plurality of communication interfaces between a host device and an embedded device;

means for receiving user input to identify a selected communication interface from the plurality of communication interfaces;

means for displaying a communication window comprising remote function calls of the selected communication interface;

means for receiving user input for instructions to store data generated from a displayed remote function call; and

means for receiving user input for instructions to load the stored data.

21. The system of claim 20, wherein one or more of the means for receiving user input comprises a graphical user interface.

22. A system for testing a routine, the method comprising one or more modules configured to perform the functions of:

receiving identifications of a plurality of communication data paths to be traced;

monitoring data transmitted across the plurality of received communication data paths;

storing the monitored data in a plurality of persistent data objects;

determining a thread to receive data from one of the persistent data objects; and

transmitting the data from the one of the persistent data objects across one of the communication data paths.

23. A system for testing a routine, the method comprising one or more modules configured to perform the functions of:

displaying a plurality of communication interfaces between a host device and an embedded device,

receiving user input to identify a selected communication interface from the plurality of communication interfaces;

displaying a communication window comprising remote function calls of the selected communication interface;

receiving user input for instructions to store data generated from a displayed remote function call; and

receiving user input for instructions to load the stored data.