System and method for automatically testing software programs

• US 6,002,869 A
• Filed: 02/26/1997
• Issued: 12/14/1999
• Est. Priority Date: 02/26/1997
• Status: Expired due to Term

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Hinckley, David N.
• Primary Examiner(s): Trammell, James P.
• Assistant Examiner(s): Nguyen, Cuong H.
• Application Number:
  US08/806,390
• Time in Patent Office: 1,021 Days
• Field of Search: 395/701, 395/704, 395/183.13, 395/183.22, 395/183.08, 395/183.09, 395/682, 395/685, 702/108, 371/27.1, 324/73.1, 714/38, 714/35, 714/36
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable

Abstract

A test automation system for performing functional tests of a software program. The system includes a plurality of test functions each configured to test a discrete component of the software program. a user-defined test specification associated with the program provides state definitions that specify a desired test approach for each type of test procedure to be performed on the program. A test engine creates all test cases appropriate for a user-selected test type and controls the software program, applying the test functions and state definitions in accordance with the test specification. All test-specific and software program-specific data are located in the user-defined test functions and specifications while all generic test system processing resides in the test engine. The test specifications are preferably implemented in modifiable text files to maintain concurrency with an evolving software program. The test engine creates all possible permutations and combinations for performing a desired test. These test specification includes such items as the states that the software program may possess, the test functions required to transfer between one state and other possible states, information pertaining to the values that specific inputs may have, etc. During operation, the test engine generates test histories indicating the results of the test performed in accordance with one of the test specifications. The contents of the test histories include determination made by the test functions executed in accordance with an associated test specification.

Claims

1. A computer based test automation system for functionally testing a software program, comprising:

at least one test function, each configured to test and associated with a discrete functional component of the software program;

at least one user-defined test specification file containing state definitions associated with the software program, said state definitions defining which of said at least one test function the test engine must execute to advance the program from a state to a next state after each of said at least one test function is successfully completed; and

a test engine configured to perform a test procedure in accordance with said at least one test specification, said test procedure including the execution of one or more of said at least one test function.

2. The system of claim 1, wherein said at least one test specification file is implemented in a text file accessible to said test engine.

3. The system of claim 1, wherein said state definitions of said at least one test specification file comprises:

one or more states that the software program may possess;

for each of said one or more states, one or more potential next states, each defining a state transition; and

for each of said one or more state transitions, a pointer to one of said at least one test function that causes said state transition.

4. The system of claim 3, wherein said test engine provides a user with a test history of said test procedure, said test history comprising:

each of said one or more states that the software program possessed during said test procedure; and

which of said at least one test function caused the software program to transition to each of said one or more next states.

5. The system of claim 4, wherein said test history is implemented in a text file accessible to said test engine.

6. The system of claim 4, wherein said test engine comprises:

a test function executor configured to execute said at least one test function, said test function executor operating with a software controller to control execution of the software program; and

a test case generator configured to cause, in accordance with said at least one test specification, said test function executor to execute a specific one or more of said test functions to cause said state transitions in the software program.

7. The system of claim 6, wherein said test engine further comprises:

a test specification file reader for reading said at least one user-created test specification file in response to requests from said test case generator.

8. A computer based system for functionally testing a software program, comprising:

a plurality of user-defined test function means for testing associated discrete portions of the software program;

a plurality of test specification means for identifying functional state relationships of the software program, said specification means defining which of said plurality of test function means the test engine must execute to advance the program from a state to a next-state after each of said plurality of test function means is successfully completed; and

test engine means for performing a test procedure in accordance with one of said test specification means to cause the execution of one of said plurality of test function means.

9. The system of claim 8, wherein each of said plurality of test specification means comprises:

one or more states that the software program may possess;

for each of said one or more states, one or more potential next states each defining a state transition; and

for each of said one or more state transitions, a pointer to one of said one or more test functions that causes said state transition.

10. The system of claim 9, wherein said test engine means provides a user with results of said test procedure, said results comprising:

each of said one or more states that the software program possessed during said test procedure; and

which of said plurality of test functions caused each state transition.

11. The system of claim 10, wherein said test engine means comprises:

test function executor means for executing said plurality of test function means, said test function executor means operating with a software controller to control execution of the software program; and

test case generator means for causing, in accordance with said test specification means, said test function executor means to execute a specific one or more of said test function means to cause said state transitions in the software program.

12. A computer based test engine for performing test procedures on a software program, said program having a plurality of states, the test engine comprising:

test function executor means for executing user-created test functions on discrete functional components of said program, each of said test functions being associated with one of said discrete functional components;

state definition input means for accepting user-created state definitions which define which of said test functions the test engine must execute to advance the program from a state to a next state after each of said test functions are successfully completed; and

test case generation means for determining, when the program is in a first state, which of said plurality of states will be said next state;

wherein said test case generator means instructs said test function executor means which of said test functions to execute on the software program to advance the program from said first state to said next state.

13. The test engine of claim 12, wherein, upon executing each of said test functions on the software program, said test function executor means informs said test case generator means whether or not the software program successfully executed each of said test functions.

14. The test engine of claim 13, further comprising:

test history creator means, responsive to said test case generator means, for storing each state, each corresponding next state and each corresponding test function which advances the software program from each state to each next state, to a test history file.

15. The test engine of claim 14, wherein said test case generator means utilizes said test history files to instruct said test function executor means to perform previously-performed test procedures.

21. The test engine of claim 15, further comprising:

means for testing said test functions prior to using said test functions to test the software program.

16. A method of testing software having a plurality of states, the method comprising the steps of:

a) receiving user-created test functions, each associated with and configured to test a predetermined discrete portion of the software program and to output results of said test;

b) receiving user-created state definitions, each of said state definitions including a current state, a next state and an identifier of at least one of said test functions which causes a transition of the software program from a current state to a next state after each of said test functions are successfully completed; and

c) executing said at least one of said test functions to cause a transition of the software program from each of said current states to each of said next states.

17. The method of claim 16, further comprising the steps of:

d) writing each next state and test function executed to a test history file; and

e) writing test-related information to said test history file.

18. The method of claim 17, further comprising the step of:

f) using said test history file to perform further testing of said software.

19. The method of claim 18, further comprising the step of:

g) recording, in said test history file, an elapsed time between each transition.

20. A computer program product comprising a computer readable medium having a computer program logic thereon for enabling a processor in a computer system to automatically perform tests on a software program, the computer system having a memory, accessible to said processor, in which is stored a test specification file containing state definitions associated with the software program, said software program having a plurality of states the product comprising:

test engine means for testing discrete portions of said software program in accordance with the test specification file, said test engine means performing a plurality of test functions on the software program, each of said test functions being associated with and testing one of said discrete portions of said software program, wherein, when each of said test functions are successfully performed, said software program transitions from a current state to a next state, wherein said test engine means determines whether said software program transitioned correctly.