JPH0210443A - Reset case selecting system - Google Patents

Abstract

PURPOSE:To efficiently execute the test again by analyzing an influence which correction of a source program has upon the control flow of this program and selecting the test case requiring the retest for source program correction from a table of correspondence between best cases and fundamental paths. CONSTITUTION:In the case of source program correction, a change influence range analysis 4 extracts fundamental paths, which are affected by this correction, in accordance with source program difference information in a source program library 11 (the library management function of a general operating system) and control flow information 13. Thereafter, retest case selection 5 inputs said results and a table 16 of correspondence between test cases and fundamental paths and selects test cases requiring the retest to output a retest case number list 18. A retest controller 6 uses a test case 5 and a load module 14 as parameters based on the selection information to start a tester 3, thus executing the test.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a test automation method for software systems, and in particular to automatic selection and execution of test cases that require retesting for source program modification. Conventional technology] Conventionally, in this type of test case selection method,
As in No. 166443, the environment of the test case in the database (name of product to be tested, classification of basic function/detailed function/failure test, etc., equipment used, etc.) and the test specified by the user during actual test execution. Testable test cases were selected and launched by comparing them with the execution environment.

[Problem to be solved by the invention]

In software testing, most of the testing work involves retesting due to source program modifications.
Conventional techniques, including the above-mentioned patents, lack consideration for range selection and automation of retesting (generally referred to as regression testing) for source program modifications.

An object of the present invention is to analyze basic paths affected by source program modification, automatically select the minimum number of test cases necessary for retesting, and automatically execute them.

[Means to solve the problem]

The above objectives include control flow information consisting of a group of basic paths obtained by source program analysis, a correspondence table between test cases and basic paths, a means for extracting influencing basic paths corresponding to source program modifications, a means for selecting test cases including the basic paths listed on the left, and This is achieved by a test execution means based on the above.

[Effect]

Analyze the impact that source program modifications have on the control flow of this program, and select test cases that include the affected basic paths, that is, test cases that require retesting due to source program modifications, and create a correspondence table between test cases and basic paths. Choose from. Further, a test based on this test case is executed by the test execution means.

〔Example〕

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

In Figure 1, compiler 1 is source program library 1
1, control flow information 13 consisting of an object program library 12 and a group of basic paths is created. Linkage editor 2 is object program library 12
and load module 14 of the program under test.
Create.

The tester 3 loads a load module 14, a test case 15 . and control flow information 13 to execute the test, create/update the correspondence table 16 between test cases and basic paths, and output the test results 17.

In the case of source program modification, change impact range analysis 4 is
An influential basic path is extracted from the source program difference information in the source program library 11 (this is a library management function of a general general-purpose operating system) and the control flow information 13. Retest case selection 5
inputs the above-mentioned result, test case, and basic path correspondence table 16, selects a test case that requires retesting, and outputs a retest case number list 18. Also, the retest controller 6 uses the test case 15 based on the above selection information.
and the load module 14 as parameters to start the tester 3 and execute the test.

FIG. 2 shows an example of the processing flow of the source program in the source program library 11 of FIG. This processing flow begins at entry point 30. Each process 41-46. Control branch points and inflow points 31-36. Consisting of exit points 39.

FIG. 3 shows a control flow corresponding to the processing flow of FIG. 2, and is expressed as a set of basic paths obtained by dividing this control flow at control branch points and inflow points. The nodes 30 to 39 in FIG. 3 correspond to the respective numbers of the entry point, the first branch point, the inflow point, and the exit point in FIG. 2. Also, the basic path is a −j
It is expressed as.

Each basic path has 9 adjacent entry points and 9 branch points in FIG.

It corresponds to a group of command statements including a blank statement between the inflow point and the exit point. For example, the basic path C corresponds to the processing box 43 in FIG. 2 and the statement group of the processing box 43.

Figure 4 shows test case t1 for the processing flow in Figure 2.
An example of a correspondence table between ~t4 and basic paths is shown.

For example, test t1 has basic paths a, b, Q, 8. Indicates that it consists of f.

When the source program is modified in the processing box 43 of the processing flow in FIG. 2, the change range analysis 4 extracts the basic path C. In the re-test case selection 5, a test case t1 including the basic path C is selected from the correspondence table of test cases and basic paths shown in FIG. That is, it is shown that only test case t1 needs to be retested for the change shown in processing box 43 in the processing flow of FIG. 2. The retest controller 6 performs test case t1
Start Tester 3 by instructing.

〔Effect of the invention〕

According to the present invention, it is possible to automatically select retest cases that affect source program modification, and to execute the minimum necessary number of retests, making it possible to efficiently perform retesting corresponding to source program modification, which accounts for the majority of testing work. Can be implemented.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing one embodiment of the present invention. FIG. 2 is a processing flow diagram of a source program, FIG. 3 is a control flow diagram corresponding to FIG. 2, and FIG. 4 is an explanatory diagram of the correspondence between test cases and basic paths corresponding to FIG. 3. 1...Compiler, 2...Linkage editor. 3...Tester, 4...Change impact range analysis, 5...
Re-test case selection, 6... Re-test controller,
DESCRIPTION OF SYMBOLS 11... Source program library, 12... Object program library, 13... Control flow information, 14... Load module, 15... Test case, 17... Test result, 18... Replay Test case number list, 30... Entrance point, 39... Exit point, 41-46... Processing box.

Claims (1)

[Claims] 1. Analyze the source program, define the control flow divided by control branch points and inflow points as basic paths, and create test cases based on the control flow information consisting of these basic path groups and the test execution results of each test case. Based on the above correspondence table of basic paths, a means to analyze the influence on the control flow due to modification of the source program and extract the affected basic paths, and select a test case that includes the execution of the affected basic path based on the above correspondence table. A retest case selection method characterized by having a means for selecting a retest case.