JPH10214205A - Module checking device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve efficiency in debugging work by preparing a test case based on a module specification described by a designer. SOLUTION: This device is constituted by providing a module specification storage means 8, test case generating means 9, test case storage means 10, module storage means 11, module checking means 12, test result storage means 13, test result output means 14 and module correcting means 15. The module specification storage means 8 stores the module specification. The module specification describes a module name, the input parameter name of module, the output parameter name of module, the sample data of concrete value and the summary of module and is prepared by the designer of entire program constituted by linking modules. The test case of module corresponding to the module specification is prepared from the input parameter, output parameter and concrete value described in the module specification stored in the module specification storage means 8 by the test case generating means 9.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a module inspection apparatus for detecting an error in a module.

[0002]

2. Description of the Related Art A conventional technique will be described with reference to FIGS. FIG. 10 is a block diagram showing the configuration of the module inspection device. FIG. 11 is an explanatory diagram showing an example of a module to be inspected. FIG. 12 is an explanatory diagram showing an example of the module specification. FIG. 13 is an explanatory diagram showing an example of a test case.

Conventionally, in the development of large-scale software, a plurality of programmers individually create each module constituting a program, and finally combine all the modules to complete one program. A technique is used.

In the development of such software, in order to prevent program errors and keep the quality constant, a unit test for each module is performed in addition to a combination test and a system test for confirming the operation of the entire program. Has also gone.

[0005] A unit test is executed by putting an appropriate specific value into an input variable of a module, executing the module, and outputting an output value of the execution result of the module and, if the module meets specifications, executing the appropriate value. This is performed by comparing with a planned value that is a specific value that has already been calculated.

[0006] The programmer performs a unit test on one or a plurality of modules in charge of the program, corrects the module whose output value is different from the expected value, and performs the unit test again. Modules are created by repeating such operations.

[0007] In FIG. 10, the module inspection apparatus comprises:
It comprises a module storage unit 1, a test case storage unit 2, a module inspection unit 3, a module correction unit 4, a test case input unit 5, a test result storage unit 6, and a test result output unit 7.

The module storage means 1 stores one or a plurality of modules to be inspected.

The test case input means 5 is for inputting a test case by an operation of a user such as a programmer. A test case indicates specific values of an input variable of each module and an output variable of the module.

The test case storage means 2 stores the input test cases.

The module checking means 3 gives a specific value of an input variable indicated by the test case to a corresponding module to execute the module, and outputs an output value of an execution result of the module and a specific value of the output variable indicated by the test case. The target value is compared to determine whether or not they match.

The test result storage means 6 stores the judgment result of the module inspection means 3. The test result output means 7 outputs the judgment result of the module inspection means 3 on paper or screen.

The module correcting means 4 is for the user to correct an error in the module based on the judgment result of the module inspecting means 3.

The module inspection apparatus configured as described above operates as follows. First, as shown in FIG. 11, the module “module1” to be inspected has input variables input1 and input1 for inputting data to the module.
It has input2 and has an output variable output1 for outputting an execution result from the module.
Then, the module “module1” has the input variable i
An arithmetic process or the like is performed based on the data given to ninput1 and input2, and the execution result is output variable out.
Substitute into put1 and output. The above module "mo
“dule1” is stored in the module storage unit 1.

Next, the user inputs a test case through the test case input unit 5, and the input test case is stored in the test case storage unit 2. The test case includes, as shown in FIG. 12, each input variable and output variable,
Specific values corresponding to the variables are described in pairs.
Note that a test case is created by a programmer as a user based on the description in the module specification and the understanding of the module programmed by the user.

Then, when the start of the unit test is instructed by the user's operation, the module checking means 3 converts the specific values "1" and "3" of the input variables input1 and input2 indicated by the test case into the module "module1".
To be executed. And module inspection means 3
Compares the output value of the execution result of the module "module1" with the specific value "12" of the output variable output1 indicated by the test case to determine whether or not they match.

The result of the determination is stored in the test result storage means 6, and is output on paper by the test result output means 7. By viewing the output, the user can select the module “mod
It can be determined whether or not an error exists in “ule1”. Therefore, the user corrects the module "module1" by the module correcting means 4 based on the determination result. In this example, one module is described. However, after a plurality of modules are inspected and all the modules are inspected sequentially, each module is appropriately corrected based on the judgment result of the inspection. May be done.

[0018]

However, the module inspection apparatus shown in FIG. 10 has the following problems.

That is, generally, a module specification is created by a program designer, and each programmer develops a module so as to satisfy the specifications described in the module specification. Created and unit tested.

Accordingly, if the programmer mistakenly interprets the meaning of the created module in the module specification document by the designer, in the unit test, the test case created by the programmer may operate as intended by the programmer. Regardless, when the designer looks at the module, a case occurs in which the module is incorrect.

Therefore, module errors are not found until all modules are combined, and the module errors are found late, and the development period is lengthened.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and its object is to solve the problem even when a module is created by a programmer misunderstanding a module specification. It is an object of the present invention to provide a module inspection apparatus that can efficiently detect an error in a module and can increase the efficiency of a debugging operation.

[0023]

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems, the present invention is directed to the invention as set forth in claim 1, wherein module storage means for storing one or a plurality of modules to be inspected; Test case storage means for storing a test case indicating a specific value of an input variable of a module and an output variable of the module, and giving the specific value of the input variable indicated by the test case to a corresponding module to execute the module; Module inspection means for comparing an output value of an execution result of the module with a specific value of an output variable indicated by the test case to determine whether or not they match, and sequentially inspects one or a plurality of modules. A module inspection device that stores module specifications describing input variables of the module, output variables of the module, and specific values of these variables. Module specification storage means; and test case creation means for creating a test case of a module corresponding to the module specification from the input variables, output variables, and specific values described in the module specification. It is assumed that.

According to the second aspect of the present invention, a test for judging whether or not the number of test cases is insufficient by comparing the control structure of the module to be inspected with the number of test cases for the module. The present invention is characterized in that a case number determining means and a test case adding means for additionally creating a test case when the test cases are insufficient are provided.

According to the third aspect of the present invention, a data specification indicating a range of specific values to be input to the input variables of the module to be inspected or specific values to be output by the output variables of the module to be inspected is stored. And a test case adding unit that creates a test case based on the data specification.

In the invention according to claim 4, the test case adding means uses a value selected from a specific value range shown in the data specification as a specific value of the input variable, and It is characterized in that a test case is additionally created using a specific value range shown in the book.

According to the invention described in claim 5, module storage means for storing one or a plurality of modules to be inspected, and a test case indicating specific values of input variables of each module and output variables of the module. A test case storing means for storing the specific value of the input variable indicated by the test case to a corresponding module to execute the module, and output values of the execution result of the module and specific values of the output variable indicated by the test case; Module inspection means for comparing the target value to determine whether or not they match each other, and module correction means for allowing the user to correct an error in the module based on the determination result of the module inspection means. In a module inspection apparatus for sequentially inspecting a plurality of modules, an input variable of the module, an output variable of the module, and a Module specification storage means for storing a module specification describing a target value, and a test for creating a test case of a module corresponding to the module specification from input variables, output variables and specific values described in the module specification Case creating means, correction number detecting means for detecting the number of times the module has been corrected by the module correcting means, and re-test order determining means for determining the order of module re-test based on the number of corrections are provided. It is characterized by the following.

[0028]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A first embodiment of a module inspection apparatus according to the present invention will be described with reference to FIGS. 1 to 3 and FIGS. 11 and 12, and a second embodiment will be described with reference to FIGS. Next, a third embodiment will be described with reference to FIG.

[First Embodiment] FIG. 1 is a block diagram showing the configuration of a module inspection apparatus. FIG. 2 is an explanatory diagram showing an example of the module specification. FIG. 3 is an explanatory diagram of the storage contents of the test result storage means. FIG. 11 is an explanatory diagram showing an example of a module to be inspected. FIG. 13 is an explanatory diagram showing an example of a test case.

In FIG. 1, the module inspection apparatus includes a module specification storage unit 8, a test case creation unit 9,
Test case storage means 10, module storage means 11,
It comprises a module inspection unit 12, a test result storage unit 13, a test result output unit 14, and a module correction unit 15.

The module specification storing means 8 stores a module specification. As shown in FIG. 2, the module specification describes the module name, the input variable name of the module, the output variable name of the module, sample data as specific values, and an outline of the module. Is created by the designer of the entire program using the CASE tool or the like. The module specification shown in FIG.
"dule1" is input1, input
ut2, and output1 as an output variable. For example, when "1" is given to the input variable input1 and "3" is given to the input variable input2, "12" is substituted into the output variable output1 after performing a certain process. And a module that performs the output operation. In addition,
The module specification storage unit 8 stores one or a plurality of module specifications.

The test case creating means 9 creates a test case based on the module specification stored in the module specification storing means 8. More specifically, the test case creation means 9 extracts a pair of an input variable name and its sample data and a pair of an output variable name and its sample data from the module specification and creates a test case as shown in FIG. The test case is stored in the test case storage unit 10.

The module storage means 11 stores one or a plurality of modules to be inspected.

The module checking means 12 gives sample data of an input variable indicated by a test case to a corresponding module to execute the module, and outputs an output value of an execution result of the module and sample data of an output variable indicated by the test case. To determine whether they match.

The test result storage means 13 stores the judgment result of the module inspection means 12. Specifically, as shown in FIG. 3, the name of the inspected module (A
Column), names of test cases used (column B), output values of modules (column C), sample data of output values (column D), and determination results (column E).

The test result output means 14 outputs the judgment result of the module inspection means 12 on paper or screen.

The module correcting means 15 is for the user to correct a module error based on the judgment result of the module checking means 12.

Next, the state of a unit test using the module inspection apparatus configured as described above will be described.

First, the designer describes the specifications of the module in a module specification shown in FIG. This work is mainly performed by using a CASE tool or the like, and the created module specification is stored in the module specification storage unit 8.

Next, the programmer creates a module "module1" based on the module specification.
As shown in FIG. 11, this module "module1" has an input variable inp for inputting data to the module.
ut1 and input2, and an output variable output1 for outputting an execution result from the module. Then, the module “module1” performs arithmetic processing and the like based on the data given to the input variables input1 and input2, and substitutes the execution result into the output variable output1 to output. The module “module1” is stored in the module storage unit 11.

Next, the test case creating means 9 extracts a pair of an input variable name and its sample data and a pair of an output variable name and its sample data from the module specification 8 to create a test case. The created test case is stored in the test case storage unit 10. The test case is
As shown in FIG. 12, each input variable name input1, in
put2 and output variable name output1 and specific values "1", "3", and "12" corresponding to the variable are described as a pair.

When the start of the unit test is instructed by the user's operation, the module checking means 12 converts the sample data "1" and "3" of the input variables input1 and input2 indicated by the test case into the module "modul".
e1 "for execution. Then, the module checking unit 12 compares the output value (for example, “12”) of the execution result of the module “module1” with the specific value “12” of the output variable output1 indicated by the test case and determines whether or not they match. Judge.

The result of the judgment is stored in the test result storage means 13, and is output on paper by the test result output means 14. By looking at the output, the user can know whether or not there is an error in the module “module1”.

The user corrects the module "module1" by the module correcting means 15 based on the judgment result. In this example, one module is described. However, a plurality of modules may be inspected. In such a case, after all the modules are inspected sequentially, the judgment result of the inspection is performed for each module. Is appropriately corrected based on the

Since the module inspection apparatus is constructed as described above, the test case is not created by the programmer based on its own interpretation, but the test case is created based on the module specification written by the designer. You. Therefore, since the created test case is based on the intention of the designer, if it is determined that there is a module error in the unit test using this test case, it is extremely possible that the error actually exists. high. Therefore, the programmer can perform the debugging work efficiently.

Further, since the test case which has been conventionally created by the programmer need not be created by the programmer,
From a programmer's perspective, the effort is reduced by not creating test cases.

[Second Embodiment] FIG. 4 is a block diagram showing a configuration of a module inspection apparatus. 5 to 7 are explanatory diagrams of the data specification. FIG. 8 is an explanatory diagram of a test case. In FIG. 4, the same parts as those in the module inspection apparatus described in the first embodiment are denoted by the same reference numerals, and the detailed description of the same parts will be omitted.

The feature of the module inspection apparatus of the present embodiment shown in FIG. 4, which is different from that of the module inspection apparatus described in the first embodiment, is as follows.

That is, the configuration is provided with the data specification storage means 16, the test case number determination means 17, and the test case estimation means 18.

The data specification storage means 16 stores one or a plurality of data specifications. As shown in FIGS. 5 to 7, the data specification describes data names of data to be assigned to input or output variables and ranges in which specific values can be taken. FIG. 5 is a data specification of data to be input to the input variable input1 of the module “module1”.
It indicates that a value of “0” or “1” is input to the input variable input1 of “ule1”. FIG. 6 is a data specification of data input to the input variable input2 of the module “module1”. The input variable input2 of the module “module1” includes “0”.
This indicates that a value in the range of "-10" is input. FIG. 7 shows the output variable ou from the module “module1”.
This is a data specification of data output as output1, and indicates that the module "module1" is to be output by substituting a value in the range of "0 to 50" into the output variable output1. These data specifications are created by a designer using a CASE tool like the module specifications.

The test case number judging means 17 judges whether or not the required number of test cases for inspecting the module to be inspected are stored in the test case storing means 10. The number of test cases is determined based on the control structure of the module to be tested. That is, if there is one control statement in the module that branches into two depending on the condition, at least two test cases are required to perform the operation for each branch. If there are two control statements, at least four test cases are required. The test case number determination means 17 pays attention to the relationship between the number of control statements and the number of branches and the required number of test cases,
The number of test cases T required for inspecting the module is calculated. Then, the number of test cases determining means 17
Is the number of test cases and the test case storage means 1
0 and is compared with the number U of test cases corresponding to the module to be inspected, and if the number U of test cases is smaller than the number T of test cases, the test case creation instructing instruction S1 is subjected to test case estimation. Output to the means 18.

The test case estimating means 18 receives a test case creation instruction command S 1 from the test case number determining means 17.
Is received, a required number of test cases are created based on the data specification, and stored in the test case storage unit 10. More specifically, an appropriately selected value within the data range described in the data specification of the data input to the input variable input1 of the module "module1" is used as sample data for the input variable input1 of the test case, and the module "module1" Input variable i
An appropriately selected value within the data range described in the data specification of the data input to ninput2 is used as sample data for the input variable input2 of the test case. Then, the test case estimating unit 18 sets the data range described in the data specification of the data output from the output variable output1 of the module "module1" as sample data for the output variable output1 of the test case. Accordingly, in the description of the test case, for example, since the input variable input1 can take “0” or “1” as shown in FIG. 5, the sample data is set to “0” as shown in FIG. 8, and the input variable input2 is FIG.
As shown in FIG. 8, a range of “0 to 10” can be taken.
The sample data is set to “7” as shown in FIG.
Since output1 can take a range of "0 to 50" as shown in FIG. 7, the sample data is set to "0" as shown in FIG.
~ 50 ".

Since the sample data of the output variable is represented by a range, the module inspection means 12 compares the output value of the executed module with the sample data indicated by the range. In this case, the user can only determine whether or not the output value is included in the range,
Although it cannot be determined that the module is operating without errors as expected, at least if the output value is not within the range of the sample data, it is possible to determine that the possibility of an error in the module is extremely high. is there. Also,
In the present embodiment, a module having a plurality of input variables is provided on condition that the input variables are independent of each other.

In the module inspection apparatus configured as described above, the number of test cases is determined by the test case number determining means 17 to determine whether or not the number of test cases is insufficient. Then, the test case estimating means 18 creates the required number of test cases based on the existing data specification. Therefore, even when a module includes a control structure, a unit test can be performed using a required number of test cases.

[Third Embodiment] FIG. 9 is a block diagram showing a configuration of a module inspection apparatus. In FIG. 9, the same parts as those in the module inspection apparatus described in the first embodiment are denoted by the same reference numerals, and the detailed description of the same parts will be omitted.

The feature of the module inspection apparatus of the present embodiment shown in FIG. 9, which is different from that of the module inspection apparatus described in the first embodiment, is as follows.

That is, the configuration is such that the number-of-corrections detecting means 19 and the retest order creating means 20 are provided.

The number-of-corrections detecting means 19 detects the number of times the module to be inspected has been corrected, and outputs the number of times to the retest order creating means 20 for each module. Here, as the number of corrections, the number of corrections made after the module is inspected by the module inspection means 12 and before the module is inspected again is counted as “1”.
For example, when a unit test is performed on five modules a, b, c, d, and e, the modules c, d, and e are determined to have errors as a result of the inspection performed by the module inspection unit 12. Modify only c, d and e,
If the module e is corrected again when it is determined that there is an error in the module e and the module e is corrected, the number of corrections of the module e is "2" and the number of corrections of the modules c and d is "1". , The number of corrections of the modules a and b is “0”.

The retest order creating means 20 determines the order of module inspection by the module inspection means 12. The retest order creating means 20 determines the module inspection order from the module having the largest number of corrections to the module having the largest number of modifications, starting with the module having the largest number of modifications. Therefore, in the above example, since the number of times of modification of all modules is "0" at first, the module inspection unit 12 inspects the modules in an appropriate order such as the order of module names "abcde". I do. When the modules c, d, and e are corrected based on the inspection result, the number of corrections of the modules c, d, and e becomes “1”, and the number of corrections is input to the retest order creating unit 20. Therefore, the retest order creating means 20 creates an order "cdeab" based on the number of corrections, and the module checking means 12 checks the module again in the order. Then, if only the module e is further corrected based on the inspection result, the number of corrections for the module e becomes “2”. When the number of corrections is input to the retest order creation means 20, the retest order creation means 20
Based on the number of corrections, an order of “ecdab” is created, and the module inspection unit 12 inspects the module again in the order.

In the module inspection apparatus configured as described above, the module having a larger number of corrections is inspected first at the time of inspection. Generally, it is considered that a module having a large number of corrections is likely to contain an error.

Therefore, even if the inspection is interrupted during the inspection by the module inspection means 12, the inspection of the module which has a high possibility of containing an error and has a large number of corrections may already be completed. High in nature. Therefore, there is an advantage that the debugging operation can be performed efficiently.

[0062]

Since the program checking apparatus of the present invention is constructed as described above, according to the first aspect of the present invention, the module specification storing means stores the input variables of the module, the output variables of the module and The module specification describing the specific values of the variables is stored, and the test case creation means creates a test case of the module corresponding to the module specification from the input variables, output variables, and the specific values described in the module specification. Test cases based on the module specifications, even if the programmer mistakenly understands the module specifications and the module is created, without the programmer creating test cases based on their own interpretation. By unit testing, module errors can be found efficiently and debugging There is an effect that it provides a modular inspection apparatus capable of achieving streamlining.

According to the second aspect of the present invention, the test case number determination means compares the control structure of the module to be inspected with the number of test cases for the module, and determines whether the number of test cases is insufficient. Judgment is made and the test case adding means creates additional test cases when there are not enough test cases.Therefore, even if the module contains a control structure, unit test using the required number of test cases And a module inspection device that can detect an error in the module can be provided.

According to the third aspect of the present invention, the data specification storage means sets a specific value to be input to the input variable of the module to be inspected or a range of the specific value to be output to the output variable of the module to be inspected. Since the data specifications shown are stored and the test case adding unit creates the test cases based on the data specifications, even if the module includes a control structure, the necessary number created based on the data specifications is required. This makes it possible to perform a unit test using the test case (1), and to provide a module inspection device capable of detecting module errors.

In the invention according to claim 4, the test case adding means uses a value selected from a specific value range shown in the data specification as a specific value of the input variable, and Since the test cases are additionally created using the specific value range shown in the document, the user cannot determine that the module is operating without errors as expected. When it is out of the range, there is an effect that it is possible to provide a module inspection device that can determine that the possibility of an error in a module is extremely high.

According to the fifth aspect of the present invention, the number-of-corrections detecting means detects the number of times the module has been corrected by the module correcting means, and the re-examination order determining means determines whether or not the module has been re-examined based on the number of corrections. Since the order is determined, even if the inspection is interrupted during the inspection by the module inspection means, the inspection may be already completed for a module having a high number of corrections with a high possibility that the module contains an error. It is possible to provide a module inspection apparatus which has high reliability and can perform a debugging operation efficiently.

[Brief description of the drawings]

FIG. 1 is a block diagram showing one configuration of a module inspection device of the present invention.

FIG. 2 is an explanatory diagram showing an example of a module specification document.

FIG. 3 is an explanatory diagram of contents stored in a test result storage unit.

FIG. 4 is a block diagram showing another configuration of the module inspection device of the present invention.

FIG. 5 is an explanatory diagram of a data specification.

FIG. 6 is an explanatory diagram of a data specification.

FIG. 7 is an explanatory diagram of a data specification.

FIG. 8 is an explanatory diagram of a test case.

FIG. 9 is a block diagram showing another configuration of the module inspection device of the present invention.

FIG. 10 is a block diagram showing a configuration of a conventional module inspection apparatus.

FIG. 11 is an explanatory diagram showing an example of a module to be inspected.

FIG. 12 is an explanatory diagram showing an example of a module specification.

FIG. 13 is an explanatory diagram showing an example of a test case.

[Explanation of symbols]

 8 Module specification document storage means 9 Test case creation means 10 Test case storage means 11 Module storage means 12 Module inspection means 15 Module correction means 16 Data specification storage means 17 Test case number determination means 18 Test case estimation means 19 Correction count detection means 20 Retest order creation means

Claims (5)

[Claims] 1. A module storage means for storing one or a plurality of modules to be tested, a test case storage means for storing test cases indicating specific values of an input variable of each module and an output variable of the module, The specific value of the input variable indicated by the test case is given to the corresponding module to execute the module, and the output value of the execution result of the module is compared with the specific value of the output variable indicated by the test case to match. Module inspection means for sequentially inspecting one or a plurality of modules, the module specification describing module input variables, module output variables and concrete values of these variables. Module specification storage means for storing specifications, input variables and output variables described in the module specifications Module inspection apparatus is characterized by providing a test case creation means for creating a module test cases corresponding to the value in the module specification, a. 2. A test case number determining means for comparing a control structure of a module to be inspected with the number of test cases for the module to determine whether or not the number of test cases is insufficient. A test case adding means for creating additional test cases in case of lack,
The module inspection device according to claim 1, further comprising: 3. A data specification storage means for storing a data specification which indicates a specific value to be input to an input variable of a module to be inspected or a specific value output by an output variable of the module to be inspected, 3. The module inspection apparatus according to claim 2, wherein the test case adding unit creates a test case based on a data specification. 4. The test case adding means uses a value selected from a specific value range shown in a data specification as a specific value of an input variable, and outputs a specific value range shown in a data specification as an output variable. 4. The module inspection apparatus according to claim 3, wherein a test case is additionally created using the test case. 5. A module storage means for storing one or more modules to be inspected, a test case storage means for storing test cases indicating specific values of input variables of each module and output variables of the modules, The specific value of the input variable indicated by the test case is given to the corresponding module to execute the module, and the output value of the execution result of the module is compared with the specific value of the output variable indicated by the test case to match. A module inspection unit that determines whether or not the module is correct, and a module correction unit that allows a user to correct an error in the module based on the determination result of the module inspection unit, and that sequentially inspects one or a plurality of modules. A module specification that describes the input variables of the module, the output variables of the module, and the specific values of these variables. Module specification storage means for storing a specification, test case generation means for generating a test case of a module corresponding to the module specification from input variables, output variables and specific values described in the module specification, and module modification A module inspection apparatus, comprising: a number-of-modifications detecting means for detecting the number of times a module has been modified in the means; and a re-inspection order determining means for determining an order of module re-inspection based on the number of modifications. .