Generation of correctly ordered test code for testing software components

• US 6,823,281 B2
• Filed: 10/11/2001
• Issued: 11/23/2004
• Est. Priority Date: 10/20/2000
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Empirix Incorporated (Empirix Holdings I, Inc.)
• Inventors: Makar-Limanov, Sergei, Glik, Michael, Friedman, George
• Primary Examiner(s): Hoff, Marc S.
• Assistant Examiner(s): SUAREZ, FELIX E
• Application Number:
  US09/975,568
• Publication Number:
  US 20020059039A1
• Time in Patent Office: 1,139 Days
• Field of Search: 702/79, 702/81, 702/90, 702/107, 702/109, 702/119, 702/120, 702/83, 702/84, 702/118, 702/182, 702/197, 706/50, 706/45, 709/203, 712/233, 712/300, 715/501.1
• US Class Current: 702/119
• CPC Class Codes: G06F 11/28 by checking the correct order of processing G06F11/08 - G06F11/26 take precedence; monitoring patterns of pulse trains H03K5/19
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: H04L 43/50 Testing arrangements

Abstract

The present invention to provide correctly ordered test code in order to effectively test software designs. There are software diagramming tools on the market today that capture software designs in a standard meta-language (UML). This software provides sequence diagrams that relate to the software component being analyzed. The UML sequence diagrams expose enough semantic content to allow the generation of test code correctly ordered. Since all of the objects are modeled consistently, the data requirements of the software component can also be determined. As a result, the generated test code is correctly ordered, thereby providing a more accurate, useful and real-world testing environment of the software component.

Claims

1. A method of correctly ordering test code for testing software components comprising the steps of:

generating test code for testing a software component;

utilizing a software diagramming tool to provide at least one sequence diagram of said software component; and

ordering said test code in accordance with said sequence diagram to provide properly ordered test code.

2. The method of claim 1 wherein said software component is selected from the group comprising COM, DCOM, COM+, Corba, and EJB.

3. The method of claim 1 wherein said step of generating test code comprises the step of determining at least one method of said software component.

4. The method of claim 3 further comprising the step of evaluating said at least one method to determine the type of data required to test said at least one method.

5. The method of claim 3 further comprising the step of evaluating said at least one method to determine parameters to be passed to said at least one method in order to test said at least one method of said software component.

6. A computer program product comprising a computer usable medium having computer readable code thereon for correctly ordering test code for testing software components, the computer readable code comprising:

instructions for generating test code for testing a software component;

instructions for utilizing a software diagramming tool to provide at least one sequence diagram of said software component; and

instructions for ordering said test code in accordance with said sequence diagram to provide properly ordered test code.

7. The computer program product of claim 6 wherein said software component is selected from the group comprising COM, DCOM, COM+, Corba, and EJB.

8. The computer program product of claim 6 wherein said instructions for generating test code further comprise instructions for determining at least one method of said software component.

9. The computer program product of claim 8 further comprising instructions for evaluating said at least one method to determine the type of data required to test said at least one method.

10. The computer program product of claim 8 further comprising instructions for evaluating said at least one method to determine parameters to be passed to said at least one method in order to test said at least one method of said software component.