JPH0635754A - Retesting method and device therefor - Google Patents

Abstract

(57) [Summary] [Purpose] To provide a retesting method and an apparatus for facilitating extraction of test data to be retested and facilitating confirmation of test results. To do. [Structure] In a retest method for determining the test coverage of a program, a retest range at the time of module modification is extracted based on test data and related information of a test target module, and the extracted test data is re-executed. Then, a retesting method characterized by comparing and verifying a (previous) executed test result and the present test result for the test data, and an apparatus therefor.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a retesting method and a device therefor, that is, a so-called, for confirming a correction result when a program is debugged.
The present invention relates to a retesting method and a device therefor.

[0002]

2. Description of the Related Art Conventionally, in a retest (hereinafter simply referred to as "retest") for confirming a correction result when a program is debugged, the contents of test data are saved from the viewpoint of saving test time. That is, based on the judgment as to whether or not the data is affected by the above-mentioned correction, the data to be retested is judged by the person in charge of retesting by himself and the test data at the time of retesting is judged. Had been selected. Also, the person in charge again verified the result of the retest based on the selection as described above by himself. In addition,
As a technique related to this, for example, Japanese Patent Laid-Open No. 1-226043
The technique disclosed in the publication is known. In this technique, as a method of verifying the retest result, there is a method of creating correct answer data in advance and comparing the correct answer data with an actual test result.

[0003]

The above-mentioned prior art has the following problems. First, the former of the above-mentioned conventional techniques, that is, the method of manually extracting the test data to be retested is time-consuming and incomplete, and there is a problem that sufficient retesting is not performed. Also, regarding the verification of the test results, it is necessary to verify all the test results again with one's own eyes, and there is a problem that the test results are likely to be incomplete. Further, the latter of the above-mentioned conventional techniques, that is, in the verification method disclosed in Japanese Patent Laid-Open No. 1-226043, the correct answer data must be created in advance, which requires a lot of trouble. There's a problem. The present invention has been made in view of the above circumstances, and an object of the present invention is to solve the above-mentioned problems in the conventional technique, facilitate extraction of test data to be retested, and verify the test result. Also, regarding the above, it is to provide a retest method and an apparatus therefor capable of facilitating the confirmation.

[0004]

The above object of the present invention is to provide a retest method for determining the test completeness of a program, in which the retest range at the time of module modification is defined, and the test data and related information of the module to be tested are provided. Based on the extracted test data, re-execute the extracted test data, and compare and verify the (previous) executed test result and the present test result for the test data, and a retest method, and This is achieved by a device therefor.

[0005]

In the retesting method according to the present invention, the relationship between the test data and the test target module is grasped by the change of the test coverage ratio collected at the time of the test execution, and the related test data and the test target module are associated with each other. The test data to be tested at the time of retest is extracted based on the information related to and the test data is automatically re-executed, and the previous (executed) test result and the current test result for that test data are To compare automatically. As described above, since the relationship between the test data and the test target module is grasped by the change of the test coverage rate, the effect of facilitating the extraction of the test data at the time of the retest can be obtained. In addition, the comparison result between the previous test result and the present test result outputs only the difference information, so that there is an effect that only the above-mentioned difference can be confirmed.

[0006]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a configuration diagram of a test apparatus showing an embodiment of the present invention. In the figure, 1 is a terminal device,
The correction module name 15 is input. Reference numeral 2 denotes a retesting device, which is composed of a test data extracting unit 3, a test executing unit 4, a test data grasping unit 5, and a test result verifying unit 6. The test data extraction unit described above extracts the test data related to the correction module name 15 from the test data related information file 7 and outputs the result to the test data extraction file 8. The test execution unit 4 reads the test data from the test data file 9 and the test program from the test target program file 10 based on the information in the test data extraction file 8, and executes the test. Further, the test execution unit 4 inputs the test coverage information from the test coverage information file 11 and collects the test coverage during the test. The test data grasping unit 5 associates the module with the changed test coverage ratio, which is collected by the test executing unit 4, with the test data. Further, the test result verification unit 6 compares the verification test result in the verification test result file 12 with the previous test result in the verification data file 13 and outputs the result to the verification result file 14.

Next, the information in each file shown in FIG. 1 will be described in detail with reference to FIGS. 2 to 7. First, FIG. 2 is a diagram showing an example of the test data = module correspondence table 16 in the test data related information file 7. The test data = module correspondence table 16 uses a two-dimensional table for associating the test data 17 with the test target module 18, as shown in the figure. Next, FIG.
FIG. 8 is a diagram showing an example of a test data name list 19 in the test data extraction file 8. The test data name is
It is composed of the test data name to be retested, which is related to the correction module name 15 input from the terminal device 1.
FIG. 4 is a diagram showing an example of the test data 20 in the test data file 9. The test data 20 contains
As shown in the figure, an initial data setting unit 21 that defines the state at the start of the test, and a test procedure unit 22 that describes the test procedure by a command input to the test execution unit 4
Is described.

FIG. 5 is a diagram showing an example of the test coverage information 23 in the test coverage information file 11. The test coverage information 23 is represented by the number of executed statements 24 of the module to be tested, the number of branching directions 25, the number of executed statements / total number of sentences 27, and the number of passing branching directions / the number of all branching directions 28. Test coverage rate 2
6, coverage collection position (position of execution statement or position of branch statement) 29, type 3 indicating execution statement or branch direction
0, the collection state flag 31. FIG. 6 is a diagram showing an example of the test result 32 in the verification test result file 12 and the verification data file 13. The test result 32 is the verification key 33 and the confirmation contents 34 during the test.
Made of. The verification key 33, as shown in FIG.
It is composed of a test target program name 35, a test target module name 36, and an execution interruption position 37. Hereinafter, the operation of each unit of the present embodiment configured as described above will be described based on the process flow charts shown in FIGS. 8 to 11.

FIG. 8 is a processing flow chart of the test data extracting section 3. First, the correction module name 15 is input from the terminal device 1 (step 201), and the correspondence table 16 of the test data and the test target module is input from the test data related information file 7 (step 202). Next, it is judged whether or not there is a relation between the corrected module name 15, the test data and the test data name in the correspondence table 16 of the test target module (step 204), and if there is a relation, the test data name is stored in the test data extraction file 8. It is output to the test data name list 19 (step 205). Step 20
4 and step 205 are repeated until all the test data in the correspondence table 16 of the test data and the module to be tested are completed (step 203). FIG. 9 is a process flow diagram of the test execution unit 4. In step 206, the test data name list 19 output by the test data extraction unit 3 is input to the test data extraction file 8.
Steps 208 to 218 are repeated for all the input test data in the test data name list 19 (step 206).

That is, the test data 2 corresponding to the test data names listed in the test data name list 19
Input 0 from the test data file 9 (step 20
8) Input the test coverage information 23 of the module to be tested from the test coverage information file 11.
(Step 209). Next, in step 210, the test target program is read from the test target program file 10 and execution is started. During execution of the test target program, if the execution position is the test coverage collection position (step 211), the coverage collection state flag 31 in the test coverage information 23 is operated to bring it into the passing state.
(Step 212). When the execution position is the interruption position designated by the test data 20 (step 213), the verification key 33 and the confirmation content 34 are output together with the verification test result file 12 (step 215). Steps 211 to 214 are repeated until the execution of the program under test is completed (step 215).

Then, at the time when the execution of the test target program is completed, based on the coverage collection state flag 31 collected during the execution of the test target program, the test coverage rate 26 among the modules collecting the test coverage is determined. If the value has changed (step 216), the test data grasping unit 5 associates the module with the executed test data (step 217). Then, the test coverage information 23 changed by executing the test data 20 is output to the test coverage information file 11 and updated (step 218). FIG. 10 is a process flow diagram of the test data grasping unit 5. The correspondence table 16 between the test data and the test target module in the test data related file 7 is checked by the test data name and the test target module name in which the test coverage ratio has changed (step 2
19) If the test data and the test target module are not associated (step 220), they are registered in the correspondence table 16 and the test data and the test target module are associated (step 221).

FIG. 11 is a process flow chart of the test result verification unit 6. First, in step 222, the verification test result is read from the verification test result file 12, and then in step 223, the previous test result is read from the verification data file 13. Then, the verification key 33
And the check contents 34 are compared (step 224). If they do not match, different test results and verification data are output to the verification result file 14 (step 225). If they match, they match. It is output to the verification result file 14 (step 226). Step 224 to step 2 until all test results are verified
26 is repeated (step 227). According to the above-mentioned embodiment, it becomes possible to automatically extract the test data to be retested, and it is only necessary to confirm the difference in the verification of the test result, so that the retesting is easy. The effect of becoming It is needless to say that the above embodiment shows one example of the present invention, and the present invention should not be limited to this.

[0013]

As described above in detail, according to the present invention, it becomes easy to extract test data to be retested,
Further, with respect to the verification of the test result, the re-testing method and the apparatus therefor capable of facilitating the confirmation can be realized.

[0014]

[Brief description of drawings]

FIG. 1 is a configuration diagram of a test apparatus showing an embodiment of the present invention.

FIG. 2 is a test data related information file 7 according to the embodiment.
It is a figure which shows an example of the test data = module correspondence table 16 in.

FIG. 3 is a diagram showing an example of a test data name list 19 in a test data extraction file 8 according to an embodiment.

FIG. 4 is a diagram showing an example of test data 20 in a test data file 9 according to an embodiment.

FIG. 5 is a test coverage information file 1 according to the embodiment.
It is a figure which shows an example of the test coverage information 23 in 1.

FIG. 6 is a diagram showing an example of a test result 32 in a verification test result file 12 and a verification data file 13 according to the embodiment.

FIG. 7 is a diagram showing an example of a configuration of a verification key 33 according to the embodiment.

FIG. 8 is a process flow diagram of the test data extraction unit 3 according to the embodiment.

FIG. 9 is a process flow diagram of the test execution unit 4 according to the embodiment.

FIG. 10 is a process flow diagram of the test data grasping unit 5 according to the embodiment.

FIG. 11 is a process flow diagram of the test result verification unit 6 according to the embodiment.

[Explanation of symbols]

1: terminal device, 2: retest device, 3: test data extraction unit, 4: test execution unit, 5: test data grasping unit,
6: Test result verification unit, 7: Test data related information file, 8: Test data extraction file, 9: Test data file, 10: Test target program file, 1
1: Test coverage information file, 12: Verification test result file, 13: Verification data file, 14:
Verification result file, 15: correction module name, 16:
Test data = test target module correspondence table, 17: test data name, 18: module name, 19: test data name list, 20: test data, 21: initial data setting section, 22: test procedure section, 23: test coverage information , 24: number of executable statements, 25: number of branch directions, 2
6: test coverage rate, 27: number of executed statements / number of executed statements, 28: number of executed branch directions / number of branch directions, 29: coverage collection position, 30: type, 31: collection status flag , 32: test result, 33: verification key,
34: test result (confirmation content), 35: test target program name, 36: test target module name, 37: execution interruption position.

Claims (5)

[Claims] 1. A retest method for determining the test coverage of a program, wherein a retest range at the time of module modification is extracted based on test data and related information of a test target module, and the extracted test data is extracted. A retesting method comprising re-executing and comparing and verifying a previous (executed) test result and a present test result for the test data. 2. The retesting method according to claim 1, wherein the relationship information between the test data and the test target module is grasped by the change of the test coverage rate when the test data is executed. 3. The retesting method according to claim 1, wherein the relationship between the test data and the module to be tested is detected by detecting a module passing through when the test data is executed. 4. A user specifies a test result comparison key in test data in advance, outputs internal information of a test module in association with the key at the time of test execution, and outputs the output result to use the key. The retesting method according to claim 1, wherein the retesting is performed by comparing and verifying each. 5. A means for extracting test data to be retested from related information of the test data and the module to be tested, a means for executing the test data extracted by the extracting means, and collecting test coverage, and a test. A retesting apparatus comprising means for grasping a relationship between test data and a module to be tested by a change in coverage rate and means for automatically comparing and verifying a previous test result and a present test result.