JPH04281536A - Program retest system for conversational tool - Google Patents

Abstract

PURPOSE:To obtain a program retest system of a conversational tool by which a workability and reliability at the time of the retest of a program can be sharply improved. CONSTITUTION:At the time of testing the program of the conversational tool which succesively executes a data input according to a guidance displayed on a screen, the data successively inputted according to the guidance at the time of the test are collected in order to prepare an input key log file 23, and a processed result of the input data is preserved in a text file 24. At the time of the retest, the test is executed by the data in the input key log file 23, and the content of a text file 34 being this processed resuslt is compared with the content of the text file 24 being the previous processed result in order to judge the quality of the program.

Description

[Detailed description of the invention]

[Object of the invention]

0002

[Industrial Application Field] The present invention provides a program in an interactive tool that can easily retest the program by reusing key input data and created files when testing the quality of the interactive program. Concerning the retest method.

0003

[Background Art] When a problem occurs in a program of an interactive tool, in order to find out the cause of the problem, it is necessary to start the program and check the quality of each item one by one. . In the case of this interactive tool, the program must be tested by performing sequential data entry according to on-screen guidance. and,
If some kind of failure occurs again, you will have to enter data again from the beginning according to the on-screen guidance and check whether the correct processing results are obtained.

0004

[Problems to be Solved by the Invention] According to the above-mentioned conventional method, key input to the program is required in the same way as in the first test when retesting, which is cumbersome for the operator and requires visual confirmation. There was a problem with the lack of accuracy.

The present invention has been made in view of the above-mentioned conventional problems, and its purpose is to provide a program retesting method in an interactive tool that can greatly improve workability and certainty when retesting a program. There is a particular thing.

[Configuration of the invention]

[0007]

[Means for Solving the Problems] In order to achieve the above object, the present invention provides a method for testing a program of an interactive tool that sequentially executes data input according to guidance displayed on a screen. A means for collecting sequentially input data to create an input key log file, a means for storing processing results for this input data, and a means for executing a test using data in the input key log file at the time of retesting. , and means for comparing this processing result with the previous processing result to determine whether the program is good or bad.

[0008]

[Operation] According to the above configuration, at the time of the first test,
It collects the input key input data, creates an input key log file, and saves the processing results. At the time of retesting, the data of this input key log file is automatically input and the processing results are compared with the previously saved processing results to judge whether the program is good or bad. Therefore, the operator's labor can be significantly reduced and key input errors can be prevented.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows the configuration of an embodiment to which the system of the present invention is applied.

In the figure, a startup program in a startup program storage section 1 launches a program to be tested. This startup program starts the test program processing section 2 to be tested during the first test, and also starts the retest processing section 3 during the retest.

The test program processing section 2 has a test data key input section 21, a screen processing section 22, and
It includes an input key log file 23 and a text file 24, and the text data in the text file 5 is modified based on input data from the conversation terminal 4 and stored in another text file 24.

The retest processing section 3 has a log data key input section 31, a screen processing section 32, an input key log file 33, a text file 34, and a comparison section 3.
5, the text data in the text file 5 is modified using the data in the input key log file 23 and stored in another text file 34, and the data in the text file 24 and the data in the text file 34 are Compare and judge whether the results are good or bad at the time of retesting.

Next, its operation will be explained.

[0014] When some kind of fault occurs in a certain program, first, the starting program of the starting program section 1 starts the program in which the fault has occurred and is the object of the test. At the time of the first test, test processing is executed by the test program processing section 2. The text data in the text file 5 is sequentially checked and corrected according to the data input from the conversational terminal 4, and the text data is created in the text file 24.
Filed under. The input data during this time is sequentially saved in the input key log file 23. Therefore, an input keylog file 23 and a text file 24 are obtained as products of the first test.

On the other hand, at the time of retesting, a text file 34 is created in the same manner using the data of the input key log file 23. Then, the comparison unit 35 compares the contents of the text file 24 obtained initially and the text file 34 obtained at the time of retesting, and determines whether they are good or bad.

As described above, according to this embodiment, the key input data and the processing results for the data at the time of testing are saved, and at the time of retesting, while the saved key input data is used, the final The program is determined to be normal if the contents of the text file 23 and the text file 33, which are the generated products, are the same. This embodiment is particularly effective when, when a certain item of a program is modified, testing whether or not this modification affects other items.

[0017] Furthermore, by comparing the data in the input key log file 23, which is the data input at the beginning, and the data in the input key log file 33, which is saved at the time of retesting, the input key data can be compared with each other. This allows for double checking.

[0018] Also, in this embodiment. In addition to being used only during testing, it can also be used for program maintenance during operation.

[0019]

[Effects of the Invention] As explained above, according to the present invention, the operator's labor when retesting a program is significantly reduced, data input errors can be prevented, and the reliability of testing can be improved. Can be done.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the configuration of an embodiment to which the system of the present invention is applied.

[Explanation of symbols]

1 Startup program storage section 2 Test program processing section 3 Retest processing section 4 Conversation terminal 5, 24, 34 Text file 21 Test data key input section 22, 32 Screen processing section 23, 33 Input key log file 31 Log data key input section 32 Screen processing section 35 Comparison section

Claims (1)

[Claims] [Claim 1] In testing a program of an interactive tool that sequentially executes data input according to guidance displayed on a screen, an input key log file is created by collecting data input sequentially according to the guidance during testing. means for storing processing results for the input data; and at the time of retesting, executing a test using the data in the input key log file and comparing the processing results with the stored processing results; A program retest method in an interactive tool, characterized by comprising: a means for determining whether a program is good or bad.