JP2643819B2 - Bug management system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a bug management system, and more particularly, to a bug management system in a unit test phase during program development.

[0002]

2. Description of the Related Art Conventionally, a bug picked up in a unit test of a program has been used for judging the quality of a program by generating a bug management slip for each bug by a tester.

However, in such a conventional method, the bug report is left to the tester, so creating a bug management slip is a burden on the tester, and the bug report is likely to be omitted. However, since the method of catching the number of bugs was dependent on the tester, there was a problem that the number of bugs recorded for a similar event might be different.

Therefore, a test process support system has been proposed which compares a test execution result with result determination data and automatically outputs a bug form to prevent omission of a bug from being recorded. (Japanese Unexamined Patent Publication No. 63-1294)
No. 33).

[0005]

In the above-mentioned conventional test process support system, although the output of a bug form is automated, it is not possible to collectively manage even the cause of the bug. Therefore, there has been a problem that the cause of the bug has to be investigated for each test based on the bug vote, and the cause of the bug investigated in the previous test has to be repeatedly investigated.

SUMMARY OF THE INVENTION In view of the above, an object of the present invention is to reduce the load on a tester in investigating the cause of a bug by managing not only the bug information but also the cause of the bug in a bug information management unit. It is to provide a bug management system as described above.

[0007]

According to the present invention, there is provided a bug management system comprising: a test information management unit having test data of a test performed on a program under test and an expected value of a test result; Test execution means for executing the program under test by data; a test result storage unit for storing a test result obtained by executing the program under test; a test result of the test result storage unit and the test information management unit Test result verification means for matching the corresponding test result expectation value with the corresponding test result, and when there is a mismatch, the mismatch status is extracted as bug information, and the bug information extracted by the test result verification means is collectively managed as a bug information management record. and bug information management unit, or bug information management records management in this bug information management unit Bugs manifest editing output means for editing outputs bugs manifest, relevant bugs tube of the causes of bugs investigated on the basis of the bug manifest Bugs management unit
Type and bug cause registration means for registering the cause division sense record, the number of excised bugs in the number and the bug information management section of the test results expected values testing of the test information managing unit, the test Test results period
A bug extraction status determination unit that outputs the number of the extracted bug information with respect to the number of waiting values as a bug extraction status determination result , and a cause of the bug information management record of the bug information management unit.
Bug content analyzing means for classifying and totaling the bug causes based on the classification and outputting the result as a bug content analysis result.

[0008]

Next, the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a bug management system according to one embodiment of the present invention. The main part of the bug management system according to the present embodiment includes a program under test 1, a test information management unit 2, a test execution unit 3, a test result storage unit 4, and a bug management processing unit 14. I have.

The bug management processing unit 14 includes a test result verification unit 5, a bug information management unit 6, a bug cause registration unit 7,
A bug management form editing / outputting means 8, a bug management form 9, a bug extraction status determination means 10, a bug extraction status determination result 11,
It is configured to include a bug content analysis means 12 and a bug content analysis result 13.

The program under test 1 is a program to be tested.

The test information management unit 2 is a file that holds test data 21 of a test to be performed on the program under test 1 and a test result expected value 22 expected by executing the program under test 1.

The test execution means 3 inputs the test data 21 of the test information management unit 2 to the program under test 1, executes the test, and executes the test results (output parameters, output data, update results of files, etc.). ) Is output.

The test result storage unit 4 includes the test execution unit 3
Is a file that saves the test results output by.

The test result verification means 5 compares the test result of the test result storage unit 4 with the corresponding test result expected value 22 of the test information management unit 2, and if there is a mismatch, the content of the mismatch is regarded as bug information and the bug information is managed. This is a means for extracting to the part 6.

The bug information management section 6 is a file for collectively managing the extracted bug information.

The bug cause registration means 7 is a means for registering the cause of the extracted bug in the bug information management section 6.

The bug management form editing and outputting means 8 is a means for editing and outputting the bug management form 9 based on the bug information of the bug information managing section 6.

The bug extraction status determination means 10 inputs the number of test result expected values 22 of the test information management unit 2 and the number of bug information of the bug information management unit 6 to determine the bug extraction status, and to determine the quality of the test. This is a means for outputting a bug extraction status determination result 11 indicating the following.

The bug content analysis means 12 is a means for inputting bug information from the bug information management unit 6, classifying bugs according to their contents and causes, and outputting a bug content analysis result 13.

FIG. 2 is a diagram showing a structure of a test result expected value record stored in the test information management unit 2. The test result expected value record includes a test number and expected value data.

FIG. 3 is a diagram showing the structure of a test result record stored in the test result storage unit 4. The test result record includes a test number, a test date and time, and test result data.

FIG. 4 is a diagram showing the structure of a bug information management record stored in the bug information management unit 6. The bug information management record includes a test number, a test date and time, an event category, a cause category, expected value data, and mismatch data. The event category encodes and holds the result abnormalities and the program abort categories for the test results.
The cause category is set by the bug cause registration means 7. In the case of a program abort, no mismatch data is created.

FIG. 5 is a diagram showing the structure of the expected value data in the test result expected value record and the bug information management record and the structure of the test result data in the test result record. The expected value data and the test result data include a data length and a data part. If there is no test result due to a program abort or the like, only the data length is used.

FIG. 6 is a diagram showing the structure of mismatched data in the bug information management record. The unmatched data is composed of the entire length and one or more sets of information including test results that did not match the data length, offset value, length, and expected value. The offset value is the position of the data at which the test result did not match the expected value (the absolute position from the beginning of the data part of the expected value data). The length is the length of the mismatched portion.

FIGS. 7A and 7B are diagrams illustrating examples of the contents of the mismatch data in the expected test result record, the test result record, and the bug information management record. FIG. 7A illustrates the expected test result record, and FIG. Result records,
(C) shows the mismatch data in the bug information management record.

Referring to FIG. 8, test result verification means 5
The processing in step S101 is for inputting a test result and a test result expected value, an end determination step S102, and a step S103 for matching the test result and the test result expected value.
, Match determination step S104, bug information registration step S105, and test result verification completion notification step S10.
6

Referring to FIG. 9, the processing of the bug extraction status determination means 10 is performed in the expected result number of test results input step S2.
01, a number of bugs to be picked input step S202, a step of determining bugs and test quality S203, and a step of outputting bugs determination results S204.

Referring to FIG. 10, bug content analysis means 1
The process 2 is a bug information management record input step S30
1, a bug cause classification and counting step S302, and a bug content analysis result output step S303.

Next, the operation of the bug management system according to the present embodiment thus configured will be described.

In the unit test phase at the time of program development, the test execution means 3 applies the test data 21 stored in the test information management unit 2 to the program under test 1.
To execute the test, and outputs the test results (update results of output parameters, output data, files, etc.) to the test result storage unit 4.

When the execution of the test is completed normally, the bug management processing unit 14 performs the following series of processes to manage the bug.

The test result verification means 5 inputs the test result output to the test result storage section 4 by the test execution means 3 and the corresponding test result expected value 22 registered in the test information management section 2, respectively. (Step S10
1) Verification of the test result is performed by matching (step S103). As a result of the verification, if the test result matches the test result expected value 22 (step S10)
4), the test result verification means 5 executes the step S1.
01, and returns the test result and the test result expected value 22.
Does not match (No in step S104),
The content of the mismatch is registered as bug information in the bug information management unit 6 (step S105), and the control returns to step S101. When the test result of the test result storage unit 4 and the test result expected value 22 of the test information management unit 2 are completed (Yes in step S102), the test result verification unit 5 notifies the completion of the test result verification to a console (not shown). Etc. (step S106), and the process ends.

For example, the test result record is shown in FIG.
When the corresponding test result expected value record is as shown in FIG. 7A, mismatch data as shown in FIG. 7C is output in the bug information management record. .

The bug management form editing and outputting means 8 outputs the name of the program under test of the bug information registered in the bug information
The date and time of the occurrence of the bug and the content of the bug (a state of mismatch of the test results) are edited and output as a bug management slip 9.

The tester investigates the cause of the bug recorded in the bug management slip 9, and when the cause is found, the bug cause registration means 7 uses the bug information management record of the bug information management unit 6 as a cause classification. register.

The bug extraction status determination means 10 inputs the number of test result expected values 22 that have been tested by the test information management unit 2 (step S 201), and the bug information management unit 6 determines the number of bug information extracted. Input (Step S20)
2), bug extraction status (= number of bug information extracted / te
A judgment test result count expected value 22) carrying out the test (step S203), digested status test (= test
Number of test results with expected value of 22 / test result
Total number of expected values 22) , bug extraction status and test quality judgment result (test digestion status is above a certain level value
Or whether the bug extraction status is equal to or higher than a certain level value) is output as the bug extraction status determination result 11 (step S20).
4).

The bug content analysis means 12 inputs the bug information management record of the bug information management section 6 (step S30).
1) Classify and compile the bug causes based on the cause classification (step S302), and list the summary list of the extracted bug information, the summary list of the bug causes, and the list of the bugs for which the cause has not been registered (unresolved bugs). It is output as the content analysis result 13 (step S303).

[0039]

As described above, the present invention comprises a test information management unit, a test execution unit, a test result storage unit, a test result verification unit, a bug information management unit, a bug cause registration unit, and a bug management form editing and output unit. The bug information management department collectively manages not only bug information but also bug causes, so that the bug causes investigated in the previous test do not have to be repeated and the bugs of the tester This has the effect of reducing the load on investigating the cause.

Further, the provision of the bug extraction status determination means has an effect that the test quality can be determined by analyzing the bug extraction status in more detail.

Furthermore, the provision of the bug content analysis means makes it possible to easily analyze bugs that are easy to create at the time of designing a program by classifying and totaling the causes of the bugs, thereby improving the quality of the subsequent program design. effective.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a bug management system according to an embodiment of the present invention.

FIG. 2 is a diagram showing a structure of a test result expected value record stored in a test information management unit in FIG. 1;

FIG. 3 is a diagram illustrating a structure of a test result record stored in a test result storage unit in FIG. 1;

FIG. 4 is a diagram showing a structure of a bug information management record stored in a bug information management unit in FIG.

5 is a diagram showing the structure of the expected value data in the test result expected value record of FIG. 2, the bug information management record of FIG. 4, and the test result data in the test result record of FIG. 3;

FIG. 6 is a diagram showing a structure of mismatched data in the bug information management record of FIG. 4;

7A and 7B are diagrams exemplifying the contents of mismatched data in the test result expected value record of FIG. 2, the test result record of FIG. 3, and the bug information management record of FIG. 4, and FIG. , (B) shows the test result record, and (c) shows the mismatch data in the bug information management record.

FIG. 8 is a flowchart showing a process of a test result verification means in FIG. 1;

FIG. 9 is a flowchart showing a process of a bug extraction situation determination unit in FIG. 1;

FIG. 10 is a flowchart showing a process of a bug content analysis unit in FIG. 1;

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Tested program 2 Test information management part 3 Test execution means 4 Test result storage part 5 Test result verification means 6 Bug information management part 7 Bug cause registration means 8 Bug management form edit output means 9 Bug management form 10 Bug extraction status judgment means 11 Bug Extraction Status Judgment Result 12 Bug Content Analysis Means 13 Bug Content Analysis Result 14 Bug Management Processing Unit

Claims (3)

(57) [Claims] 1. A test information management unit that holds test data of a test to be executed on a program under test and an expected value of a test result, and a test execution that executes the program under test using the test data of the test information management unit. Means, a test result storage unit for storing a test result obtained by executing the program to be tested, and a test result of the test result storage unit and a corresponding test result expected value of the test information management unit are compared with each other, and are not matched. When there is a test result, a test result verification means for extracting the mismatch status as bug information, and the bug information extracted by the test result verification means are backed up.
Bugs management unit for collectively managed as grayed information management record, and bug manifest editing output means for editing outputs bugs manifest from the bugs bugs managed by the management unit management record <br/>, the bug tracking The cause of the bug investigated on the basis of the vote is stored in the corresponding bug information management record of the bug information management section.
A bug management system comprising: a bug cause registration unit for registering a bug as a minute . 2. A test of the test information management unit is performed.
Test results expected value number and the removal of the bug information management unit of
Te enter the number of bug information, it was carried out the test, which is
Bug information extracted for the expected number of strike results
Bug tracking system according to claim 1, further comprising a bug excised condition determining means for outputting the number as a bug excised status determination result. 3. A bug information management record of the bug information management unit.
2. The bug management system according to claim 1, further comprising: a bug content analyzing unit that classifies and totals bug causes based on a cause category of the code and outputs the result as a bug content analysis result.