Integration testing method for object-oriented software

• US 5,615,333 A
• Filed: 05/11/1995
• Issued: 03/25/1997
• Est. Priority Date: 05/11/1994
• Status: Expired due to Fees

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Zimmerer, Peter, Naumann, Udo, Juettner, Peter, Kolb, Sebald
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): DECADY, ALBERT
• Application Number:
  US08/438,846
• Time in Patent Office: 684 Days
• Field of Search: 395/183.01, 395/183.13, 395/183.14, 364/267.91, 364/275.5, 364/274.1
• US Class Current: 714/38.13
• CPC Class Codes: G06F 11/3676 for coverage analysis
• CPC Class Codes: G06F 9/4488 Object-oriented

Abstract

A method for integration testing of all objects of an object-oriented program in which an analysis of its source code is first carried out in order to identify the mutual dependencies between objects and classes and, on the basis of these dependencies, those objects that have already been tested are allocated to a set of tested objects and, further, objects that are dependent only on these tested objects are also identified. These objects are tested and are subsequently added to the set of tested objects. When no object can be found that is dependent only on tested objects, those objects are sought that are dependent only on one additional, untested object. This untested object can then be replaced by an object stub for test purposes. The object thus tested is subsequently transferred into the set of tested objects. When objects are found that are dependent only on one another and form a cycle, then one of these is replaced by an object stub in order to be able to test the other. As a result, all objects of the object-oriented program to be tested are united in the set of tested objects and the entire program is tested.

Claims

1. An integration test method for an object-oriented computer program comprising the following steps:

a) conducting a source code analysis of a structural relationship between objects in the object-oriented program;

b) identifying mutual dependencies between at least two objects and/or object classes by way of the source code analysis of the structural relationships of the object-oriented program;

c) allocating a tested object and/or an object derived from a tested class to a set of tested objects; and

d) identifying at least one object with the assistance of the structural relationship of the source code, said at least one object being dependent only on objects of the set of tested objects; and

e) testing uses of said object.

2. The method according to claim 1, whereby a correct constructor is automatically identified for testing an object with the source code and with the relationship structure, said constructor serving the purpose of generating the object for the integration test.

3. The method according to claim 2, whereby the object to be tested is automatically brought into a status as required for the integration test, being brought thereinto by a constructor call upon employment of the source code and by copying data components.

4. The method according to any of claims 1-3, whereby a method call with which the object is tested is derived from the relationship structure for the testing of an object.

5. The method according to any of claims 1-3, whereby, when no object is identified that is dependent only on objects of the set of tested objects, then an object that is additionally dependent on optimally few untested objects is identified and tested.

6. The method according to claim 5, whereby an untested object is replaced by an object stub.

7. The method according to claim 5, said method being executed until an untested object is no longer present.

8. The method according to any of claims 1-3, whereby at least one of those objects that, due to the relationship structure, are only dependent on one another and not on objects of the set of tested objects, is replaced by an object stub in order to test another object.

9. An integration test method for a object-oriented computer program comprising the following steps:

a) analyzing a source code for the object-oriented program to identify mutual dependencies between objects, such analysis being an analysis of structural relationships between said objects;

b) identifying mutual dependencies between at least two objects and/or object classes by way of such analysis;

c) identifying all objects that have not been tested and use only standard data types or objects that have already been tested and objects whose uses can only be tested in a common testing step;

d) allocating to a set of tested objects any objects that have already been tested and variables of standard types;

e) identifying at least one object by way of the structural relationship of the source code which is dependent only on objects of the set of tested objects; and

f) testing uses of said object.

10. The method according to claim 9, whereby a correct constructor is automatically identified for testing an object with the source code and with the relationship structure, said constructor serving the purpose of generating the object for the integration test.

11. The method according to claim 9, whereby the object to be tested is automatically brought into a status as required for the integration test, being brought thereinto by a constructor call upon employment of the source code and by copying data components.

12. The method of claim 9, whereby a method call with which the object is tested is derived from the relationship structure for the testing of an object.

13. The method of claim 9, whereby, when no object is identified the is dependent only on objects of the set of tested objects, then an object that is additionally dependent on optimally few untested objects is identified and tested.

14. The method of claim 13, whereby an untested object is replaced by an object stub.

15. The method of claim 13, said method being executed until an untested object is no longer present.

16. The method of claim 9, whereby at least one of those objects that, due to the relationship structure, are only dependent on one another and not on objects of the set of tested objects is replaced by an object stub in order to test another object.

17. An integration test method for an object-oriented computer program whose objects have been tested previously, comprising the following steps:

(a) conducting a source code analysis of a structural relationship between the previously tested objects in the object-oriented program;

(b) identifying mutual dependencies between at least two objects and/or object classes by way of the source code analysis of the structural relationships of the object-oriented program;

(c) allocating a tested object and/or an object derived from a tested class to a set of tested objects;

(d) identifying at least one object with the assistance of the structural relationship of the source code, said at least one object being dependent only on objects on the set of tested objects; and

(e) testing uses of said at least one described object.

19. The method according to claim 17, whereby a correct constructor is automatically identified for testing an object with the source code and with the relationship structure, said constructor serving the purpose of generating the object for the integration test.

21. The method according to any of claims 17-20, whereby, when no object is identified that is dependent only on objects of the set of tested objects, then an object that is additionally dependent on optimally few untested objects is identified and tested.

22. The method according to claim 21, whereby an untested object is replaced by an object stub.

23. The method according to any of claims 17-20, whereby at least one of those objects that, due to the relationship structure, are only dependent on one another and not on objects of the set of tested objects is replaced by an object stub in order to test another object.

24. The method according to claim 21, said method being executed until an untested object is no longer present.

18. An integration test method for an object-oriented program whose objects were previously tested, comprising the following steps executed automatically by a computer:

(a) conducting a source code analysis of a structural relationship between objects in the object-oriented program;

(b) identifying mutual dependencies between at least two objects and/or object classes by way of the source code analysis of the structural relationships of the object-oriented program;

(c) allocating a tested object and/or an object derived from a tested class to a set of tested objects;

(d) identifying at least one object with the assistance of the structural relationship of the source code, said at least one object being dependent only on objects of the set of tested objects; and

(e) testing uses of said object.

20. The method according to claim 18, whereby the object to be tested is automatically brought into a status as required for the integration test, being brought thereinto by a constructor call upon employment of the source code and by copying data components.

25. An integration test method for an object-oriented computer program whose objects were previously tested, comprising the following steps executed by a computer:

(a) analyzing a source code for the object-oriented program to identify mutual dependencies between objects, such analysis being an analysis of structural relationships between said objects;

(b) identifying mutual dependencies between at least two objects and/or object classes by way of such analysis;

(c) identifying all objects that have not been tested and use only standard data types or objects that have already been tested and objects whose uses can only be tested in a common testing step;

(d) allocating to a set of tested objects any objects that have already been tested in variables of standard types;

(e) identifying at least one object by way of the structural relationship of the source code which is dependent only on objects of the set of tested objects; and

(f) testing uses of said object.

26. The method according to claim 25, whereby a correct constructor is automatically identified for testing an object with the source code and with the relationship structure, said constructor serving the purpose of generating the object for the integration test.

27. The method according to claim 25, whereby the object to be tested is automatically brought into a status as required for the integration test, being brought thereinto by a constructor call upon employment of the source code and by copying data components.

28. The method of claim 25, whereby, when no object is identified that is dependent only on objects of the set of tested objects, then an object that is additionally dependent on optimally few untested objects is identified and tested.

29. The method of claim 28, whereby an untested object is replaced by an object stub.

30. The method of claim 28, said method being executed until an untested object is no longer present.

31. The method of claim 25, whereby at least one of those objects that, due to the relationship structure, are only dependent on one another and not on objects of the set of tested objects, is replaced by an object stub in order to test another object.