Method and apparatus for testing object-oriented programming constructs

• US 5,737,609 A
• Filed: 10/18/1994
• Issued: 04/07/1998
• Est. Priority Date: 10/18/1994
• Status: Expired due to Fees

• Current Assignee: Infor Global Solutions Michigan Incorporated (Infor Incorporated)
• Original Assignee: Marcam Corporation
• Inventors: Aibel, Jonathan B., Reed, Harvey G., Dalton, John T., Sciandra, Stephen A.
• Primary Examiner(s): Kriess, Kevin A.
• Assistant Examiner(s): Chavis, John Q.
• Application Number:
  US08/324,810
• Time in Patent Office: 1,267 Days
• Field of Search: 395/650, 395/700, 395/701, 395/704
• US Class Current: 717/126
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 8/78 Methods to solve the "Year 2000" [Y2K] problem

Abstract

The invention provides methods and apparatus for generating, from a source signal defining a subject class to be tested, an inspection signal defining an inspection class that has one or more members for (i) generating a test object as an instantiation of the subject class or a class derived therefrom, (ii) invoking one or more selected method members of the test object, and (iii) generating a reporting signal based upon an outcome of invocation of those members. he inspection class, as defined by the inspection signal, can include one or more method members, referred to as "inspection members," for testing corresponding method members of the test object (and, therefore, in the subject class). So-called "test suite members," that are also defined as part of the inspection class, exercise the inspection members. The invention also provides methods and apparatus for responding to an inspection signal to create an inspection object instantiating the inspection class. Members of the inspection object are invoked to create the test object, to invoke method members thereof and to generate a signal reporting an effect of such invocation. The test object members can be invoked by corresponding inspection members of the inspection class, which in turn can be invoked by test suite members of the inspection class.

Claims

1. A method for testing a subject class in an object-oriented digital data processing system, said method comprising the step of:

(A) responding to a source signal defining said subject class to generate an inspection signal defining an inspection class having one or more members for

(i) creating a test object as an instantiation of any of said subject class and a class derived therefrom,

(ii) invoking one or more selected method members of said test object,

(iii) generating a signal, hereinafter referred to as a report signal, reporting an effect of such invocation.

2. A method according to claim 1, comprising

(B) responding to said source signal to generate a test signal defining a test class that comprises any of

(i) said subject class, and

(ii) an instantiable class derived from said subject class, and

step (A)(i) includes the step of generating said inspection signal to define said inspection class to include one or more members for creating said test object as an instantiation of said test class.

3. A method according to claim 2, wherein

step (B) includes the step of generating said test signal to define an instantiable test class that inherits one or more members of said subject class.

4. A method according to claim 3, wherein

step (B) includes the step of generating said test signal to define said test class to substantially duplicate pure virtual functions of said subject class, absent constructs that denote those functions as having both pure and virtual attributes.

5. A method according to claim 3, wherein

step (B) includes the step of generating said test signal to define said test class to substantially duplicate at least one constructor and a destructor of said subject class.

6. A method according to claim 3, wherein

step (B) includes the step of generating said test signal to define said test class to give instantiations of said inspection class access to members of said subject class.

7. A method according to claim 1, wherein

step (A) includes the step of generating said inspection signal to define said inspection class to include one or more method members, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

8. A method according to claim 7, wherein

step (A) includes the step of generating said inspection signal to define said inspection members to include method member functions corresponding to at least one constructor in said test object, wherein each of those method member functions take substantially the same arguments as the corresponding constructor in said test object.

9. A method according to claim 7, wherein

step (A) includes the step of generating said inspection signal to define said inspection members to include method member functions corresponding to a destructor in said test object.

10. A method according to claim 7, wherein

step (A) includes the step of generating said inspection signal to define said inspection members to include method member functions corresponding to at least one operator function in said test object.

11. A method according to claim 7, wherein

step (A) includes the step of generating said inspection signal to define said inspection members to have function names similar to those of the corresponding method members of the test object that they test.

12. A method according to claim 7, wherein

step (A) includes the step of generating said inspection signal to define said inspection class to include one or more method members, referred to hereinafter as test suite members, for exercising one or more of said inspection members.

13. A method according to claim 12, wherein

step (A) includes the step of generating said inspection signal to define said test suite members to include one or more members for at least one of

(i) testing for memory leaks in connection with at least one of creation and destruction of said test object,

(ii) testing accessor and transformer members of said test object,

(iii) testing operator member methods of said test object,

(iv) testing members involved in persistence of said test object, and

(v) testing method members semantically unique to said test object.

14. A method according to claim 12, wherein

step (A) includes the step of generating said inspection signal to define said inspection class to include one or more method members, hereinafter referred to as test run members, for invoking said one or more test suite members.

15. A method according to claim 12, wherein

step (A) includes the step of generating said inspection signal to define said inspection class to comprise one or more method members providing common services for invocation by said test suite members.

16. A method according to claim 12, wherein

step (A) includes the step of generating said inspection signal to define said inspection class to comprise one or more method members providing common reporting services for invocation by said test suite members.

17. A method according to claim 1, comprising the step of

(B) responding to said inspection signal to create an inspection object as an instantiation of said inspection class, and

(C) invoking one or more members of said inspection object to

(i) create said test object,

(ii) invoke one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation.

18. A method according to claim 17, wherein

step (C)(ii) includes the step of preventing exceptions that occur during invocation of said one or more selected method members from discontinuing execution of steps (C)(ii) and C(iii).

19. A method according to claim 17, wherein

step (C)(iii) includes comparing said result of such invocation with one or more expected values thereof, and generating said report signal to be indicative of such comparison.

20. A method according to claim 17, wherein

said method includes the step of executing step (B) a plurality of times, each for invoking a different group of one or more selected method members of said test object.

21. A method according to claim 17, wherein

step (C)(ii) includes applying at least one argument to one or more of said selected method members of said test object in connection with invocation thereof.

22. A method according to claim 21, wherein

step (C)(i) includes applying at least one argument to a constructor member of said test object in connection with creation thereof.

23. A method according to claim 17, wherein

step (C)(iii) includes the step of storing said report signal in a data member of said inspection object.

24. A method according to claim 23, wherein

step (C)(iii) includes the step of generating said report signal to be indicative of at least one of

(i) a comparison of results of invocation of one or more method members of said test object with one or more expected values thereof, and

(ii) detection of a memory leak.

25. A method according to claim 23, wherein step (C)(iii) includes the step of storing in said data member of said inspection object a signal indicative of a number of errors incurred in connection with invocation of said one or more selected method members of said test object.

26. A method according to claim 25, wherein

step (C)(iii) includes the step of storing in said data member of said inspection object a signal indicating coverage of testing associated with invocation of said one or more method members of said test object.

27. A method according to claim 17, wherein

step (C)(ii) includes the step of invoking one or more method members of said inspection object, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

28. A method according to claim 27, wherein

step (C)(ii) includes the step of invoking one or more method members one or more members of said inspection object, referred to hereinafter as test suite members, for exercising one or more of said inspection members.

29. A method according to claim 28, wherein

step (C)(ii) includes the step of invoking one or more test suite members to at least one of

(i) test for memory leaks in connection with at least one of creation and destruction of said test object,

(ii) test accessor and transformer members of said test object,

(iii) test operator member methods of said test object,

(iv) test members involved in persistence of said test object, and

(v) test method members semantically unique to said test object.

30. A method according to claim 28, wherein

step (C)(ii) includes the step invoking one or more method members of said inspection object for invoking one or more test suite members.

31. A method according to claim 17, wherein

step (B)(i) includes the step of placing said digital data processor in a mode of a desired runtime environment.

32. A method according to any of claims 18-24, comprising:

invoking one or more method members of said inspection object to generate said report signal.

33. A method according to any of claims 32, comprising:

responding to a verbosity control signal to generate report signals with a selected level of verbosity.

34. A method for testing a subject class in an object-oriented digital data processing system, said method comprising:

(A) creating an inspection object as an instantiation of an inspection class having one or more members for

(i) creating a test object as an instantiation of any of said subject class and a class derived therefrom,

(ii) invoking one or more selected method members of said test object,

(iii) generating a signal, hereinafter referred to as a report signal, reporting an effect of such invocation

(B) invoking one or more members of said inspection object to

(i) create said test object,

(ii) invoke one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation.

35. A method according to claim 34, wherein

step (B)(i) includes the step of creating said test object as an instantiation of a test class that comprises any of

(a) said subject class, and

(b) an instantiable class derived from said subject class.

36. A method according to claim 34, wherein

step (B)(ii) includes applying at least one argument to one or more of said selected method members of said test object in connection with invocation thereof.

37. A method according to claim 36, wherein

step (B)(ii) includes applying at least one argument to a constructor member of said test object in connection with creation of said test object.

38. A method according to claim 34, wherein

step (B)(ii) includes the step of preventing exceptions that occur during invocation of said one or more selected method members from discontinuing execution of steps (B)(ii) and (B)(iii).

39. A method according to claim 34, wherein

step (B)(iii) includes comparing said result of such invocation with one or more expected values thereof, and generating said report signal to be indicative of such comparison.

40. A method according to claim 39, wherein

step (B)(iii) includes the step of storing a signal indicative of said effects in a data member of said inspection object.

41. A method according to claim 34, wherein

said method includes the step of executing step (B) a plurality of times, each for invoking a different group of one or more selected method members of said test object.

42. A method according to claim 41, wherein

step (B)(iii) includes the step of generating said report signal to be indicative of at least one of

(i) comparison of results of invocation of one or more method members of said test object with one or more expected values thereof, and

(ii) detection of a memory leak.

43. A method according to claim 34, wherein

step (B)(ii) includes the step of invoking one or more method members of said inspection object, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

44. A method according to claim 43, wherein

step (B)(ii) includes the step of invoking one or more method members of said inspection object, referred to hereinafter as test suite members, for exercising one or more of said inspection members.

45. A method according to claim 44, wherein

step (B)(ii) includes the step of invoking one or more test suite members to at least one of

(i) test for memory leaks in connection with at least one of creation and destruction of said test object,

(ii) test accessor and transformer members of said test object,

(iii) test operator member methods of said test object,

(iv) test members involved in persistence of said test object, and

(v) test method members semantically unique to said test object.

46. A method according to claim 44, wherein

step (B)(ii) includes the step invoking one or more method members of said inspection object for invoking one or more test suite members.

47. A method according to claim 34, wherein

step (B)(i) includes the step of placing said digital data processor in a desired runtime environment.

48. A method according to any of claims 38-42, comprising:

invoking one or more method members of said inspection object to generate said report signal.

49. A method according to any of claims 48, comprising:

responding to a verbosity control signal to generate said report signal with a selected level of verbosity.

50. Apparatus for testing a subject class in an object-oriented digital data processing system, said apparatus comprising:

(A) code generator means for responding to a source signal defining said subject class to generate an inspection signal defining an inspection class having one or more members for

(i) creating a test object as an instantiation of any of said subject class and a class derived therefrom,

(ii) invoking one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation, and

(B) test harness means, coupled to said code generator means, for responding to said inspection signal for creating an inspection object instantiating said inspection class, and for generating an inspection object invocation signal for invoking one or more members thereof.

51. An apparatus according to claim 50, wherein

said code generator means includes test class generating means for responding to said source signal to generate a test signal defining a test class that comprises any of

(i) said subject class, and

(ii) an instantiable class derived from said subject class, and wherein

said code generator further includes means for generating said inspection signal to define said inspection class to include one or more members for creating said test object as an instantiation of said test class.

52. An apparatus according to claim 50, wherein

said code generator means includes means for generating said inspection signal to define said inspection class to include one or more method members, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

53. An apparatus according to claim 52, wherein

said code generator means includes means for generating said inspection signal to define said inspection class to include one or more method members, referred to hereinafter as test suite members, for exercising one or more of said inspection members.

54. An apparatus according to claim 53, wherein

said code generator means includes means for generating said inspection signal to define said inspection class to include one or more method members, hereinafter referred to as run members, for invoking said one or more test suite members.

55. An apparatus according to claim 53, wherein

said code generator means includes means for generating said inspection signal to define said inspection class to include one or more method members providing common services for invocation by said test suite members.

56. An apparatus according to claim 53, wherein

said code generator means includes means for generating said inspection signal to define said inspection class to include one or more method members providing common reporting services for invocation by said test suite members.

57. An apparatus according to claim 50, comprising:

(A) inspection object execution means, coupled to said test harness means, for responding to said inspection object invocation signal for

(i) creating said test object,

(ii) generating a test object invocation signal to invoke one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation,

(B) test object execution means, coupled to said inspection object execution means, for responding to said test object invocation signal to execute one or more selected method members thereof.

58. An apparatus according to claim 57, wherein

said inspection object execution means includes means for creating said test object as an instantiation of a test class that comprises any of

(a) said subject class, and

(b) an instantiable class derived from said subject class.

59. An apparatus according to claim 57, wherein

said inspection object execution means includes means for applying at least one argument to one or more of said selected method members of said test object in connection with invocation thereof.

60. An apparatus according to claim 57, wherein

said inspection object execution means includes exception service means preventing exceptions that occur during invocation of said one or more selected method members from discontinuing at least reporting on effects of invocation of said test object.

61. An apparatus according to claim 57, wherein

said inspection object execution means includes means for comparing a result of invocation of said one or more selected method members of said test object with expected results of such invocation, and for generating said report signal to be indicative of such comparison.

62. An apparatus according to any of claims 57 and 59, wherein

said inspection object execution means includes means for executing one or more member methods of said inspection object to generate said report signal.

63. An apparatus according to any of claims 61, wherein:

said inspection object execution means includes means responding to a verbosity control signal to generate said report signals with a selected level of verbosity.

64. An apparatus according to claim 57, wherein

said inspection object execution means includes means for executing one or more method members of said inspection object, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

65. An apparatus according to claim 64, wherein

said inspection object execution means includes means for executing one or more members of said inspection object, referred to hereinafter as test suite members, for exercising one or more of said inspection members.

66. An apparatus according to claim 65, wherein

said inspection object execution means includes means for executing said test suite members for at least one of

(i) testing for memory leaks in connection with at least one of creation and destruction of said test object,

(ii) testing accessor and transformer members of said test object,

(iii) testing operator member methods of said test object,

(iv) testing members involved in persistence of said test object, and

(v) testing method members semantically unique to said test object.

67. An apparatus according to claim 65, wherein

said inspection object execution means includes means for executing a method member of said inspection object for invoking one or more test suite members.

68. An apparatus according to claim 57, wherein

said inspection object execution means includes means for placing said digital data processor in a desired runtime environment.

69. Apparatus for testing a subject class in an object-oriented digital data processing system, said apparatus comprising:

test harness means for responding to an inspection signal defining an inspection class having one or more members for

(i) creating a test object as an instantiation of any of said subject class and a class derived therefrom,

(ii) invoking one or more selected method members of said test object,

(iii) generating a signal, hereinafter referred to as a report signal, reporting an effect of such invocation

for creating an inspection object instantiating an inspection class, and for generating an inspection object invocation signal for invoking one or members thereof,

(B) inspection object execution means, coupled to said test harness means, for responding to said inspection object invocation signal for

(i) creating said test object,

(ii) generating a test object invocation signal to invoke one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation,

(C) test object execution means, coupled to said inspection object execution means, for responding to said test object invocation signal to execute one or more selected method members thereof.

70. An apparatus according to claim 69, wherein

said inspection object execution means includes means for creating said test object as an instantiation of a test class that comprises any of

(a) said subject class, and

(b) an instantiable class derived from said subject class.

71. An apparatus according to claim 69, wherein

said inspection object execution means includes means for applying at least one argument to one or more of said selected method members of said test object in connection with invocation thereof.

72. An apparatus according to claim 69, wherein

said inspection object execution means includes exception service means preventing exceptions that occur during invocation of said one or more selected method members from discontinuing at least reporting on effects of invocation of said test object.

73. An apparatus according to claim 69, wherein

said inspection object execution means includes means for comparing a result of invocation of said one or more selected method members of said test object with expected results of such invocation, and for generating said report signal to be indicative of such comparison.

74. An apparatus according to any of claims 69 and 73, wherein

said inspection object execution means includes means for executing one or more member methods of said inspection object to generate said report signal.

75. An apparatus according to any of claims 69, wherein:

said inspection object execution means includes means responding to a verbosity control signal to generate said report signals with corresponding verbosity.

76. An apparatus according to claim 69, wherein

said inspection object execution means includes means for executing one or more method members of said inspection object, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

77. An apparatus according to claim 76, wherein

said inspection object execution means includes means for executing one or more members of said inspection object, referred to hereinafter as test suite members, for exercising one or more of said inspection members.

78. An apparatus according to claim 77, wherein

said inspection object execution means includes means for executing said test suite members for at least one of

(i) testing for memory leaks in connection with at least one of creation and destruction of said test object,

(ii) testing accessor and transformer members of said test object,

(iii) testing operator member methods of said test object,

(iv) testing members involved in persistence of said test object, and

(v) testing method members semantically unique to said test object.

79. An apparatus according to claim 77, wherein

said inspection object execution means includes means for executing a method member of said inspection object for invoking one or more test suite members.

80. An apparatus according to claim 69, wherein

said inspection object execution means includes means for placing said digital data processor in a desired runtime environment.

81. An object-oriented computer program having a subject class tested by a method comprising the step of:

(A) responding to a source signal defining said subject class to generate inspection signal defining an inspection class having one or more members for

(i) creating a test object as an instantiation of any of said subject class and a class derived therefrom,

(ii) invoking one or more selected method members of said test object,

(iii) generating a signal, hereinafter referred to as a report signal, reporting an effect of such invocation.

82. A method according to claim 81, comprising an additional step of

(B) responding to said source signal to generate a test signal defining a test class that comprises any of

(i) said subject class, and

(ii) an instantiable class derived from said subject class, and step (A)(i) includes the step of generating said inspection signal to define said inspection class to include one or more members for creating said test object as an instantiation of said test class.

83. A method according to claim 81, wherein

step (A) includes the step of generating said inspection signal to define said inspection class to include one or more method members, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

84. A method according to claim 81, comprising the step of

(B) responding to said inspection signal to create an inspection object as an instantiation of said inspection class, and

(C) invoking one or more members of said inspection object to

(i) create said test object,

(ii) invoke one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation.

85. An object-oriented computer program having a subject class tested by a method comprising:

(A) creating an inspection object as an instantiation of an inspection class having one or more members for

(i) creating a test object as an instantiation of any of said subject class and a class derived therefrom,

(ii) invoking one or more selected method members of said test object,

(iii) generating a signal, hereinafter referred to as a report signal, reporting an effect of such invocation

(B) invoking one or more members of said inspection object to

(i) create said test object,

(ii) invoke one or more selected method members of said test object,

(iii) generate a signal, hereinafter referred to as a report signal, reporting an effect of such invocation.

86. A method according to claim 85, wherein

step (B)(i) includes the step of creating said test object as an instantiation of a test class that comprises any of

(a) said subject class, and

(b) an instantiable class derived from said subject class.

87. A method according to claim 85, wherein

step (B)(ii) includes applying at least one argument to one or more of said selected method members of said test object in connection with invocation thereof.

88. A method according to claim 85, wherein

step (B)(ii) includes the step of preventing exceptions that occur during invocation of said one or more selected method members from discontinuing execution of steps (B)(ii) and (B)(iii).

89. A method according to claim 85, wherein

step (B)(iii) includes comparing said result of such invocation with one or more expected values thereof, and generating said report signal to be indicative of such comparison.

90. A method according to claim 85, wherein

said method includes the step of executing step (B) a plurality of times, each for invoking a different group of one or more selected method members of said test object.

91. A method according to claim 85, wherein

step (B)(ii) includes the step of invoking one or more method members of said inspection object, referred to hereinafter as inspection members, for testing corresponding method members of said test object.

92. A method according to claim 85, wherein

step (B)(i) includes the step of placing said digital data processor in a desired runtime environment.