Method of testing interfaces between computer program modules

• US 4,595,981 A
• Filed: 03/05/1984
• Issued: 06/17/1986
• Est. Priority Date: 03/05/1984
• Status: Expired due to Term

• Current Assignee: Bell Telephone Laboratories, Inc. (Nokia Corporation)
• Original Assignee: AT&T, Inc.
• Inventors: Leung, Wu-Hon F.
• Primary Examiner(s): Zache, Raulfe B.
• Application Number:
  US06/586,291
• Time in Patent Office: 834 Days
• Field of Search: 364/300, 371/19
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable

Abstract

A method of testing interfaces between computer program modules. The individual cause/effect charts of each of the modules are used to test the interfaces between the modules by executing the test cases in the charts in such manner that each test case need only be executed once. The variables passed between modules are monitored and compared with the input conditions in the charts.

Claims

1. A method of operating a digital computer to test an interface between a first program module and a second program module, each of said first and second program modules having associated input variables and an associated cause/effect chart comprising a plurality of cases each having an input condition comprising values of input variables, said method comprising

initiating the execution of said first program module,

suspending the execution of said first program module at a point where said first program module calls said second program module and

verifying that the values of those input variables associated with said second program module that are defined at the time the execution of said first program module is suspended, are consistent with the input condition of at least one of the cases of the cause/effect chart associated with said second program module.

2. A method of operating a digital computer to test an interface between a first program module and a second program module, each of said first and second program modules having associated input variables and an associated cause/effect chart comprising a plurality of cases each having an input condition comprising values of input variables, said method comprising

initiating the execution of said first program module,

suspending the execution of said first program module at a point where said first program module calls said second program module,

executing said second program module and

verifying that the value of those input variables associated with said first program module that are defined at the time that the execution of said second program module is completed, are consistent with the input condition of at least one of the cases of the cause/effect chart associated with said first program module.

3. A method of testing an interface between a first program module and a second program module wherein said first program module, when executed on a digital computer, calls said second program module and wherein each of said first and second program modules has associated input variables and an associated cause/effect chart comprising a plurality of cases each having an input condition comprising values of input variables, said method comprising

generating a first error indication upon a determination that the values of those input variables associated with said second program module that are defined at the time that said first program module calls said second program module, are not consistent with the input condition of any of the cases of the cause/effect chart associated with said second program module,

executing said second program module and

generating a second error indication upon a determination that the values of those input variables associated with said first program module that are defined at the time that the execution of said second program module is completed, are not consistent with the input condition of any of the cases of the cause/effect chart associated with said first program module.

4. A method of operating a digital computer to test an interface between a first program module and a second program module, each of said first and second program modules having associated input variables and an associated cause/effect chart comprising a plurality of cases each having an input condition comprising values of input variables, said method comprising

storing said first program module and the cause/effect chart associated with said first program module,

storing said second program module and the cause/effect chart associated with said second program module,

initiating the execution of said first program module,

suspending the execution of said first program module at a point where said first program module calls said second program module and

generating a first error indication upon a determination that the values of those input variables associated with said second program module that are defined at the time that the execution of said first program module is suspended, are not consistent with the input condition of any of the cases of said stored cause/effect chart associated with said second program module.

5. A method in accordance with claim 4 further comprising

executing said second program module and

generating a second error indication upon a determination that the values of those input variables associated with said first program module that are defined at the time that the execution of said second program module is completed, are not consistent with the input condition of any of the cases of said stored cause/effect chart associated with said first program module.

6. A method of operating a digital computer to verify an interface between a first program module and a second program module, each of said first and second program modules having associated input variables and an associated cause/effect chart comprising a plurality of cases each having an input condition comprising values of input variables, said method comprising the steps of

(A) storing said first program module and the cause/effect chart associated with said first program module,

(B) storing said second program module and the cause/effect chart associated with said second program module,

(C) initializing the input variables associated with said first program module that are arguments and the input variables associated with said first program module that are external variables, in accordance with the input condition of at least one unexecuted case in said stored cause/effect chart associated with said first program module,

(D) initiating the execution of said first program module,

(E) suspending the execution of said first program module at a point where said first program module calls said second program module and

(F) verifying that the values of the input variables associated with said second program module that are defined at the time that the execution of said first program module is suspended, define a base equivalence class of cases in said stored cause/effect chart associated with said second program module.

7. A method in accordance with claim 6 further comprising the steps of

(G) executing said second program module once for each case in said base equivalence class not previously executed, with the input variables associated with said second program module initialized in accordance with the input condition of that case, and

(H) upon completion of each execution of said second program module in said step (G), verifying that the values of the input variables associated with said first program module that are then defined, are consistent with the input condition of at least one case in a current equivalence class of cases in said stored cause/effect chart associated with said first program module, said current equivalence class being defined by the values of the input variables associated with said first program module that are defined at the time that the execution of said first program module is suspended.

8. A method in accordance with claim 7 further comprising the steps of

(I) upon completion of each execution of said second program module in said step (G), recording the values of the input variables associated with said first program module that are then defined and

(J) verifying that the input condition of at least one unexecuted case in said current equivalence class is consistent with the values of the input variables associated with said first program module that were recorded in said step (I) following at least one of the executions of said second program module in said step (G).

9. A method in accordance with claim 8 further comprising the steps of

(K) selecting one unexecuted case in said current equivalence class having an input condition that is consistent with the values of the input variables associated with said first program module that were recorded in said step (I) following at least one of the executions of said second program module in said step (G),

(L) assigning to the input variables associated with said first program module, values consistent with the input condition of said selected case and

(M) completing the execution of said first program module.

10. A method in accordance with claim 9 further comprising the step

(N) repeating said steps (C), (D), (E), (F), (G), (H), (I), (J), (K), (L) and (M) until each case in said stored cause/effect chart associated with said first program module has been executed.

11. A method in accordance with claim 6 further comprising the steps of

(G) determining an expanded base equivalence class of cases in said stored cause/effect chart associated with said second program module, said expanded base equivalence class being defined by the values of the input variables associated with said second program module that are defined at the time that the execution of said first program module is suspended but that are not live variables of said first program module,

(H) executing said second program module once for each case in said expanded base equivalence class not previously executed, with the input variables associated with said second program module initialized in accordance with the input condition of that case, and

(I) upon completion of each execution of said second program module in said step (H), verifying that the values of the input variables associated with said first program module that are then defined, are consistent with the input condition of at least one case in a current equivalence class of cases in said stored cause/effect chart associated with said first program module, said current equivalence class being defined by the values of the input variables associated with said first program module that are defined at the time that the execution of said first program module is suspended.

12. A method of operating a digital computer to verify an interface between a first program module and a second program module, each of said first and second program modules having associated input variables and an associated cause/effect chart comprising a plurality of cases each having an input condition comprising values of input variables, said method comprising the steps of

(A) storing said first program module and the cause/effect chart associated with said first program module,

(B) storing said second program module and the cause/effect chart associated with said second program module,

(C) initializing the input variables associated with said first program module that are arguments and the input variables associated with said first program module that are external variables, in accordance with the input condition of at least one case that is marked as not exercised, of the cases in said stored cause/effect chart associated with said first program module,

(D) initiating the execution of said first program module,

(E) suspending the execution of said first program module at a point where said first program module calls said second program module and

(F) verifying that the values of the input variables associated with said second program module that are defined at the time that the execution of said first program module is suspended, define a base equivalence class of cases in said stored cause/effect chart associated with said second program module.

13. A method in accordance with claim 12 further comprising the steps of

(G) storing the present values of input variables associated with said second program module that are external variables and of input variables associated with any program module transitively called by said second program module that are external variables,

(H) executing said second program module once for each case in said base equivalence class that is marked as not exercised, with the input variables associated with said second program module initialized in accordance with the input condition of that case, and

(I) upon completion of each execution of said second program module in said step (H), verifying that the values of the input variables associated with said first program module that are then defined, are consistent with the input condition of at least one case in a current equivalence class of cases in said stored cause/effect chart associated with said first program module, said current equivalence class being defined by the values of the input variables associated with said first program module that are defined at the time that the execution of said first program module is suspended.

14. A method in accordance with claim 13 further comprising the steps of

(J) upon completion of each execution of said second program module in said step (H), recording the values of the input variables associated with said first program module that are then defined,

(K) upon completion of each execution of said second program module in said step (H), marking as exercised a case of said stored cause/effect chart associated with said second program module having an input condition that is consistent with the values of the input variables associated with said second program module as then defined,

(L) upon completion of each execution of said second program module in said step (H), assigning the values stored in said step (G) to said input variables associated with said second program module that are external variables and said input variables associated with any program module transitively called by said second program module that are external variables and

(M) verifying that the input condition of at least one case in said current equivalence class that is marked as not exercised, is consistent with the values of the input variables associated with said first program module that were recorded in said step (J) following at least one of the executions of said second program module in said step (H).

15. A method in accordance with claim 14 further comprising the steps of

(N) selecting one case in said current equivalence class that is marked as not exercised and that has an input condition that is consistent with the values of the input variables associated with said first program module that were recorded in said step (J) following at least one of the executions of said second program module in said step (H),

(O) assigning to the input variables associated with said first program module, values consistent with the input condition of said selected case,

(P) completing the execution of said first program module and

(Q) marking as exercised a case of said stored cause/effect chart associated with said first program module having an input condition that is consistent with the values of the input variables associated with said first program module.

16. A method in accordance with claim 15 further comprising the step

(R) repeating said steps (C), (D), (E), (F), (G), (H), (I), (J), (K), (L), (M), (N), (O), (P) and (Q) until each case in said stored cause/effect chart associated with said first program module has been marked as exercised.

17. A method in accordance with claim 16 wherein said second program module has a set of live variables, said method further comprising the step

(O) before said storing step (G), marking as not exercised, at least one case in said stored cause/effect chart associated with said second program module, upon a determination that the values of said set of live variables following the present suspension of the execution of said first program module in said step (E), differ from the values of said set of live variables following previous suspensions of the execution of said first program module in said step (E).

18. A method in accordance with claim 16 wherein said second program module has a set of live variables, said method further comprising the steps of

(O) after said verifying step (F) and upon a determination that the present values of said set of live variables differ from values of said set of live variables stored in a live variable table associated with said second program module, marking the cases of said base equivalence class defined in said step (F) as not exercised and

(P) upon said determination that the present values of said set of live variables differ from values of said set of live variables stored in said live variable table associated with said second program module, storing the present values of said set of live variables in said live variable table associated with said second program module.