JPH01229341A - Program test method - Google Patents

Abstract

PURPOSE:To obtain a program test system which considerably reduces a re-test operation by setting only coverage information in a range which is affected by means of a change when there is the change in a program, and succeeding other coverage information after the change. CONSTITUTION:The succeeding processing of coverage information is to map program execution history information recorded in a hardware mechanism 1, namely, extracted coverage information MT1 on an object code like OT1. Next, a program change influence range (AT1 of analysis processing mechanism 2 on a source code group ST2 after the change of the program is grasped. Coverage information beyond the range of change influence (coverage information corresponding to OBJ1 and OBJ2 of OT2) is succeeded on the object code of OT2 after the change of the program. Next, coverage information on the succeeded object code is mapped in a program execution history MT2 after the hardware mechanism 1 has information-succeeded coverage information.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a program test method in a data processing system, and particularly to a program test method suitable for inheritance of coverage information when a part of the program is changed.

[Conventional technology]

In program testing, the concept of a test force A register that uses a hardware mechanism to determine whether instructions are executed or branches are executed at the machine code level has become common. In this case, traditionally there was a change in part of the program,
When a part of the source code was changed and the memory location of the machine language loaded into memory was changed, all coverage information for the entire program before the change was invalidated and all tests were re-executed. In addition, related to program testing, for example, Japanese Patent Application Laid-Open No. 58-181
No. 152 is mentioned.

[Problem to be solved by the invention]

Normally, during program development, many defective corrections that change part of the source code occur.

In the prior art, even in such a case, all the coverage information of the entire program before the change is invalidated and the test is repeated, which has the problem of poor test efficiency.

An object of the present invention is to provide a program test in which, when a program is changed, only the coverage information affected by the change is invalidated, and other coverage information can be inherited after the change, thereby significantly reducing re-testing work. The goal is to provide a method.

[Means to solve the problem]

The above purpose is to provide a table representing object code information including source code information of a program to be loaded into memory and instruction correspondence information with the source code, and when there is a change in the program, the source code before the change and the changed This is achieved by analyzing the scope of program change influence from the subsequent source code, and inheriting the program execution history information before the change to the object code after the change, excluding the history information of the change influence scope.

[For production]

In the present invention, program history information at the machine language level, that is, coverage information, corresponds to the source code, and the coverage information of the part excluding the program change influence range grasped on the source code is inherited. As a result, the scope of program change is not simply invalidating only the part where the instructions have changed at the machine language level, or invalidating all sections where the change has been made, but rather , it is possible to grasp the data flow, so the inheritance range of coverage information can be made accurate.

〔Example〕

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a conceptual diagram of an embodiment of the present invention. In Figure 1,
1 is a hardware mechanism that collects and records program execution history; 2 is a source code change influence range analysis processor 41;
5 is shown. MTI is program execution history information before coverage information is inherited, and MT2 is program execution history information after coverage information is inherited.

The hardware mechanism 1 holds it. OTI is the object code table before the program change, OT2 is the object code table after the program change, ATL is the source code group affected by the change, STI is the source code group before the program change, and ST2 is the source code group after the program change. be.

OB J i in each table is an object code, S
i represents source code.

Now, the correspondence between the source code, object code, and location controllers on memory before the program change is as shown by OTI. Sl corresponds to 0BJI at location 0 and 0BJ2 at location 1, and S2 corresponds to location 2.
Corresponds to 0BJ3.

S3 is location 3 0BJ4 and location 4 0
It corresponds to BJ5. Also, the correspondence between the source code, object code, and memory locations after the program change is as shown by OT2, where Sl is 0BJ1 at location O and 0BJ2 at location 1.
82' corresponds to 0BJ3' of location 2 and OB J 3' of location 3, and S3 corresponds to 0BJ4 of location 4 and 0BJ5 of location 5.
shall correspond to The program has 8 source codes
2 to 32', and the affected range of the program, that is, the range on the source code that requires retesting, is S2' and S3, and the program execution method location in MTI is 0°1. 2.3.

The coverage information relay process will be described below with reference to FIG. Note that the process of collecting coverage information itself is well known and is not directly related to the gist of the present invention, so a description thereof will be omitted.

Step 11 Map the program execution history information recorded in the hardware mechanism 1, that is, the collected coverage information MTI, onto the object code like OTI.

The coverage information MT1 collected by the hardware mechanism 1 is
If the machine language loaded in locations 0 to 3 has already been tested and executed (indicated by a logical value of #I11), the machine language loaded in location 4 has not yet been executed (indicated by a logical value of “0”). First,
Associate object code and location from loading information.

For example, the machine language loaded at location 0 and executed is 0BJI, and the machine language loaded at location 4 and not executed is 0BJ5. Further, the source code and the object code are associated with each other from object code information having correspondence information between the source code and the object code obtained from the compiler when the source code group before program change is compiled. for example,
Object code BOJ 1. OBJ 2 is an object expansion code of the source code S1. in this case,
Due to compiler optimization, one object code may correspond to multiple source codes.

As described above, the source code before program change,
A table OTI showing the correspondence between object code, location, and coverage information is obtained.

Step 12: Ascertain the program change influence range (ATl of the analysis processing mechanism 2) on the source code group ST2 after the program change. The source code group STI before the program change can also be obtained from the source code group ST2 after the program change and the changed difference source code group accumulated when the program is changed.

In this case, source code S2 is changed due to program change.
It is assumed that S2' has been changed to S2', and that source codes S1 and S3 have not been changed.

First, in the source code change influence range analysis processing mechanism 2,
The changed source code S2' is grasped from the source code group ST1 before the program change and the source code group ST2 after the program change. Furthermore, by performing, for example, control flow analysis or data flow analysis on the source code group ST2 after the program change, the source code change influence range other than 82' (83 in ATL) is grasped. In other words, in control flow analysis, the changed source code (
In addition to the source code (82') in ATL, the source code (33 in ATL) to which control may be transferred after execution of the changed source code (S2') is set as the scope of change influence. In data flow analysis, in addition to the changed source code (82' in ATL), the changed source code (S2'
) source code (ATL) that uses the variables used in
83) is the scope of change influence.

Step 13 Inherit coverage information outside the range of change influence (coverage information corresponding to 0BJI and 0BJ2 of OT2) on the object code after the program change (object code of OT2).

First, source code and object code are associated on OT2 from object code information having correspondence information between source code and object code obtained from a compiler when compiling a source code group after a program change. For example, 0BJ3' and 0BJ3'' are object expansion codes of source code S2'. In this case, one object code may correspond to multiple source codes due to compiler optimization.

The change influence range (indicated by an umbrella) in OT2 is obtained from the AT1 information.

Coverage information is inherited by associating the source code and object code of OT1 and OT2.

For example, 0 corresponding to source code S1 in OT2
The coverage information of BJI and OBJ2 is inherited as is (O
If the coverage information of Tl is 1, the coverage information of OT2 is set to 1, and if the coverage information of OTI is O, the coverage information of OT2 is set to O).On the other hand, 0BJ3' corresponding to source code S2'S3 in OT2, OBJ 3”
, 0BJ4. As for the coverage information of OBJ 5, since S2' and S3 are the source code in the scope of change influence, the coverage information is invalidated and is not inherited (the coverage information of OT2 is set to O).

The coverage information of OT2 is expressed as 1 for outside the change influence range and O for change influence range, and OTI for each object code.
(Coverage information for object codes that do not correspond to OTl is set to 0) with the coverage information of . When one object code corresponds to multiple source codes due to compiler optimization, if any source code is within the change-affected range, the corresponding object code is considered to be within the change-affected range.

Step 14 Map the coverage information on the inherited object code to the program execution history information MT2 of the hardware mechanism 1 after the inheritance of the coverage information.

Here, MTI and MT2 may be program execution history information corresponding to memory addresses on the same hardware. First, the correspondence between the OT2 object code and location is obtained from the loading information. Furthermore, for example, 1 is mapped to location O of MT2 and O is mapped to location 2 from the information of OT2.

According to this embodiment, the machine language level coverage information loaded into locations 0 and 1 of MTI can be inherited by the machine language level coverage information loaded into locations O and 1 of MT2. , M'r2, it is possible to obtain machine language level coverage information indicating that location O and location 1 are already executed and do not require retesting.

〔Effect of the invention〕

As explained above, according to the present invention, coverage information collected at the machine language level during program testing can be inherited based on program influence range information at the source code level even after the program is changed. Coverage information in a range that requires retesting due to program changes can be invalidated without omission, and coverage information can be inherited with minimal invalidation of coverage information, making it possible to significantly reduce retesting work. .

[Brief explanation of the drawing]

FIG. 1 is a conceptual diagram of an embodiment of the present invention, and FIG. 2 is a flowchart for explaining coverage information inheritance processing based on FIG. 1. MTI...Program execution history information before coverage information inheritance, MT2...Program execution history information after coverage information inheritance, ○T1...Object code table before program change, OT2...Object after program change Code table, ATL... Source code group in the change affected range, STI... Source code group before program change, Sr1... Source code group after program change.

Claims (1)

[Claims] (1) In a program test method that tests a program and records its execution history, it is equipped with a table that represents object code information including program source code information and instruction correspondence information with the source code, and when a program change occurs. In this case, analyze the scope of program changes from the source code before the change and the source code after the change, and inherit the program execution history information before the change to the object code after the change, excluding the history information of the scope of change influence. A program testing method characterized by: