Automated testing system

• US 5,390,325 A
• Filed: 12/23/1992
• Issued: 02/14/1995
• Est. Priority Date: 12/23/1992
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Taligent, Inc. (HP Inc.)
• Inventors: Miller, Christopher M.
• Primary Examiner(s): Canney, Vincent P.
• Assistant Examiner(s): LE, DIEU MINH T
• Application Number:
  US07/996,047
• Time in Patent Office: 783 Days
• Field of Search: 395/575, 395/425, 395/725, 395/600, 395/800, 395/500, 395/700, 371/15.1, 371/10.1, 371/18, 371/16.1, 371/27.1, 371/28.1, 371/29.1, 371/22.4, 371/25.1, 371/22.6, 371/22.1, 364/487, 364/481, 364/424.04, 364/424.03, 364/550, 364/571.01, 364/231, 364/578
• US Class Current: 714/38.14
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

An object-oriented automated testing system and method tests program subroutines which operate on parameter data objects to generate results. Tests determine whether the subroutines meet design specifications provided by test engineers in the form of precondition objects and postcondition objects. The precondition objects comprise data invariant objects and functional precondition objects and are applied to a generated pool of candidate parameter data objects to check data syntax and data semantics, respectively before the parameter data is applied to the subroutines. Each parameter data object belongs to a predetermined data type and the precondition objects are written for generic data types and associated with each parameter data object during the testing process. The subroutines are run with the checked data by an automatically generated test program. After the subroutines have been run the results are checked for proper syntax and semantics by the postconditions to determine whether design specifications have been met.

Claims

1. A system for automated testing of a software program comprising parameter data and a subroutine operating on the parameter data to generate output data, the system comprising:

memory means for storing the software program and the parameter data;

processor means for controlling and coordinating the operation of the system and the memory means;

first invariant means responsive to parameter data stored in the memory means for generating a data consistent signal when the parameter data stored in the memory means is internally consistent;

precondition means responsive to the parameter data stored in the memory means and to the subroutine for generating a data valid signal when the parameter data stored in the memory means will operate with the subroutine without causing an error condition;

means responsive to the data consistent signal and to the data valid signal for running the subroutine with the parameter data stored in the memory means; and

postcondition means responsive to the parameter data stored in the memory means and to output data generated by the subroutine from the parameter data stored in the memory means for determining whether an error occurred during operation of the subroutine.

2. A system for automated testing of a software program according to claim 1 further comprising command interpreter means for receiving user commands and wrapper generator means responsive to the user commands for generating wrapper code for running the subroutine with the parameter data stored in the memory means.

3. A system for automated testing of a software program according to claim 1 wherein the precondition means comprise error checking means responsive to the data valid signal for discontinuing automated testing when the data valid signal indicates that the parameter data stored in the memory means is not valid.

4. A system for automated testing of a software program according to claim 1 further comprising second invariant means responsive to the parameter data stored in the memory means and operable after the subroutine has been run for determining whether the parameter data stored in the memory means is still internally consistent.

5. A system for automated testing of a software program according to claim 1 wherein the subroutine requires parameter data with a plurality of predetermined data types and wherein the first invariant means comprises:

means for generating a plurality of test sets of parameter data, each of the plurality of test sets of parameter data having data with one of the plurality of predetermined data types; and

first selecting means responsive to the plurality of test sets of parameter data for selecting test sets of parameter data in which the parameter data is internally consistent.

6. A system for automated testing of a software program according to claim 5 wherein the precondition means comprises second selecting means responsive to selected test sets of parameter data for further selecting test sets of parameter data in which the parameter data will operate with the subroutine without causing an error condition.

7. A system for automated testing of a software program according to claim 6 wherein the first invariant means comprises:

an invariant rule for each of the plurality of predetermined data types; and

association means responsive to each of the plurality of predetermined data types for associating an invariant rule with each of the plurality of test sets of parameter data.

8. An object-oriented system for testing whether a subroutine, operating on parameter data objects with internal data states to generate output data, meets design requirements, the system comprising:

memory means for storing the subroutine and the parameter data objects;

processor means for controlling and coordinating the operation of the system and the memory means;

first invariant objects responsive to parameter data objects stored in the memory means for selecting candidate parameter data objects with a correct data syntax to operate with the subroutine and meet design requirements;

precondition objects responsive to the candidate parameter data objects for selecting valid parameter data objects with correct data semantics to operate with the subroutine and meet design requirements;

means responsive to user commands for running the subroutine with the valid parameter data objects; and

postcondition objects responsive to the valid parameter data objects and to output data generated by the subroutine from the valid parameter data objects for determining whether the subroutine met design requirements.

9. An object-oriented system for testing whether a subroutine meets design requirements according to claim 8 further comprising command interpreter means for receiving user commands and wrapper generator means responsive to the user commands for generating wrapper code for running the subroutine with the valid parameter data objects.

10. An object-oriented system for testing whether a subroutine meets design requirements according to claim 8 wherein each of the precondition objects comprises error checking subroutines for discontinuing testing when the valid parameter data objects will not operate with the subroutine and meet design requirements.

11. An object-oriented system for testing whether a subroutine meets design requirements according to claim 8 further comprising second invariant objects responsive to the valid parameter data objects and operable after the subroutine has been run for determining whether the valid parameter data objects still have the correct data syntax.

12. An object-oriented system for testing whether a subroutine meets design requirements according to claim 8 wherein the subroutine requires parameter data with a plurality of predetermined data types and wherein the first invariant objects comprise:

means for generating a plurality of test sets of parameter data, each of the plurality of test sets of parameter data having data with one of the plurality of predetermined data types; and

means for associating one of the first invariant objects with each of the plurality of test sets of parameter data.