Determination of software functionality

Claim 3

A method according to claim 1 further including preparing said test plan.

Claim 4

A method according to claim 2 further including preparing said set of test scripts.

Claim 5

A method according to claim 1 wherein the user interface software invokes each test script of said sequence of test scripts in the test plan and presents each script to the software testing interface program so that the latter also reads the script as a recording made earlier by the software testing interface program.

Claim 6

A method according to claim 1 wherein the user interface software includes at least a graphical user interface, a test script definition language parser, a test plan parser which generates a set of action codes for each test plan, and an interpreter which responds to the action codes and interacts with the software system under test.

Claim 7

A method according to claim 1 wherein the user interface software checks the test plans for syntax errors prior to running.

Claim 8

A method according to claim 1 wherein the parameter inputs for test scripts after the first include parameter inputs derived from recorded outputs of earlier test scripts.

Claim 9

A method according to claim 1 wherein running of each of the test plans includes recordal of an inheritance file containing the values returned by test scripts while the test plan was running.

Claim 10

A method according to claim 1 wherein said test scripts are written in a simple programming language, and include a mix of general routines selected from the language, and routines specific to said software system.

Claim 11

A method according to claim 1 wherein the inputting and logging steps are carried out in computer apparatus in which the software testing interface program is installed and which includes memory means in which the test scripts and test plans are stored.

Claim 12

A method according to claim 1 further including generating a response indicative of functionality of the software system.

Claim 15

A method according to claim 12 wherein the parameter inputs for test scripts after the first include parameter inputs derived from recorded outputs of earlier test scripts.

Claim 16

A method according to claim 12 wherein running of each of the test plans includes recordal of an inheritance file containing the values returning by test scripts while the test plan was running.

Claim 17

A method according to claim 12 wherein said test scripts are written in a simple programming language, such as visual basic, and include a mix of general routines selected from the language, and routines specific to said software system.

Claim 18

A method according to claim 12 further including preparing said test plan.

Claim 19

A method according to claim 16 further including preparing said set of test scripts.

Claim 20

A method according to claim 12 wherein the inputting and logging steps are carried out in computer apparatus in which the software testing interface program is installed and which includes memory means in which the test scripts and test plans are stored.

Claim 21

A method according to claim 12 further including generating a response indicative of functionality of the software system.

Claim 24

A method according to claim 20 further including preparing said test plan.

Claim 25

A method according to claim 21 further including preparing said set of test scripts.

Claim 26

A method according to claim 20 wherein the parameter inputs for test scripts after the first include parameter inputs derived from recorded outputs of earlier test scripts.

Claim 27

A method according to claim 20 wherein running of each of the test plans includes recordal of an inheritance file containing the values returned by test scripts while the test plan was running.

Claim 28

A method according to claim 20 wherein said test scripts are written in a simple programming language, such as visual basic, and include a mix of general routines selected from the language, and routines specific to said software system.

Claim 29

A method according to claim 20 wherein the inputting and logging steps are carried out in computer apparatus in which the software testing interface program is installed and which includes memory means in which the test scripts and test plans are stored.

Claim 30

A method according to claim 20 further including generating a response indicative of functionality of the software system.

Claim 31

Computer apparatus for determining the functionality of a software system, including: first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program, said user interface software communicating with the software testing interface program as if it were a recording made earlier by the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s).

Claim 32

Computer apparatus for determining the functionality of a software system, including: first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program, said user interface software communicating with the software testing interface program as if it were a recording made earlier by the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s).

Claim 33

Apparatus according to claim 28 wherein, in use of the apparatus, the user interface software invokes the test script identified in the test plan and presents each script to the software testing interface program so that the latter also reads the script as a recording made earlier by the software testing interface program.

Claim 34

Apparatus according to claim 28 wherein the parameter inputs for test scripts after the first include parameter inputs derived from recorded outputs of earlier test scripts.

Claim 35

Apparatus according to claim 28 wherein the test plans include generator utility functions to uniquely generate and/or identify parameter values.

Claim 36

Apparatus according to claim 28 wherein the test plan(s) are written in a characteristic language utilising names for the respective test scripts, an established sequence for parameter inputs, identifiers for the respective parameters, parameter generator notation, and parameter broker notation instructing derivation of parameter inputs from recorded outputs of other test scripts.

Claim 37

Apparatus according to claim 28, further including third memory means to store an inheritance file containing the values returned by test scripts while the test plan was running.

Claim 38

Apparatus according to claim 28 wherein the user interface software includes at least a graphical user interface, a test script definition language parser, a test plan parser which generates a set of action codes for each test plan, and an interpreter which responds to the action codes and interacts with the software system.

Claim 39

Apparatus according to claim 28 wherein the test scripts are characterised if their operation for a first user affects other users of said software system.

Claim 40

Apparatus according to claim 28 wherein the user interface software includes provision to check the test plan(s) for syntax errors prior to running.

Claim 43

A method according to claim 37 wherein the parameter inputs for test scripts after the first include parameter inputs derived from recorded outputs of earlier test scripts.

Claim 44

A method according to claim 37 wherein generator utility functions are employed in test plans to uniquely generate and/or identify parameter values.

Claim 45

A method according to claim 37 wherein the test plans are written in a characteristic language utilising names for the respective test scripts, an established sequence for parameter inputs, identifiers for the respective parameters, parameter generator notation, and parameter broker notation instructing derivation of parameter inputs from recorded outputs of other test scripts.

Claim 46

A method according to claim 37 wherein running of each of the test plans includes recordal of an inheritance file containing the values returned by test scripts while the test plan was running.

Claim 47

A method according to claim 37 wherein said test scripts are written in the language of the software system under test, and include a mix of general routines selected from the language, and routines specific to said software system.

Claim 48

A method according to claim 37 wherein the user interface software includes at least a graphical user interface, a test script definition language parser, a test plan parser which generates a set of action codes for each test plan, and an interpreter which responds to the action codes and interacts with said software system.

Claim 49

A method according to claim 37 wherein the test scripts are characterised if their operation for a first user affects other users of said software system.

Claim 50

A method according to claim 37 wherein the user interface software checks the test plans for syntax errors prior to running.

Claim 51

A method according to claim 37 wherein the inputting and logging steps are carried out in computer apparatus in which the test scripts and test plans are stored in memory means and in which the software testing program is installed and logging steps are carried out in computer apparatus in which the software testing interface program is installed and which includes memory means in which the test scripts and test plans are stored.

Claim 52

A method according to claim 37 further including generating a response indicative of functionality of the software system.

Claim 53

Computer apparatus for determining the functionality of a software system, including: first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting the test plan(s) to the software system via the software testing interface program and running the test plan; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s); wherein the user interface software is arranged for presenting each test script to the software testing interface program so that the latter if it were a recording made earlier by the software testing interface program.

Claim 54

Computer apparatus for determining the functionality of a software system, including: first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting the test plan(s) to the software system via the software testing interface program and running the test plan; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s); wherein the user interface software is arranged for presenting each test script to the software testing interface program so that the latter if it were a recording made earlier by the software testing interface program.

Claim 55

Apparatus according to claim 48 wherein the parameter inputs for test scripts after the first include parameter inputs derived from recorded outputs of earlier test scripts.

Claim 56

Apparatus according to claim 48 wherein the test plans include generator utility functions to uniquely generate and/or identify parameter values.

Claim 57

Apparatus according to claim 48 wherein the test plan(s) are written in a characteristic language utilising names for the respective test scripts, an established sequence for parameter inputs, identifiers for the respective parameters, parameter generator notation, and parameter broker notation instructing derivation of parameter inputs from recorded outputs of other test scripts.

Claim 58

Apparatus according to claim 48, further including third memory means to store an inheritance file containing the values returned by test scripts while the test plan was running.

Claim 59

Apparatus according to claim 48 wherein the user interface software includes at least a graphical user interface, a test script definition language parser, a test plan parser which generates a set of action codes for each test plan, and an interpreter which responds to the action codes and interacts with said software system.

Claim 60

Apparatus according to claim 48 wherein the test scripts are characterised if their operation for a first user affects other users of said software system.

Claim 61

Apparatus according to claim 48 wherein the user interface software includes provision to check the test plan(s) for syntax errors prior to running.

Claim 62

Computer apparatus for determining the functionality of a software system, including; first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script, wherein the test plan(s) are written in a characteristic language utilizing names for the respective test scripts, an established sequence for parameter inputs, identifiers for the respective parameters, parameter generator notation, and parameter broker notation instructing derivation of parameter inputs from recorded outputs of other test scripts; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s).

Claim 63

Computer apparatus for determining the functionality of a software system, including; first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script, wherein the test plan(s) are written in a characteristic language utilizing names for the respective test scripts, an established sequence for parameter inputs, identifiers for the respective parameters, parameter generator notation, and parameter broker notation instructing derivation of parameter inputs from recorded outputs of other test scripts; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s).

Claim 64

Computer apparatus for determining the functionality of a software system, including: first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s); wherein the user interface software includes at least a graphical user interface, a test script definition language parser, a test plan parser which generates a set of action codes for each test plan, and an interpreter which responds to the action codes and interacts with said software system.

Claim 65

Computer apparatus for determining the functionality of a software system, including: first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s); wherein the user interface software includes at least a graphical user interface, a test script definition language parser, a test plan parser which generates a set of action codes for each test plan, and an interpreter which responds to the action codes and interacts with said software system.

Claim 66

Computer apparatus for determining the functionality of a software system, including; first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed, which test scripts are characterised if their operation for a first user affects other users of said software system; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s).

Claim 67

Computer apparatus for determining the functionality of a software system, including; first memory means to store a set of test scripts each able, when input to the software system via a software testing interface program, to prompt performance of a transaction or function for which the software system is designed, which test scripts are characterised if their operation for a first user affects other users of said software system; second memory means to store one or more test plans each invoking a sequence of said test scripts and including associated parameter inputs for the test scripts and an expected output of the transaction or function of each test script; computing means, including installed user interface software and an installed software testing interface program, and operatively connectable to said first and second memory means, for selectively inputting and running the test plan(s) to the software system via the software testing interface program; and logging means for logging an indication of one or more resulting outputs of the software system compared to expected output(s).