System for testing interactive software

Abstract: A method for testing host resident interactive software. The host resident interactive software is first executed while an interactive test case is captured. The test case is then executed on another version of the interactive software. The differences between the versions of the interactive software are detected and subsequently presented. Another function of the method of the present invention is to allow complete document­ ation of perceived errors in host resident interactive software.

Description: The present invention relates to a system for testing interactive software and, more particularly, to a system for automatically testing and comparing versions of interactive software. In the development of software products, people responsible for producing error free software or code have heretofore had difficulty in testing different versions or levels of the code as they mature and reach the intended level of sophistication and functionality. Such tests are required to identify areas that should be evaluated by the software developer and corrected, if necessary. It is possible, of course, that a difference found between versions of an interactive program do not imply an error of one of the versions. Nevertheless such a difference should be evaluated by the developer in accordance with accepted software development practice. In the field of interactive software particularly, testing and quality assurance routines have required a tester to work through programs repeatedly and to make a record, usually in written farm, of any errors found during the exercise of each iteration of the code. The record keeping aspects of this sort of work alone are cumbersome and are prone to error. Such errors in reporting the accuracy and usability of a program are obviously as unacceptable as deficient programs themselves. Accordingly, a system for testing interactive software is prone to error to the extent that humans are relied on to perform such testing. What is needed is a system for testing that minimizes human contribution. The article "Tools for automating software test package execution" by Craig D.Fuget and Barbara J. Scott in the Hewlett-Packard journal, vol 37, no 3, March 1986, pp24-28, discloses a software testing tool to enable automated regressive testing of a program using the interactive features of computers. The test engineer operates the tool by firstly creating an initial file which instructs the tool how to test the system. This initial file is run and all of the output from the system is stored in first log file. Then, when the program has to be tested again - for example after the release of a new software version - the initial file is run again and the system output stored in a second log file. The test engineer can use the saved output in the second log file for comparison with the previously saved output in the first log file to determine the differences between the two outputs and thus identify any errors that may have occurred. The system described in this publication is the closest prior art to the current invention. The test tool described in the article has the disadvantage in that a lot of memory has to be dedicated to storing the complete output response in the various log files. In addition, after the test has been carried out, it is necessary to run a further program in order to determine the differences between the log files which is time consuming and leads to a reduction in performance. An article in the IBM Technical Disclosure Bulletin, vol 28, no 9, Feb 1986, pp 3726-3727, entitled "Automated Testing of Application Programs" describes a set of Automated Program Test programs which automate the testing of applications software running on a personal computer. When running with a file maintenance tool and a full screen process, the test programs automate testing to the point in which keystrokes are pulled from a file, live code is executed, screen and printer output are saved and the actual results are compared to expected results. The system described in this article requires the construction, by the test engineer, of special batch files which automatically perform the tasks to be implemented. This is time consuming and during the development of the batch file, undetected errors may be introduced. The test system also requires the use of a comparison tool in which to compare the test runs with previously stored comparison runs. This has the disadvantages mentioned above. Another article in the IBM Technical Disclosure Bulletin, "Automated Software Test Facility" by H.N.Ozarker, vol 26, no 9, Feb 1984 describes an automated software test facility which allows the test engineer to capture the input data which is keyed in manually, capture the output screen image which is the response to the manually input data, automatically resubmit the captured input, compare the new output responses with the previously captured output and report any discrepancies. The test cases can also be created externally rather than by capturing the keyed-in input data. The system disclosed in this document has the major disadvantage in that it requires the resources of the system under test. This leads to problems in that some applications cannot be tested since there is conflict between these applications and those of the test system itself. In addition, the facility is not timing aware and is unable to intelligently query a 'wait' status of a system under test. Finally in this system, as in the other prior art systems mentioned, the responses have to be compared with a previously stored output with the disadvantages outlined above. In the terminology of claim 1 from the article IBM Technical Disclosure Bulletin, " Automated Software Test Facility " by H.N. Ozarker, vol. 26, no. 9, February 1984 a method for testing host resident interactive software, the steps comprising: a) generating a list of commands suitable for subsequent execution in conjunction with interactive software; b) playing back said commands using a first version of said software to generate and capture respective screen images for use as a test case; c) executing said test case on a second version of said interactive software; d) detecting differences between the captured screen images of said interactive software; and e) presenting said differences is known. The article "Regression Tester for CPS Programs" by F.C.Bequaert and M.G.Neff in the IBM Technical Disclosure Bulletin, vol 14, no 5, Oct 1971, pp 1417-1418, discloses a method for testing a programming system through its various modifications. The method used involves creating a set of statements for testing purposes and storing these in a test file. A special test program applies these statements to the system prior to its modification and the output is used to create a first master file. After modification, the same set of statements are applied and the new output stored in a second master file. The contents of the first and second master files can be compared in order to generate an indication of problems that have arisen. The disadvantages associated with this method (creation of test program, comparison of output results) have been discussed above. The object of this invention is therefore to provide a system to test different versions of interactive software automatically which overcomes these problems. In accordance with the present invention there is provided a method for testing interactive software. The interactive software is first executed while an interactive test case is captured. The test case is then executed on another version of the interactive software. The differences between the versions of the interactive software are detected and subsequently presented. Another function of the method of the present invention is to allow to record system response times and to detect and present differences in the response times of two versions of the interactive software. In one embodiment of the invention, the software to be tested is resident on the host and the test cases are caputured on a personal computer. The invention further allows a complete document of perceived errors in the host resident interactive software. Error reports can also be produced by users of the interactive software at remote locations. A complete understanding of the present invention may be obtained by reference to the accompanying drawings, when taken in conjunction with the detailed description thereof and in which: FIGURE 1 is a block diagram illustrating the elements in accordance with the SESSION program of the present invention and the data flow therebetween including optional elements; FIGURES 2a - 2p represent images displayed on a console in the course of executing a running example; FIGURE 3 is a block diagram of configurations of the editor with optional elements; FIGURES 4a - 4p represent instructional text associated with FIGURES 2a - 2p, respectively; FIGURE 5 is a block diagram of the educational driver and modes that can be operated therewith; FIGURES 6a - 6d represent error messages associated with an educational driver; FIGURE 7 is a block diagram of configurations for retesting of the present invention; and FIGURE 8 is a block diagram of the convert function in accordance with the present invention. The present system, intended for use in a computer environment, comprises three basic modes of operation: Education, Testing and Retest. Each of these basic modes of operation comprises sub-modes as hereinbelow described. The heart of the system is a SESSION program, the use of which results in a session or time period devoted to performing a specified task in accordance with one of the aforementioned modes of operation. This distinction between the SESSION program and a session (time period) is made herein by the printing convention of capitalizing the former. Referring now to FIGURE 1, there are shown the elements of the system in accordance with the present invention including data flow between elements. A console or so-called smart computer terminal 10, such as a personal computer available from IBM Corporation as Model PC/XT with a data communications adapter card, is adapted to execute a computer program loaded therein. The console 10 includes a display, preferably a high resolution, color cathode ray tube, for displaying alphanumeric characters and graphics. In the preferred embodiment, two display screens are used and arc differentiated by the fact that one is capable of displaying information in color while the other is capable of displaying information monochromatically. The display is often herein referred to as a monitor or a screen and the information displayed on it as a screen image. A computer program called SESSION 12 resides in the console 10. The SESSION program has many functions, all capable of being used both independently and in conjunction with one another. The console 10 can communicate with (i.e., transfer data to and receive data from) a host computer 14. The host 14 is typically a mainframe computer, such as an IBM Model 3081 processor. Communication among the host 14, the console 10 and various files described hereinbelow occurs by means of the SESSION software 12. A mechanism for allowing such communication between the host computer 14 and the console 10 resides therein. One such a mechanism, commonly referred to as an emulator, is available from IBM Corporation as the PC/VM BOND System. Connected to the SESSION program 12 are user selectable input files, shown generally as reference numeral 15. For example, an images file 16 contains screen images for use in the system as hereinafter described. Another file 18 stores commands and yet another file 20 stores timing or performance data. These three input files 15 can be used simultaneously. It should be understood that, although for the sake of simplicity and clarity of description the images file 16, commands file 18 and performance file 20 are shown in FIGURE 1 as single files, a plurality of such files can be used with the system of the present invention as conditions warrant. The embodiment described is not intended to limit the scope of the present invention. Any combination of files can be configured depending upon requirements. A second set of files, called output files and shown generally as reference numeral 21, is provided for receiving data generated by the SESSION program 12. A differences file 22 stores information obtained when previously stored data is compared to an interactive set of recently generated data. This information is most useful when the operator or the user performs a playback function in the retesting mode, hereinbelow described, but can also be used in the education mode to update screens. An output performance data file 24 contains a record of the performance or efficiency of both the system and the human user. The performance data file 24 contains timing information that can be accessed at a later time and subsequently analyzed. An output images file 26 is also accessible by the SESSION program 12 and contains data representative of the screen images that are displayed on the console 10. An output commands file 28 connected to the SESSION program 12 stores commands that are issued by the operator in the course of a session. The SESSION Program The SESSION program 12 can capture both commands and entire screen images. For purposes of understanding, it is helpful to analogize some of the major functions of the present invention to certain functions of an audio or video tape recorder and to use terminology associated with conventional recording functions, such as "record" and "playback." From the point at which the capturing or recording (i.e., mass storage of data at the PC) occurs, one of a number of programs including SESSION itself can be run. These programs are EDUCATOR, EDITOR, CONVERT and REVIEW. The human user, not shown in FIGURE 1, logs onto a system program that resides in the host 14 via the console 10. The user then accesses, by toggling, the console 10 and begins to execute the SESSION program 12 which has been previously loaded in the console 10. The SESSION program 12 reconnects the user to the host 14 and can be invoked from the PC console 10 via a conventional keyboard, not shown, or via other suitable means. The word SESSION and appropriate parameters are entered. The syntax for the command SESSION is as follows: SESSION 〈filename〉 [.#*s*p*d*n*a vm s# p# d# c# step saveon/saveoff 0/1 playback mask=n] where the aforementioned parameters, shown in brackets [] to indicate that they are optional, represent the following functions: .# file level to be used *s save a screen images file *p save a performance file *d save a differences file *n overwrite similar file *a append to existing file VM include VM system checking s# use .s extension p# use .p extension d# use .d extension c# use .c extension step playback each user command, pausing between them saveon/saveoff enter (or do not enter) record mode from first screen 0/1 display system screen on separate monochrome or color monitor playback enter SESSION in playback mode mask=n user specified ignore character (n) used when building differences file To aid in generating commands to the system, it is most efficient to define certain function keys, not shown, on the keyboard in order to execute particular commands. In the SESSION program 12, these function keys are defined by default as hereinbelow described. It should be understood, however, that any definitions for control keys can be generated by a user in accordance with common PC profiles practice. The following definitions of function keys are default system definitions and have been found to be most useful for general applications. The screen that is displayed when help menu is invoked, by typing the keys Ctrl-F1 from within the SESSION program, appears as follows: The SESSION program 12 can be run periodically (e.g., daily) by specifying a general filename at program invocation. This filename can be the current date with the save screens option specified in the event that it becomes necessary to save important information about a session. To save specific information, the Ctrl-M (Make Macro File) option is used and a filename is specified, relating to that information. This enables the user to playback (Ctrl-P) macro files immediately after they are created. If the filename under which the session is recording is also the general SESSION filename specified at invocation, the file cannot be played back until the SESSION filename is changed, which requires ending SESSION with Ctrl-E and restarting it with a different filename. This is due to the fact that the SESSION file created at inovacation is a file opened for output and cannot be used as both input and output. Therefore, it is advisable to use a generic SESSION filename, such as the current date (e.g., AUG27) for routine operation on a day to day basis. For purposes of understanding, it is helpful to carry a running example forward through this description. The following example is herein presented for explanatory purposes only and is not intended to limit the scope of the invention as defined by the appended claims. The purpose of the following example is to instruct a student on the use of commands in the ISIL language. The use of a system editing program such as XEDIT, as described in "IBM Virtual Machine/System Product: System Product Editor Command and Macro Reference" (Endicott, NY, Second Edition 1982), is required for this example. The user enters the PC command: SESSION ISIL*S Once the user has determined the point at which he would like to begin recording, he enters CTRL-R from the console 10. The system is then in a recording mode. It will capture the keystrokes and because *S was specified in the original SESSION command screen images entered henceforth. After CTRL-R is entered, the initial screen shown in FIGURE 2a is recorded on a newly named file, ISIL. To create a VM data set with a filename of ISILDEMO SCRIPT, the user enters the command: XEDIT ISILDEMO SCRIPT A1. This statement allows the user to execute the XEDIT system editing program, oblivious to the session interaction that is occurring. The recording session is therefore performed transparently to the user as he merely executes an XEDIT routine and operates in an XEDIT environment. The resulting screen recorded is shown in FIGURE 2b. In this running example, the author creates an education package to teach a student how to use subheadings or headers which are identified by the characters h1-h6. These and similar characters are known as tags. From time to time in this session, as shown in FIGURES 2a-2p, the author presses a console attention key in order to freeze and capture a given screen. He can then continue his session. This repeated use of attention keys is not additional work for an author using SESSION, since in the course of working on a host system attention keys are normally used repeatedly to get a system response. The ENTER key is an example of an attention key. Attention keys are normally used to update or refresh the screen. Other examples of attention keys are: CLEAR, PA1, PA2 and function keys F1-F12. The author next invokes the XEDIT input mode by entering the command INPUT. The resulting screen recorded is shown in FIGURE 2c. The next statement entered by the author is: :p.Paragraph [CR] used like :p.This where [CR] represents a carriage return key. The characters :p. designate the beginning of a new paragraph. All text following these characters are accepted as part of the paragraph. The resulting screen recorded is shown in FIGURE 2d. The next key pressed by the author is merely ENTER. This allows the author to save the previous screen image again for modifying at a later time. Thus, there now exist two copies of the screen image shown in FIGURE 2d. By referring to the screen shown in FIGURE 2e, a student is later able to see the effect of the ISIL tags on the text. The system screen now appears as shown in FIGURE 2f. The author then types and enters: :h1.Head level one [CR] :h2.Head level two The characters :h1. and :h2. are used to designate headings or subheadings in text. The number designating the header level can be from 1 through 6. The resulting screen recorded is shown in FIGURE 2g. The author then types and enters: :h3.Head level three [CR] :h4.Head level four The resulting screen recorded is shown in FIGURE 2h. The author then types and enters: :h5.Head level five [CR] :h6.Head level six The resulting screen recorded is shown in FIGURE 2i. The author again presses the ENTER key to save a duplicate screen image of FIGURE 2i so that at a later time he can alter the image to show the effect of the ISIL tags on text to a student, as shown in FIGURE 2j. The system screen now appears as shown in FIGURE 2k. To generate lists, the author enters the following text: :sl. [CR] :li.item1 [CR] :li.item2 [CR] :esl. The characters :sl. designate the beginning of a simple list. Characters :li. identify an item or member of a list. Characters :esl. designate the end of a simple list. The resulting screen recorded is shown in FIGURE 2l. To see the effect of these ISIL tags on the text, the author again presses the ENTER key, resulting in a duplicate screen image to be altered later to yield the screen shown in FIGURE 2m. The list (item1 and item2) appears below the level six subheading, as that level is the last one referenced before the list begins. The system screen now appears as shown in FIGURE 2n. The author then types and enters: :ul. [CR] :li.item1 [CR] :p.stuff for 1 [CR] :li.item2 [CR] :eul. The characters :ul. designate the beginning of an unordered list and :eul. designate the end of an unordered list. The resulting screen recorded is shown in FIGURE 2o. The author then presses ENTER, resulting in a termination of the XEDIT INPUT mode, as shown in FIGURE 2p. When the user is finished recording, he enters CTRL-R to end the recording session. He is, however, still executing the XEDIT system program and can therefore exit normally therefrom, if desired. The user is still also executing the SESSION program even though the recording mode is not being implemented. In order to end the SESSION program, the user types CTRL-E. While SESSION was running, two files were created: one for the screen images 26 (FIGURE 1) and the other for commands 28. Editing Save Screen Images At this point the author may wish to modify certain screen images previously recorded and may wish to add help text to the automatically generated rudimentary instructional text, thereby creating a help file. In order to do this, the editor is invoked with the following syntax: EDITOR 〈filename〉 [s# h# c# 0/1] The parameters abbreviated above have the same meanings as those described with reference to the SESSION command hereinabove described. The author now pursues the running example by entering the command: EDITOR ISIL In the editor function, certain user definable keys are assigned by default as shown below. It should be understood, however, that the user may define keys and key combinations in many other ways as desired and in accordance with conventional personal computer practice. Following is a list of keystrokes that are used in the EDITOR program. These keys are all used in conjunction with either the Ctrl (control) key or the Alt (alternate) key. All definitions are in the form: Ctrl-〈key〉 or Alt-〈key〉 denoting the need to press Ctrl and some other key or Alt and some other key at the same time. These keys are also defined within the help panel of EDITOR (Ctrl-F1). The EDITOR help screen, invoked by entering F1, is: Editor Help -LINE CONTROLS- -MARKING- Alt-F4 Erase EOL Alt-C: Copy Mark Alt- J Join Alt-L: Line Mark Ctrl-CRLF Split Alt-M: Move Mark Ctrl-Backspace Delete Line Alt-U: Unmark -SCREEN CONTROLS- -SPECIAL COMMANDS- F1 Help Ctrl-B: Background Color Select F3 Exit Without Saving Ctrl-C: Command Entry F7/PgUp Show Previous Screen Ctrl-D: Directory Listing F8/PgDn Show Next Screen Ctrl-E: End Editor F9 Swap Screens Ctrl-G: Goto a Screen ESC Save Screen and Continue Ctrl-N: Note Display on Screen Press any key to continue Editor Functions EDITOR is a screen oriented editing program for use with SESSION created files. EDITOR can be used on the screen file (.S#), help file (.H#) and even the command file (.C#) to modify and/or create new information. EDITOR places the system screen on the color monitor and the help screen on the monochrome monitor. The editable area defaults to the help screen. On a single screen system, the help screen is displayed; the system screen is accessed by toggling. EDITOR has many conventional editing features. Areas can be marked, moved and copied and lines can be inserted or deleted. These functions can be performed not only within individual help or system screens, but also between screens. EDITOR also allows color and attribute information to be defined. Colors both background and foreground may be altered and input areas may be defined as well. Referring now also to FIGURE 3, there is shown an editor 38 connected to the terminal 34. The files that can be input to the editor 38 are the previously created images file 26, the commands file 28 and the instruction or help file 30. The editor 38 can generate new images files, shown as reference numeral 26a, commands files 28a and instructions files 30a. The editor 38 can generate any such files 26a, 28a, or 30a either from existing files 26, 28 and 30, respectively, or without reference thereto. EDITOR can be used regardless of whether screen and command files exist. Although most useful when used in conjunction with SESSION-captured files, it can be used independently from SESSION. The files created or modified with EDITOR can be input to SESSION again or to EDUCATOR. EDITOR can be used to document errors. If a captured problem is too big to describe in notes on every screen, EDITOR may be used to create full screen text for the applicable system screens. EDITOR can also be used to modify test cases (command files), although CONVERT is designed for this purpose, as hereinbelow described. Although screens and help may be converted for use within any editor, the use of the EDITOR program allows these screens to be created and viewed in the way that they are to be presented. EDITOR can modify both help and system screen files, along with the command file. It is the easiest way to add help to a SESSION-captured education package. Although not specific for EDITOR, emulation tools can be explained through its use. By using macro files to create screen files, entire methods of operation can be documented and can form the basis of education. Complicated tasks that occur too quickly for education purposes in the macro can be captured (*S while playing back) in SESSION, descriptive text can be added (EDITOR) and the macro can be run at user pace (USER mode in EDUCATOR). The author now invokes the GOTO mode by pressing CTRL-G. The first screen image that has been recorded in the running example and is to be modified is on page 5 of the images file (FIGURE 2e). By typing CTRL-G 5, the author accesses a duplicate image of FIGURE 2d. He can then modify that screen using normal editing functions to arrive at an image shown as FIGURE 2e. The user now saves this modified version of FIGURE 2d by pressing the ESC key. Referring now also to FIGURES 4a-4p, there is shown a help screen file containing text that is associated with and corresponds to the images shown in FIGURES 2a-2p, respectively. FIGURES 4a-4n represent informational text that was entered during the editing session. FIGURES 4o-4p represent the rudimentary instructional text that is automatically generated by the EDITOR and EDUCATOR programs. After saving the modified version of the screen image, the system increments to the next screen image. The author may now wish to modify the image that was originally saved as shown on FIGURE 2i. To do this, he presses CTRL-G (GOTO) 10. The author can modify the screen of FIGURE 2i appropriately. By pressing the ESC key, the modified image is saved as shown in FIGURE 2j. In a similar manner, the duplicate of FIGURE 2l which appears on page 13 can be modified, resulting in the screen image shown as FIGURE 2m. Now the educational package is complete. The package can be loaded onto a floppy disk or transmitted, using network capabilities, to any location where the education is to he used. Once received, the educational package can be modified using the EDITOR program to account for site-specific variations. Education Mode In the education mode, the system is an automatic authoring tool. The author of the education is the operator who is using the host while executing the SESSION program. Any recorded screens and commands are stored in a way so as to be useful in an education context. By entering the education mode once the SESSION program terminates execution, the captured host session is simulated at PC level in instructional/tutorial format. Referring now also to FIGURE 5, there is shown the educational driver system. The images file 26 and commands file 28 have hereinabove been described with regard to FIGURE 1. In the running example of the session used to teach ISIL commands, the screen or images file 26 eventually contains a copy of all of the screen images generated during the host session while in the recording mode. These screen images are stored sequentially in a single images file 26. Similarly, the commands file 28 is also generated during the running example session. An instruction or help file 30 is also optionally provided in the educational driver system. The heart of the educational driver system is an educational driver 32 having a conventional multi-position mode switch 33 residing therein. The computer terminal 34, of which the driver 32 forms a part, is a standard console, not shown, which includes keyboard or other input means for a user to communicate with the program driver 32. Connected to the driver 32 by means of the mode switch 33 are modes, shown generally as reference numeral 36, each of which can be uniquely accessed by appropriate setting of the mode switch 33. In the preferred embodiment, eight modes can be used with the system. Modes 36a-36c are used in tutorial applications; modes 36d-36f are used in reference applications; and modes 36g-36h are utility/documentation modes. A performance data file 24, similar to that previously created by the SESSION program 12 (FIGURE 1), is also connected to the driver 32 for receiving timing data as required. Timing data represents the time interval between an event and a human response thereto via keyboard. The greater this time interval, of course, the less efficient is the human operator. The educational driver 32 comprises an EDUCATOR program which links the commands file 28, images file 26, and help file 30, if one exists, and presents them in a tutorial fashion. The EDUCATOR program has operating modes to support tutorials and training, online help, presentations, displays and error documentation. The EDUCATOR program is an interactive educational tool that authors an educational package for an author or instructor. By using the SESSION program 12 (FIGURE 1) to capture the host system 14, the EDUCATOR program can simulate that host system 14 and even supply rudimentary instructional text with no authoring needed. To create a complete education package, the EDITOR program, as hereinabove described, should create screen by screen help text. In the aforementioned running example, such screen by screen help text is generated during the EDITOR session for a portion of the system screens. The remaining system screens have rudimentary instructional text generated by the educational driver 32. Following is the syntax to invoke the EDUCATOR program. EDUCATOR 〈filename〉 [.# s# c# h# mode 0/1] where the aforementioned parameters, shown in brackets to indicate that they are optional, represent the following functions: .# level of file to use s# use screen level file c# use command level file h# use help level file mode starting mode; one of USER,STEP,AUTO,CMND,LIST,GOTO 0/1 force output display onto mono/color If .# is not specified in the EDUCATOR command, the system defaults to the highest level for each unspecified file. The parameter level (e.g., .4) sets the default level of files being used to the level specified (e.g., fourth level: s4, c4, h4). When not used, the level defaults to the highest existing level for that type of file command (.C), screen (.S) or help (.H). The specified level may be a number between 1 and 99. Separate parameters must be separated from the filename and each other by at least one space. Example: EDUCATOR ISIL STEP 1 The EDUCATOR command example shown above allows a user to invoke the EDUCATOR program with respect to the running example. COLOR ONLY (i.e., output device 1) directs the output of the EDUCATOR program to a color screen when available (e.g., on a two-screen PC). If a two-screen system is being used, it is sometimes useful to place the system screen on one of the displays. MONOCHROME ONLY (i.e., output device 0) directs the output of the EDUCATOR program to a monochrome screen. COMMAND FILE (i.e., C#) is a variation of the level parameter that allows specification of a file level for the command file only. Instead of using the latest version command file (the file with the highest value extension), the file with the specified value is used. If the specified file does not exist, the highest existing level command file is used. HELP FILE (i.e., H#) is also a variation of the level parameter. It allows specification of a file level for the help file only. SCREENS FILE (i.e., S#) is another variation of the level parameter. It allows specification of a file level for the screens file only. If the AUTO mode is specified on a two-screen system the system pauses for seven seconds, types in the command, pauses for three seconds and cycles on to the next screen. On a single screen, AUTO mode pauses for two seconds, displays the system screen with the command typed in for three seconds and cycles on to the next screen. When the end of the file is reached, the cycle begins again at the first screen. If the command mode (i.e., CMND) is specified, the system watts for the user to type in a command and then searches the list of commands available with LIST mode for an exact match. If no match is found, any command containing the entered string is marked. If only one command is marked, that screen is accessed. If more than one command is marked, a window of the marked commands is displayed as user options. If no commands are marked, a COMMAND NOT FOUND message is displayed. If the goto mode (i.e., GOTO) is specified, the system displays a window for the user to enter a screen number. The EDUCATOR program branches to the specified screen number. If the number is larger than the size of the education package, the last screen is accessed. The corresponding help screens are linked to the appropriate GOTO-specified screens. If the list mode (i.e., LIST) is specified, the system displays a window of all the available commands within the education package. Entry type keys are not displayed as commands. The command is displayed with its associated screen number. The list can be scrolled within the window and the commands can be selected. The selected commands are displayed in order of occurrence within the education package. Only one command may be selected per screen. When the screen is displayed, all the commands thereon are also displayed. Thus, selection of only the first command per screen is allowed; the other commands are suppressed. If the step mode (i.e., STEP) is specified, the system waits for any data key to be pressed. Once pressed, the entire command is typed onto the screen. STEP mode then waits for another data key to be pressed. Once this second data key is pressed, the next screen is accessed. If the user mode (i.e., USER) or if no mode is specified, the system waits for the user to input a correct command and press the correct command entry key. Three chances are given to enter a correct command. Referring now also to FIGURES 6a-6d, on the first error, a message is displayed as shown in FIGURE 6a. On the second error, corrections to incorrect characters are made by the system; the user must finish making the indicated corrections shown in FIGURE 6b (i.e., erase extraneous characters). On the third error, the proper entry is displayed by the system as shown in FIGURE 6c and the next screen is accessed. If, after the user has made all necessary corrections to the command, he enters an incorrect attention key, an additional error message is displayed as shown, for example, in FIGURE 6d. Available keystrokes in the EDUCATOR program are described below. It should be understood that the definition and function of these keys, being arbitrary, can vary in accordance with the designer's requirements or preferences. In the preferred embodiment, a keyboard adapted for use with an IBM personal computer (PC) is hereinbelow described. These keys are all used in conjunction with the control (Ctrl) or alternate (Alt) key. All definitions are in the form: Ctrl- 〈key〉 or Alt- 〈key〉 denoting the need for a user to press Ctrl and some other key or Alt and some other key simultaneously. The EDUCATOR help screen, invoked by entering Ctrl-F1, appears as follows: To run the education software package through the educational driver 32, the user enters the command EDUCATOR and a filename. The filename must be the same name as the previously created education package. In the running example being used for purposes of disclosure herein, the filename is ISIL. In the preferred embodiment, two screens are used for practicing this invention. The first screen displays screen images sequentially and the second screen displays commands that are invoked in parallel with the screen images. In an alternate embodiment, however, the 0/1 output device parameter can be used in order to display both the screens and the commands on the same terminal or console. There are two basic modes in the educator driver: a tutorial and training mode; and an online help or reference mode. On a two screen system, the system screen comes up on the color monitor and the help file on the monochrome monitor. The instructional text or help screen displays information that has been edited in connection with the system screen. Also displayed are the commands needed to be entered on the system screen. In the running example, the first command is XEDIT ISIL DEMO SCRIPT A1. This is the command that the user entered. The typed characters appear on the system screen as they would on the actual host system. Once the user types the command that is required for that screen and presses the correct entry key (ENTER, PF keys or CLEAR), the following system screen is displayed and the instructional text for that screen is also displayed. The system has been captured in the ISIL education package. As hereinabove described, text FIGURES 4a-4p are associated, respectively, to screen text FIGURES 2a-2p. The user continues operating in this function, typing in the instructions required. The keystrokes needed to enter the instructions need not be specific to the command, but the command itself must be correct. Also as hereinabove described, levels are provided for the user in case an incorrect command is entered on the screen. FIGURES 6a-6d represent the three error levels provided. On the first error level a message (FIGURE 6a) indicates that an error occurred upon input; the user is to retry. When a second error occurs on the same command, any missing or incorrect characters are corrected by the system and highlighted in one color (Figure 6b). Any characters not needed for the response are highlighted in another color. The user is asked to erase those extraneous characters. On the third incorrect attempt, the correct response is typed onto the screen by the system (FIGURE 6c) and a short message is displayed on the bottom of the screen indicating that the correct answer is being displayed. If an incorrect entry key is pressed (e.g., if ENTER is required and PF5 is pressed), an appropriate message appears at the bottom of the screen (FIGURE 6d), instructing the user to use ENTER. The user continues working through the software package to the end of the file, typing the commands requested by the instructional and help text and progressing through the system screens in the simulated system. In the aforementioned running example, the help/instructional text that was generated using the EDITOR program ends on the screens shown in FIGURE 4n. Starting with that screen (FIGURE 4n), this screen image is generated by the EDUCATOR program and is called rudimentary instructional text. The online help-mode functions best using the list mode function. This function displays a window on the system screen. In the window is displayed a list of all commands available within this education package. Both the command and the page number on which the command appears are displayed. This list is ally scrollable and selectable. The user may scan the list, type an S (for "select") in front of any number of items he wishes to see and press the ENTER key. Upon pressing the ENTER key, the system screen and the help/instructional screen relate to the first selected item. The user automatically enters the STEP mode at which time he may press any key and see the command typed onto the system screen, then press any following key and watch the resulting screen. The corresponding help/instructional text screen is displayed concurrently. If more than one item has been selected from the list, upon pressing any key again the next selected screen is moved to the STEP mode. This continues until all items selected from the list have been displayed at which time the user remains in STEP mode. At any time during this process the user may re-enter list mode to select other screens, de-select previously selected screens or view screens that have already been viewed. Such previously displayed screens are annotated with an asterisk. This sort of online help is called task oriented. It is used to show the user the type of screen on which the command is to be used, the syntax of the command and the probable results of entering such a command. Online Help Modes of Educational Driver Most forms of online help taught in the prior art are menu driven, complex and vague. The user does not acquire a thorough understanding regarding the use of the item for which help was sought. Syntax is often described or charted, but actual use is rarely shown or explained. The EDUCATOR program, however, provides online help in a task oriented manner. This is achieved by demonstrating both the syntax and the contextual use of the specified item. Education packages designed by the present system are more effective if the online help capability is utilized. The education package can thus become more than education; it remains useful even if the user is an expert on the system. The package can always be loaded at the PC level and accessed, by toggling, for reference on a host system problem. Item specific help packages can be designed, for example, to explain all the options of a menu driven system, or how all the tags of a word processor operate. Anything that can be itemized in a list may be the subject of task oriented online help. Within EDUCATOR the list and command modes are most useful for online help. The list mode displays a window of all available commands in the package. This is a scrollable, selectable list that allows the user to make choices as to the areas for which he wants help. The command mode is similar to the list mode, except that the list is not shown. Instead, the user types in a string of characters about which he wants information and the list is searched. The search performed in command mode first attempts to locate a perfect match between the user entry and a command on the list, and then attempts to locate a substring match. The effect is the same as in the list mode: the user is shown help for that which was requested. Commands in the list are separated by enter type keys. That is, each selectable command is preceded by and followed by an entry key. Although many items may appear on one host system screen, only one of the items in the list mode is selectable. This is because selection of that one item from the screen causes display of all the other items also. Alternatives exist for creating education packages. These include: a) using EDITOR to create screen and commands instead of SESSION to capture them, as hereinabove described, b) using CONVERT, as hereinbelow described, to create a command file from a text file and using SESSION to playback those commands, automatically capturing the associated sequence of images, and c) using any editor to create text files of images and commands using a set of GML-like tags and using CONVERT to create screen and command files for use by the EDUCATOR program. Test Modes Testing relates to items that are expected to yield different data with each run, even when repeated or similar sets of commands are used. Two categories of such tests are human factors testing (which does not form part of this application) and performance testing. Human factors testing can, in turn, be categorized as either basic or extended and is treated in related European Patent Application EP 87 101 591.3 (EP-A-0 236 746). Performance Testing Judging system response time at the user's terminal on a system is often a difficult task. To perform the test properly, a person with a stopwatch conventionally observes a terminal operator and times each system response relative to its associated command. This is time consuming and inaccurate. It is also difficult to gather timing information relating to the user. By using SESSION with the *P (performance chart) option, this information can be gathered and saved without the need of a timer or of extra keystrokes to start and stop a clock. The performance option starts timing from the first system attention key (ENTER, CLEAR, any PF or PA). A timing is taken at the press of one of these keys and another timing is taken when the system returns the messages, Available and Input Not Inhibited. At this point, the user is able to enter data. True end user response times can be determined. As the user enters data the clock continues to run until another system attention key is entered, at which point the timing starts again; a user time is then saved to the .P file. It is preferred, however, to have the PC submit the commands automatically to the system and to gather system response time statistics without user intervention. The means by which this is done is hereinbelow described with respect to retesting. The .P file holds all timing (performance) information. A summary at the end of the file includes the number of commands, largest system lag time and user entry time, smallest system lag time and user time, total system response time and user input time and average system response time and end user input time. Individual commands are listed in rows and timing information in columns. The performance chart generated by the system performance test is identical to that generated by the human factors test. Moreover, the events that trigger timings that appear on the performance test performance chart are identical to the aforementioned events with respect to human factors testing. Retesting Modes Retesting involves testing of products that have been tested before. If the product has been tested once, some memory of that test is expected to exist. That memory can be the PC's memory. In this way the PC can rerun the test that had been previously performed and can compare the results it gets to those previously received. The PC can also be used to document problems that are found, including where the problem occurred, and can display relevant information repeatedly. Whether the PC is used in a threshold test of a new release against an old one, in an inline test of a product once it has exceeded the performance threshold, or in reporting field errors of the product once it is released and must be supported, the system of the present invention can conduct these tests more quickly and efficiently than can a human tester. Threshold (Regression) Testing From release to release, software products change and are upgraded. During these upgrades, however, original functions are still supported and should be tested also. This is often called regression testing and occurs after new functions are tested. By using SESSION, a regression test can become a threshold test of minimum acceptable function that must exist satisfactorily before the product receives human testing. The minimal set of functions are determined by previously run tests of earlier releases. If the SESSION program were used during these initial tests, an automatic test case already exists for the threshold test. The playback file option of SESSION and the *D parameter are relevant for retesting. The playback option allows SESSION to drive the host system as if a human operator were at the PC keyboard. When the PC drives the system, however, there are no operator mistakes or delay; the PC executes as quickly as the host allows. The file used to playback to the host is the previously recorded test of the prior release. This represents the test case. By using the *D (differences file) parameter, SESSION not only plays back the commands, but compares the screens on file from the previous run to those that are displayed in playback. Any differences found are saved into the differences file for human review at any later time. Only the differences are saved. If no differences exist for a number of screens, SESSION merely continues to issue commands to the host and to identify differences. Using the running example, a threshold test can be performed by invoking SESSION as follows: SESSION ISIL*D PLAYBACK SESSION automatically retrieves the commands previously recorded for the example and detects any differences. The screen file used for comparison is the sequence images file shown in FIGURES 2a-2p before editing. Referring now also to FIGURE 7, there is shown a system configuration used in retesting. Once the threshold test is complete, the differences file 22 can be scanned with a REVIEW program 50. The images file 26 and commands file 28 are also input to the REVIEW program 50. This program 50 shows the original screen from the prior run, then overlays it with the differences found during the current run. These differences are highlighted for easy recognition even in the case of a single character. Extra information is given at the bottom of the REVIEW screen. Such information includes the command used to arrive at that screen, the screen number in the file of original screens and the total number of screens that had differences. Review Mode The REVIEW program allows the user to see the data that was handled by the console after it played back a file with the *D (differences file) option in SESSION. The original user session is displayed and the differences in the session found by the PC are overlayed on the original. The user can toggle between the original session and the PC run session, seeing only those screens that were different in the two runs. REVIEW also allows the user to see only differences on PROTECTED (non-input) or UNPROTECTED (input) fields. This way certain characteristics of different systems can be masked and the possible differences ignored. EDITOR also allows the creation of mask characters or the original user-captured screens. These mask characters are ignored by SESSION go that any differences occurring in those physical screen positions are subsequently ignored during the playback. The REVIEW program 50 resides in the terminal 34 and can be invoked thereby. The images file 26, the commands file 28 and the differences file 22, all created by the SESSION program 12 (FIGURE 1) can be input to the REVIEW program 50 separately or in any combination for processing. REVIEW is dependent on SESSION being run in playback mode with the *D (save differences) option. The toggle in REVIEW from original screen to different screen occurs relatively slowly the first time; it is immediate all following times. Thus, on screens with major differences, the differences do not suddenly appear but are painted onto the screen. The REVIEW command has the following syntax: REVIEW 〈filename〉 [.level][asterisks] [separates] Level is similar to a file extension in DOS. It sets the default level of files being used to the level specified. When not used, the level defaults to the highest existing level for that type of file (.C, .S and .D). The specified level may be a number from 1 to 99. Asterisk parameters must follow the filename immediately with no separating spaces. Separate parameters must be separated from the filename and each other by at least one space. COLOR ONLY forces REVIEW to the color screen when using a two screen PC. Example: REVIEW testfile*1 if a two screen system is being used, it is sometimes useful to place the system screen on one display or the other. *1 forces the program REVIEW to use only the color screen. The monochrome display is left free. MONOCHROME ONLY forces REVIEW to the monochrome screen when on a two screen console system. Example: REVIEW testfile*0 In establishing a command file, a user-specified command file extension number is used. Example: REVIEW testfile c5 This parameter is a variation of the level parameter that allows specification of a file level for the command file only. A user specified differences file extension number is used to create a differences file. Example: REVIEW testfile h5 This parameter is also a variation of the level parameter that allows specification of a file level for the differences file only. The protected only function is invoked by the letter P. REVIEW displays only those differences found on protected fields. Example: REVIEW testfile p Any differences found on a protected field will be displayed. All others (unprotected fields) are not displayed as differences. SESSION can also be executed with this option while the differences (.D) file is being created, in which case the differences file contains only protected field differences. Otherwise, SESSION saves all differences and REVIEW must be invoked to purge them. The QUIET function turns off most of the pre- and post-program logos and sound. Example: REVIEW testfile q Any logos at program start and end are suppressed, along with the typomatic sounds of the logos. If q is specified from the filename menu of the program, only the program ending logo is suppressed, as the initial program logo has already been displayed. The unprotected-only function is invoked by the letter U. REVIEW displays only those differences found on unprotected fields. Example: REVIEW testfile u Any difference found on a unprotected field will be displayed. All others (protected fields) are not displayed as differences. SESSION can also be run with this option while the differences (.D) file is being created, in which case the differences file contains only unprotected field differences. Otherwise, SESSION saves all differences and REVIEW must be invoked to purge them. A user specified screens file extension number is used to select a screens file. Example: REVIEW testfile s5 This parameter is also a variation of the level parameter that allows specification of a file level for the screens file only. In the preferred embodiment, the following control (Ctrl) key combinations have been found to be most useful: KEYS FUNCTION DESCRIPTION CTRL-HOME BEGINNING OF FILE Moves user to beginning of differences in files. CTRL-E F3 END REVIEW Terminates F3 REVIEW program and returns to DOS. CTRL-END END OF FILE Moves user to end of all files. CTRL-PGDN CTRL-F8 NEXT SCREEN Moves user to next differences display. CTRL-PGUP CTRL-F7 PREVIOUS SCREEN Moves user to previous differences display. Once the test is reviewed, the human tester can make the decision as to whether the differences found were also errors. Automatic Testing Automatic testing deals with those tests that are performed after the threshold tests are complete. The developed code is in the hands of the human tester who is responsible for exercising the new function. So long as he is operating under SESSION and saving at least the commands, his job can be made much easier. SESSION allows the saving of commands and screens so that the human tester can easily replay entire series of steps. Once a tester finds an error and the error is corrected by the developer, the code must be retested to ensure the repair. This retest should be an exact duplicate of the steps that caused the original error. These series of commands are often difficult to remember and time consuming to repeat. It is also difficult for the human tester to know if any other changes have occurred on the path toward the original error. SESSION replays the exact series of keystrokes leading to the original error and when run as it was in threshold testing also notes differences that have developed up to that point in the test. In automatic testing, SESSION can be used to reduce the drudgery and repetition of the tester's activities. Convert Mode CONVERT is a translation program that changes files created by SESSION into human-readable form. CONVERT can also change human-readable files into SESSION-readable form. Referring now also to FIGURE 8 there is shown the convert function 40, to which is connected the images file 26, the commands file 28 and the instructions file 30, cumulatively referred to as saved session files and identified by reference numeral 42. Three text files 46 and a host format images output file 48 form human-readable files referred to generally as reference numeral 44. Human-readable files 46 can be edited with any PC editor. Using the command language, new commands can be inserted, old ones deleted, the file expanded, contracted or even used to create an entirely new file. CONVERT 40 must be executed once again to make the file usable by SESSION. A command file can be created in either of two ways. The first is by recording the command file using the SESSION program. The user issues a begin task definition command within SESSION (Ctrl-M). The interactive task is then performed normally When the task is completed an end task definition command (also Ctrl-M) is entered, which causes the originally specified task to be saved as a command file. The second way to create a command is simply to use an editor to create a list of commands as previously defined. This list is then processed by the CONVERT program which makes an executable command file. The files 42 converted back into SESSION format are syntax checked and logic checked. This is similar to compiling a Basic or Pascal program. In the present context, the compiling analogy relates to files that contain commands, both SESSION-readable and human-readable. Errors are flagged and, depending on their severity, the conversion continues or ends. The file is placed into SESSION format and given the highest existing extension number (i.e., .C number, .S number or .H number) plus one, so that no files are overwritten. One of the advantages of using CONVERT on command files is that the language it supports allows more than the emulator keys that SESSION can capture. This allows a command file to accomplish a more generalized task than the commend file was originally created to do. Since a type of compilation is done on the file, looping controls are supported as are screen searches, saves and variable parameters. Some of these language commands simulate keys that are defined to SESSION; others are defined to the language alone. Although SESSION cannot capture special language controls when recording, it can understand the controls when they are built into the command file. The compile that is performed when the human-readable file is made SESSION-readable is a type of corrective compile. Only when the problem is compiled past the point of a correction or the problem is too severe, does CONVERT abort the compile. But if an error is found that can be corrected during the compile, it is corrected. CONVERT inserts necessary commands, if possible, to satisfy requirements of SESSION if such commands were omitted. These added commands are noticeable when the SESSION-readable file is converted back to human-readable, having been originally converted from human-readable form. This operation is useful for debugging command language files because the commands that the compiler changes become evident. It is recommended that any such twice-converted files be inspected carefully and not converted a third time. In operation, the CONVERT program 40 can convert the commands file 28, the images file 26 or the instructions file 30 or any combination thereof into the text files 46. Moreover, the images file 26 can be converted by the CONVERT program 40 into the host format images file 48. To invoke the CONVERT program 40, the following syntax must be used: CONVERT 〈filename〉 [fromc¦toc][c#] [nonum] where the aforementioned parameters, shown in brackets [] to indicate that they are optional, represent the following functions: fromc¦toc direction of conversion c# level of file to convert nonum without cursor location CONVERT can be used to create a command file, to modify one, to generalize one or even to make one a repeating self contained host session. Error Reporting Error reporting is a process in which testers and users document problems for the code developer to consider and to eliminate, if possible. Conventional methods of documentation are often poor a representation of the system. This leads to long delays before corrections are effected, confusion as to what the problem is and the need for extra communication beyond the documented error in an attempt to determine the problem. Moreover, since users may not remember the exact sequence of steps that were used in discovering the errors, the error is often incorrectly documented and considered invalid by the developer. By using SESSION, an exact record is kept of the terminal session. This record includes not only commands, but entire screen displays seen by the user as well as a single line of text that the user can add contemporaneously to further describe his actions leading to the problem. This is accomplished by the NOTE TO SCREEN function hereinabove described. An entire page or screen of user specified text can be entered after the session is complete using the EDITOR program. With this documentation, the developer sees not only the commands that the user entered, but the time at which the user entered them, what he saw and what he was thinking at the time. Reconfigurable Automatic Tasking System SESSION, as an emulator overlay, can allow features to exist that the normal emulator alone cannot allow. Macros are similar to .BAT files at the PC level, or CLISTS or EXECS on the host system. By using SESSION and simply recording a series of commands, a macro can be created. This macro can be played back at any time, reducing repetitive or difficult keystrokes to a macro file name. In the preferred embodiment, the following commands form a set that includes all commands that can be captured by the keyboard as well as additional commands that can make the macro more flexible or reconfigurable, as hereinbelow discussed. Keyboard Functions [INSOF] [INSON] [PRTSC] [ENTER] [TR] [EEOI] [EEOF] [HOME] [B] [TAB] [BTAB] [U] [D] [CR] [R] [L] [END] [PF1] [PF2] [PF3] [PF4] [PF5] [PF6] [PF7] [PF8] [PF9] [PF10] [PF11] [PF12] [PA1] [PA2] [CLEAR] [DEL] [RESET] [BEEP] Variable Parameters [%0] [%1] [%2] [%3] [%4] [%5] [%6] [%7] [%8] [%9] Time Stamp [T] Find String Delimiters [F+] [F-] Do If Found [+F] Do If Not Found [-F] Wait Until CTRL-W [WAIT] Pause Until Any Key is Struck [PAUSE] Begin and End [+] [-] Command File Name Delimiters [C+] [C-] Stop and Keep Session Going By Repeating Enters [HOLD] [STOP] Labels for GOTOS [:0] [:1] [:2] [:3] [:4] [:5] [:6] [:7] [:8] [:9] GOTO Commands [G0] [G1] [G2] [G3] [G4] [G5] [G6] [G7] [G8] [G9] No Operation [NOP] Delay Specified Period of Time [DELAY] Special Checking For System In Use [VM] [MVS] Password Delimiters [L+] [L-] Enable/Disable Screen [BLNK+] [BLNK-] Specific Cursor Location [GOXY] [SNAP] [OLDXY] [(*] [*)] [TYPER] [TYPEL] [TYPEU] [TYPED] Reset GOTOS [R0] [R1] [R2] [R3] [R4] [R5] [R6] [R7] [R8] [R9] [READ] Local Variables [VAR0] [VAR1] [VAR2] [VAR3] [VAR4] [VAR5] [VAR6] [VAR7] [VAR8] [VAR9] Uppercase/Lowercase [CAPON] [CAPOF] Assign Values to Variables [SET0+] [SET1+] [SET2+] [SET3+] [SET4+] [SET5+] [SET6+] [SET7+] [SET8+] [SET9+] [SET-] Erase Lead and/or Trail of Local Variable [STRIP] Macros can also be written instead of recorded, or altered once recorded, by using CONVERT and the command language. The command language allows conditionals, loops, writes to disk, variable parameters and many other functions that could not be duplicated merely by recording. The command language therefore allows powerful macros to be built that can process indefinitely. Once created or modified, the editable form of the macro (a .CMD file) is then executed under the CONVERT program. This places the file in SESSION-readable form (.C# file). The file can be exercised under CONVERT any number of times until even the most complex macro is correct. The following macro file is an example of a simple macro into which additional commands have been inserted to allow the file to update a whole series of host files automatically. FIND, GOTO and looping commands allow the macro to be more flexible than a conventional macro, in that the macro can react appropriately to changing system conditions. This file is designed to use XEDIT (on VM) to update a series of files automatically. Emulation CONVERT can be used to generalize macro files, create long running and/or repetitive tasks, simplify daily operations and customize the way that the user interacts with the host system. A macro file may be captured with specific inputs, such as data set names, and later converted to variable parameters. Long running and repetitive tasks can be executed by entering a few keystrokes with a looping or branching macro. Finally, CONVERT can be used to make the host appear to accept parameters with a command or automatically save a data set when editing is complete. For example, a command file to edit a data set and have it caved when editing is complete may appear as follows: To use the host editor now, the keystrokes would be: Ctrl-P EDIT MY-DATASET MY-DATASET now occupies the [%0] position and the system is in the editor in WAIT state. When editing is complete, the user can press Ctrl-W to save the file, exiting the editor.

Claims: A method for testing interactive software, the steps comprising: a) generating a list of commands suitable for subsequent execution in conjunction with interactive software; b) playing back said commands using a first version of said software to generate and capture respective screen images and system response times for use as a test case; c) executing said test case on a second version of said interactive software; d) detecting and storing differences between the captured screen images and system response time of said interactive software; and e) presenting said differences. The method in accordance with claim 1 wherein said step of executing said test case on said second version of said interactive software is initiated without human intervention. The method in accordance with claim 1 or 2 wherein said step of generating a list of commands suitable for subsequent execution in conjunction with the interactive software comprises capturing an interactive test case generated during the execution of said first version of said software. The method in accordance with any of the above claims wherein said step of generating said command list comprises: i) creating a text file containing said list of commands; and ii) converting said text file to an executable command file. The method in accordance with any of the above claims, the steps further comprising: f) evaluating said differences to detect errors and to determine system performance; g) changing said software to eliminate said detected errors or to improve system performance; and h) re-executing said test case to compare said second version of said interactive software to said first version thereof. The method in accordance with any of the above claims comprising the step of documenting errors, which step comprises a) recording data representative of a user session comprising the list of commands, system response time and the screen images, the data including an error or poor system performance; b) transmitting said recorded data to an evaluator; and c) simulating said user session using said transmitted data to determine the nature of said error or poor system performance. The method in accordance with claim 6, the steps further comprising: d) effecting a correction in said software if an error or the reason for the poor system performance exists therein. The method in accordance with claim 7, the steps further comprising: e) communicating to said user correction of said error. The method in accordance with any of claims 6 to 8 wherein said recording step comprises: i) allowing a user to annotate said user session while said data representative of said user session is recorded to indicate said user's contemporaneous thoughts. The method in accordance with any of claims 6 to 9 wherein said recording step comprises: i) allowing said user to annotate said user session subsequent to recording thereof. The method in accordance with any of claims 6 to 10 wherein said simulating step comprises: i) detecting the presence of said user annotations; and ii) viewing said user annotations. The method in accordance with claim 11 wherein, when said user annotations are made while recording, said simulating step of claim 6 comprises: i) requesting a next annotation; ii) locating said next annotation; iii) advancing simulation to the point in said user session where said next annotation occurs; and iv) displaying said annotation in a simulation context. The method in accordance with any of claims 6 to 12 the steps further comprising: d) playing back a predetermined portion of said user session to recreate said error or the poor system performance. The method in accordance with claim 13 wherein said predetermined portion of said user session comprises commands entered by said user. The method in accordance with claim 7 the steps further comprising: e) testing said software corrections by using said user session as a test case. The method in accordance with claim 8 wherein said communicating step comprises: i) annotating said data representative of said user session to indicate user deviations from correct methodology.

Inventors: KERR RANDAL HUGH, MESNARD ROBERT MARSHALL, KERR, RANDAL HUGH, MESNARD, ROBERT MARSHALL
Applicants: IBM, INTERNATIONAL BUSINESS MACHINES CORPORATION
Application year: 1987
Main classification: G06F11
IPC codes: G06F9, G06F11