Generic software testing system and mechanism

• US 20040143819A1
• Filed: 01/09/2004
• Published: 07/22/2004
• Est. Priority Date: 01/10/2003
• Status: Abandoned Application

• Current Assignee: National Cheng KUNG University (Government of The Republic of China)
• Original Assignee: National Cheng KUNG University (Government of The Republic of China)
• Inventors: Wang, Chin-Hui, Cheng, Fan-Tien, Su, Yu-Chuan, Wu, Shung-Lun
• Application Number:
  US10/753,349
• Publication Number:
  US 20040143819A1
• Time in Patent Office: Days
• US Class Current: 717/125
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A generic software testing system and mechanism is disclosed for use in distributed object-oriented systems. The present invention directly utilizes class diagrams (or interface definitions) and sequence diagrams to automatically generate the execution codes and test template required for testing the software system, wherein the class diagram data, the interface definition data and the sequence diagram data are generated by a software development tool of distributed object-oriented system. The present invention is applicable to the tests of a software system of which the functions and operations can be presented merely with class diagrams (or interface definitions) and sequence diagrams generated by the tools used during software development, wherein the software system can be as small as an individual unit (component) or module, or as large as an entire distributed object-oriented system. The present invention enables the software implementation and the software test planning to be performed at the same time. When the software implementation is done, the software test can be followed immediately to generate test results, so that the functions and performance of the software system can be evaluated.

Claims

1. A generic software testing system, provided for a distributed object-oriented system to perform a test, wherein said generic software testing system comprises:

a test-plan wizard, generating test-plan execution codes and a test-result template in accordance with class-diagram related data and sequence-diagram related data;

a tested software unit/system, executing said test plan execution codes to generate a test result; and

a comparator, comparing said test result with said test-result template to generate a test report.

2. The generic software testing system of claim 1, wherein said class-diagram related data comprises a plurality of I/O interface definitions, said I/O interface definitions defining I/O interfaces of a plurality of modules in said distributed object-oriented system.

3. The generic software testing system of claim 1, wherein said class-diagram related data comprises a plurality of class diagrams.

4. The generic software testing system of claim 3, wherein said class diagram are generated by development tools using UML (Unified Model Language).

5. The generic software testing system of claim 1, wherein said sequence-diagram related data comprises a testing sequence diagram, and said testing sequence diagram is selected from a plurality of sequence diagrams.

6. The generic software testing system of claim 5, wherein said sequence diagram are generated by development tools using UML.

7. The generic software testing system of claim 1, wherein said test-plan wizard comprises:

a class-diagram parser, used for parsing said class-diagram related data so as to obtain a class information diagram;

a sequence-diagram parser, used for parsing said sequence-diagram related data so as to obtain a sequence information diagram;

a test-plan generator, generating a test plan in accordance with said class information diagram, said sequence information diagram and a plurality of scenarios in said sequence information diagram;

a reference I/O editor, wherein said reference I/O editor generates an input/output interface so as to input a plurality of reference input values and a plurality of reference output values, and then builds a test-result template in accordance with said test plan, said reference input values and said reference output values; and

a test-code generator, generating said test codes in accordance with said test plan and said reference input values.

8. The generic software testing system of claim 1, wherein said distributed object-oriented system is composed of a plurality of units, and said class-diagram related data is the data of interface definition diagram for said units, and said sequence-diagram related data is the data of relationship diagram among said units.

9. The generic software testing system of claim 8, wherein said distributed object-oriented system uses CORBA (Common Object Request Broker Architecture) as the communication fundamental structure, and an IDL (Interface Definition Language) file is used for showing the data of interface definition diagram of said units, and the data of relationship diagram among said units.

10. The generic software testing system of claim 9, wherein said test-result template comprises a plurality of entries used for said distributed object-oriented system to perform non-functional tests.

11. The generic software testing system of claim 9, wherein said entries further comprises a first entry for showing the number of repeated executions, a second entry for showing the interval of repeated executions, and a third entry for showing the record of execution time.

12. A generic software testing mechanism, used for a distributed object-oriented system to perform a test, wherein said generic software testing mechanism comprises:

inputting class-diagram related data to a test-plan wizard as a basis of said test;

selecting a testing sequence diagram from sequence-diagram related data for use in said test, and inputting the data of said testing sequence diagram to said test-plan wizard;

filling a plurality of reference input values and a plurality of output values with respect to said testing sequence diagram;

generating a test-result template containing said reference input values and said reference output values by said test-plan wizard;

passing said test-result template to a comparator;

generating test-plan execution codes by said test-plan wizard;

executing said test-plan execution codes by a tested software unit/system for performing said test so as to generate a test result, wherein said tested software unit/system is corresponding to said class-diagram related data and said sequence-diagram related data;

passing said test result to said comparator; and

creating a test report by said comparator.

13. The generic software testing mechanism of claim 12, wherein said class-diagram related data comprises a plurality of I/O interface definitions, said I/O interface definitions defining I/O interfaces of a plurality of modules in said distributed object-oriented system.

14. The generic software testing mechanism of claim 12, wherein said class-diagram related data comprises a plurality of class diagrams.

15. The generic software testing mechanism of claim 14, wherein said class diagram are generated by development tools using UML.

16. The generic software testing mechanism of claim 12, wherein said testing sequence diagram is selected from a plurality of sequence diagrams.

17. The generic software testing mechanism of claim 16, wherein said sequence diagram are generated by development tools using UML.

18. The generic software testing mechanism of claim 12, further comprising:

parsing said class-diagram related diagram by a class-diagram parser of said test-plan wizard, so as to obtain a class information diagram;

parsing said sequence-diagram related diagram by a sequence-diagram parser of said test-plan wizard, so as to obtain a sequence information diagram;

generating a test plan by a test-plan generator of said test-plan wizard in accordance with said class information diagram, said sequence information diagram and a plurality of scenarios in said sequence information diagram;

generating an input/output interface by a reference I/O editor of said test-plan wizard, so as to input a plurality of reference input values and a plurality of reference output values.

building a test-result template by said reference I/O editor in accordance with said test plan, said reference input values and said reference output values; and

generating said test codes by a test-code generator of said test-plan wizard in accordance with said test plan and said reference input values.

19. The generic software testing mechanism of claim 12, wherein said distributed object-oriented system is composed of a plurality of units, and said class-diagram related data is the data of interface definition diagram for said units, and said sequence-diagram related data is the data of relationship diagram among said units.

20. The generic software testing mechanism of claim 19, wherein said distributed object-oriented system uses CORBA as the communication fundamental structure, and an IDL file is used for showing the data of interface definition diagram of said units, and the data of relationship diagram among said units.

21. The generic software testing mechanism of claim 20, wherein said test-result template comprises a plurality of entries used for said distributed object-oriented system to perform non-functional tests.

22. The generic software testing mechanism of claim 21, wherein said entries further comprises a first entry for showing the number of repeated executions, a second entry for showing the interval of repeated executions, and a third entry for showing the record of execution time.