JP6668808B2 - Untested portion detection device, untested portion detection method, and program - Google Patents

Description

  The present invention relates to an untested portion detecting device, an untested portion detecting method, and a program, and more particularly, to an untested portion detecting device, an untested portion detecting device, which detects an untested portion in a processing route executed in operation. The present invention relates to a location detection method and a program.

  Patent Literature 1 discloses a dynamic trace information analysis method capable of reliably tracking a passing route at a branch point.

  Patent Literature 2 discloses a method for automatically measuring test coverage in a normal inspection process without processing a program for testing.

JP-A-2-206847 JP-A-5-282177

  In the case of an important system, a sufficient test is performed for all programs constituting the system, but in the case of a less important system, some processing routes may not be tested.

  Further, a program constituting a system may include processing routes that are assumed not to be used in the system, and the processing routes may not be tested. However, at the time of actual operation, there is a possibility that a program performs an unexpected operation due to timing or an external abnormality, and a processing route on which the program has not been tested is executed.

  Untested processing routes often run correctly and are not necessarily a problem, but untested processing routes can be more buggy than tested processing routes. Is expensive.

  In some cases, the bug is caused by the content of input data and the timing of processing. Therefore, in a system in which a processing route that has not been tested is running, a bug may be more apparent due to a change in input data or processing timing than in a system in which a processing route that has not been tested is not running. high.

  In this connection, as disclosed in Patent Literature 1 and Patent Literature 2, there is known a method of outputting a trace so that the processing route being executed can be known. However, it is not possible to determine whether or not the executed processing route is being tested only by outputting the trace.

  Detecting an untested route among executed processing routes is an important issue in order to predict and prevent a risk of a failure occurring in the system.

  An object of the present invention is to provide an untested portion detecting device, an untested portion detecting method, and a program for solving the above problems.

  According to an embodiment of the present invention, there is provided an untested portion detection device, comprising: an execution unit that executes a program module; a test result storage unit that stores a location identifier indicating a tested location in the program module; When the boot instruction is executed, the boot instruction is activated, the location identifier indicating the insertion location of the boot instruction is acquired, and it is determined whether the acquired location identifier is stored in the test result storage unit. And a test result search means for outputting a judgment result.

  According to one embodiment of the present invention, an untested portion detection method stores a location identifier indicating a tested portion in a program module in a test result storage unit, executes the program module, and determines whether an inserted startup instruction is When executed, a test result search that obtains the position identifier indicating the insertion position of the activation instruction, determines whether the obtained position identifier is stored in the test result storage unit, and outputs a determination result I do.

  According to an embodiment of the present invention, there is provided a program for storing a location identifier indicating a tested location in a program module in a test result storage unit, executing the program module, and executing an inserted startup instruction. And acquiring the location identifier indicating the insertion location of the activation instruction, determining whether the acquired location identifier is stored in the test result storage unit, and outputting a determination result. To run.

  An untested portion detection device according to the present invention detects that an untested processing route is being executed during system operation.

FIG. 1 is a diagram illustrating a configuration of an untested portion detection device 11 and a start command embedding device 10 according to the first embodiment. FIG. 2 is a diagram showing an example of the program source code 100. FIG. 3 is a diagram showing an example of the embedded program source code 101 (func1). FIG. 4 shows an example of data stored in the test result storage file 304. FIG. 5 shows an example of data stored in the log file 305. FIG. 6 is an operation flowchart of the embedding unit 300. FIG. 7 is an operation flowchart of the test result recording unit 302. FIG. 8 is an operation flowchart of the test result search unit 303. FIG. 9 shows an example of the embedded program source code 101 (func1) when a unique area identifier is passed in the untested portion detection device 11 along with the program name and the number of lines in the second embodiment. FIG. FIG. 10 illustrates an example of data stored in the test result storage file 304 according to the second embodiment. FIG. 11 is a diagram illustrating a configuration of the untested portion detection device 11 according to the third embodiment.

<First embodiment>
<Overview>
FIG. 1 is a diagram illustrating a configuration of an untested portion detection device 11 and a start command embedding device 10 according to the first embodiment. The untested portion detection device 11 and the activation command embedding device 10 include the configuration and functions of a computer.

  In the activation instruction embedding device 10, the activation instruction embedding unit 200 includes a code (hereinafter, referred to as a code for activating the embedding unit 300 at a location of a branch or a function call in the source code of the program module 102 operating on the untested location detection device 11). , Start instruction). In the figure, a program source code 100 is a source code of a program module 102. The start command embedding unit 200 embeds a start command in the program source code 100 to generate an embedded program source code 101.

  In the boot instruction embedding device 10, the embedded program source code 101 becomes an executable program module 102 through processing such as compilation.

  The program module 102 is executed by the untested portion detection device 11. At this time, when the route in which the start command is embedded is executed by the program module 102, the start instruction starts the embedding unit 300. At this time, the start command includes information on a location where the start command for starting the embedding unit 300 is embedded in the embedding unit 300, for example, the name of the running program and the start command. Pass the number of rows.

  In the test phase, the embedding unit 300 activated by the program module 102 activates the test result recording unit 302 by passing the program name and the number of lines. The test result recording unit 302 records in the test result storage file 304 that the passed program name and the number of lines have been executed in the test.

  In the operation phase, the embedding unit 300 activated from the program module 102 activates the test result search unit 303 by passing the program name and the number of lines. The test result search unit 303 searches the test result storage file 304 in which the test results are recorded, and determines whether or not the passed program name and the number of lines have already been recorded, that is, whether or not the test at the relevant location has been executed. Confirm whether or not. The test result search unit 303 outputs the name of the program and the number of lines to the log file 305 when the name of the program and the number of lines where the test is not executed.

  As a result, the untested portion detection device 11 checks whether a processing route that has not been tested is not executed during the operation of the program module 102. Such a processing route includes the possibility that another route will be executed and a problem will occur depending on timing or an external abnormality. For this reason, the untested portion detection device 11 can detect one of the signs of a failure that the processing route for which the test is not performed is being executed.

<Structure>
Next, the configuration of an embodiment of the present invention will be described in detail with reference to the drawings.

  Referring to FIG. 1, the system according to the present embodiment includes a start command embedding device 10 and an untested portion detecting device 11. The activation command embedding device 10 generates the program module 102. The untested portion detection device 11 executes the program module 102 in the test phase and the operation phase of the system.

  The boot instruction embedding device 10 includes a first execution unit 201 and a boot instruction embedding unit 200, and generates an embedded program source code 101 and a program module 102 from the program source code 100. The untested portion detection device 11 includes a second execution unit 306, an embedding unit 300, a phase information file 301, a test result recording unit 302, a test result search unit 303, a test result storage file 304, and a log file 305. Execute the module 102.

  The first execution unit 201 and the second execution unit 306 include components that perform standard functions as a computer. The first execution unit 201 and the second execution unit 306 include, for example, a processor, a memory, a compiler, and an OS (Operating System).

  The program source code 100 is a source code for generating a program module 102 that operates in the system. FIG. 2 is a diagram showing an example of the program source code 100.

  The embedded program source code 101 is a source code in which a code for activating the embedding unit 300 created by the activation instruction embedding unit 200 is embedded.

  The start instruction embedding unit 200 embeds a start instruction for activating the embedding unit 300 in the program source code 100, and generates an embedded program source code 101. The activation command embedding unit 200 generates a code for activating the embedding unit 300 so as to pass the program name and the number of lines to be activated to the embedding unit 300.

  FIG. 3 is a diagram showing an example of the embedded program source code 101 (func1). In the example of FIG. 3, in the embedded program source code 101, a start instruction is embedded at a start point of a branch instruction and at two end points after the branch. In this example, the embedding unit 300 is implemented in the form of a subroutine, and the activation instruction is shown as an instruction “routine” for calling the subroutine. FIG. 3 shows that the start instruction “routine” further includes, in the embedding unit 300, the program name (func1) including the start instruction and the number of lines (2, 4, 7) in which the start instruction is embedded in the program. An example of a description passed as a parameter is shown.

  The program module 102 is a module generated from the embedded program source code 101 by the first execution unit 201. For example, a processor of the first execution unit 201 executes a compiler to generate a program module 102 from the embedded program source code 101.

  The program module 102 is an execution module of a program that operates on the untested portion detection device 11.

  The program module 102 generated by the boot command embedding device 10 is copied to the untested portion detection device 11 and operates. In the untested portion detection device 11, the program module 102 is executed by the second execution unit 306. For example, the program module 102 is stored in the memory of the second execution unit 306, and is executed by the processor.

  When the program module 102 is executed and the control reaches a location where the start command is embedded, the start command embedded in the embedded program source code 101 is executed, and the embedding unit 300 is started.

  The embedding unit 300 is started from the program module 102 by passing the program name and the number of lines. When activated, the embedding unit 300 first refers to the phase information file 301. The embedding unit 300 starts the test result recording unit 302 by passing the program name and the number of lines in the test phase, and starts the test result search unit 303 by passing the program name and the number of lines in the operation phase. I do.

  The phase information file 301 stores information indicating whether the program module 102 is operating in the test phase or the operation phase of the system. This information is set, for example, by the operation manager when the untested portion detection device 11 is started.

  The test result recording unit 302 records the program name and the number of lines passed from the embedding unit 300 in the test result storage file 304.

  The test result search unit 303 searches whether the program name and the number of lines passed from the embedding unit 300 are recorded in the test result storage file 304, and outputs a search result. If the program name and the number of lines are not recorded in the test result storage file 304, the test result search unit 303 determines that the program name and the number of lines passed from the embedding unit 300 have not been tested. Then, the program name and the number of lines are output to the log file 305. The test result search unit 303 may store the search results in a memory and output the search results to a console device (not shown) later.

  In the test result storage file 304, information on a place where a test is performed in the program module 102, for example, a program name and the number of lines in the program are recorded. FIG. 4 shows an example of data stored in the test result storage file 304. FIG. 4 shows that, for example, in the program module 102, the second line of the function func1 is being tested.

  The log file 305 records information of a part of the program module 102 that did not operate in the test phase but operated in the operation phase, for example, a program name and the number of lines. FIG. 5 shows an example of data stored in the log file 305. FIG. 5 shows, for example, that the seventh line of the function func1 has been executed in the operation phase even though it has not been tested.

  The start command embedding unit 200 of the start command embedding device 10 is configured by a logic circuit. The start command embedding unit 200 may be realized by a program executed by the first execution unit 201. That is, the start command embedding unit 200 may be realized by a program stored in a memory in the first execution unit 201 and executed by the processor.

  The embedding unit 300, the test result recording unit 302, and the test result search unit 303 of the untested portion detection device 11 are configured by logic circuits. The embedding unit 300, the test result recording unit 302, and the test result search unit 303 may be realized by a program executed by the second execution unit 306. That is, the test result recording unit 302 and the test result search unit 303 may be realized by a program stored in the memory in the second execution unit 306 and executed by the processor.

  The phase information file 301, the test result storage file 304, and the log file 305 are disk devices included in the untested location detection device 11.

<Operation>
Next, the operation of the untested portion detecting device 11 of the present embodiment will be described in detail with reference to the flowcharts of FIGS.

  FIG. 6 is an operation flowchart of the embedding unit 300.

  First, when the embedding unit 300 is started from the program module 102, the embedding unit 300 refers to the phase information file 301 and checks whether the system is operating in the test phase or the operation phase of the system (see FIG. 6). Step 1). In the test phase, the embedding unit 300 activates the test result recording unit 302 by passing the program name and the number of lines passed from the program module 102 (step 2). In the operation phase, the embedding unit 300 starts the test result search unit 303 by passing the program name and the number of lines passed from the program module 102 (Step 3).

  FIG. 7 is an operation flowchart of the test result recording unit 302.

  The test result recording unit 302 searches whether or not the program name and the number of lines passed from the embedding unit 300 are recorded in the test result storage file 304 (Step 11 in FIG. 7). If the program name and the number of lines have not been recorded, the test result recording unit 302 records the program name and the number of lines in the test result storage file 304 (Step 2).

  FIG. 8 is an operation flowchart of the test result search unit 303.

  The test result search unit 303 searches whether or not the program name and the number of lines passed from the embedding unit 300 are recorded in the test result storage file 304 (Step 21 in FIG. 8). If not recorded, the test result search unit 303 records the program name and the number of lines in the log file 305 (Step 22 in FIG. 8).

<Modification>
The untested portion detection device 11 may be configured integrally with the activation command embedding device 10. That is, the untested portion detection device 11 may also include the activation command embedding unit 200.

  For example, at the time of initial setting, the untested portion detection device 11 may read information of the test result storage file 304 into a memory in advance. Then, the test result recording unit 302 and the test result search unit 303 may be configured to search the memory at the time of search, thereby speeding up the search process.

  The data of the test result storage file 304 may be manually stored by the test executor. In that case, the start command embedded in the program module 102 may directly start the test result search unit 303, and the embedded unit 300 may not be provided.

<Effect>
The first effect is that the untested portion detection device 11 can detect during operation that a processing route that did not operate in the test operated during operation of the system. The reason is that the test result search unit 303 refers to the test result storage file 304 and determines during the operation of the system whether or not the processing route has been operated in the test.

  The second effect is that the amount of output to the log file 305 can be reduced. The reason is that the test result search unit 303 outputs only the trace of the processing route that did not operate in the test to the log file 305.

<Second embodiment>
In the first embodiment, the location information passed from the program module 102 to the embedding unit 300 is the program name and the number of lines. The program module 102 may be configured to pass, to the embedding unit 300, a unique area identifier in the untested portion detection device 11 instead of the program name and the number of lines. Further, the program module 102 may be configured to pass a unique area identifier in the untested portion detection device 11 along with the program name and the number of lines to the embedding unit 300.

  FIG. 9 is a diagram showing an example of the embedded program source code 101 (func1) when a unique area identifier is passed in the untested portion detection device 11 along with the program name and the number of lines. In the example of FIG. 9, in the embedded program source code 101, a start instruction is embedded at a start point of a branch instruction and at two end points after the branch. In this example, the embedding unit 300 is implemented in the form of a subroutine, and the activation instruction is shown as an instruction “routine” for calling the subroutine.

  FIG. 9 further shows a program name (func1) including a start instruction, the number of lines (2, 4, 7) in which the start instruction is embedded in the program, and a unique area in the untested portion detection device 11. An example of description of parameters when passing another (1,2,3) to the embedding unit 300 is shown.

  In this case, the test result recording unit 302 may record, in the test result storage file 304, whether or not the test has been performed for each unique identifier, instead of the program name and the number of lines.

  FIG. 10 illustrates an example of data stored in the test result storage file 304 according to the second embodiment. FIG. 10 shows that, for example, a place where a start instruction having the identifier 1 as a parameter is embedded in the program module 102 is tested. On the other hand, FIG. 10 shows that the place where the start instruction having the identifier 2 as a parameter is embedded is not tested.

  The untested portion detection device 11 of the present embodiment can speed up the processing of the test result recording unit 302 and the test result search unit 303. The reason is that the test result recording unit 302 and the test result search unit 303 can immediately acquire information as to whether or not the test has been performed by using the unique identifier as an index.

<Third embodiment>
FIG. 11 is a diagram illustrating a configuration of the untested portion detection device 11 according to the third embodiment. The untested portion detection device 11 includes a second execution unit 306, a test result storage unit 307, and a test result search unit 303.

  The second execution unit 306 executes the program module 102.

  The test result storage unit 307 stores a location identifier indicating a tested location in the program module 102. The test result storage unit 307 may be the test result storage file 304 or another file. The test result storage unit 307 may be, for example, a device that collects data via a network.

  When the start command inserted into the program module 102 is executed, the test result search unit 303 acquires a location identifier indicating a location where the start instruction is inserted, and the acquired location identifier is stored in the test result storage unit 307. Is determined, and a determination result is output.

  The effect of the present embodiment is that the untested portion detection device 11 can detect during operation that a processing route that did not operate in the test operated during operation of the system. The reason is that the test result search unit 303 uses the test result storage unit 307 to determine during the operation of the system whether or not the processing route has been operated in the test.

  Although the present invention has been described with reference to the exemplary embodiments, the present invention is not limited to the above exemplary embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

DESCRIPTION OF SYMBOLS 10 Start-up instruction embedding apparatus 11 Untested part detection apparatus 100 Program source code 101 Embedded program source code 102 Program module 200 Start-up instruction embedding part 201 First execution part 300 Embedding part 301 Phase information file 302 Test result recording part 303 Test result Search unit 304 Test result storage file 305 Log file 306 Second execution unit 307 Test result storage unit

Claims (8)

Execution means for executing the program module;
Test result storage means for storing a location identifier indicating a tested location in the program module,
The program module is started when a start command inserted in the program module is executed, and determines whether the program module is in operation or under test. If the apparatus is in operation, the test result search unit is started. An embedding means for activating the means;
Activated from the embedding unit , obtain the location identifier indicating the insertion location of the activation command , determine whether the acquired location identifier is stored in the test result storage unit, and output a determination result. The test result search means;
The test result recording unit, which is activated from the embedding unit, acquires the location identifier indicating the insertion location of the activation instruction, and records the acquired location identifier in the test result storage unit.
An untested portion detection device comprising: Further comprising a log storage means,
2. The untested location detecting apparatus according to claim 1, wherein the test result search unit outputs a log to the log storage unit when the acquired location identifier is not stored in the test result storage unit. The program module may output to the embedding means when the activation command is executed and the routine name of the routine to which the activation instruction is embedded, the line number of the source code in the routine as an input parameter, said embedding means, 3. The untested portion detecting device according to claim 1, wherein the routine name and the line number are input to the test result recording unit and the test result searching unit as the location identifier indicating a location where the activation instruction is inserted. 4. The method according to claim 3 , further comprising a start instruction embedding unit that inputs the source code of the program module, and embeds the start instruction in which the routine name and the line number are specified as input parameters in the source code of the program module. Untested location detector. The program module outputs the unique identifier in the program module as an input parameter to the embedding unit when the start instruction is executed, and the embedding unit indicates the unique identifier indicating a place where the start instruction is inserted. the test result recording means as said position identifier, and the test input to the search results means, untested point detecting device of any one of claims 1 to 4. A location identifier indicating a tested location in the program module is stored in the test result storage means,
When the program module is executed and a start instruction inserted in the program module is executed, it is determined whether the program is in operation or under test. An identifier is obtained, a determination is made as to whether the obtained location identifier is stored in the test result storage means, a test result search for outputting a determination result is performed , and if a test is being performed , the insertion location of the start instruction is determined. An untested part detection method , comprising: obtaining the part identifier indicating the following; and recording the obtained part identifier in the test result storage means . 7. The method according to claim 6 , wherein a log is output when the acquired location identifier is not stored in the test result storage unit. An execution process for executing the program module;
A test result storing process of storing the location identifier indicating the tested points in the program module to the test result storage means,
When the start instruction inserted in the program module is executed, it is determined whether the operation is being performed or the test is being performed. If the operation is being performed, the test result search process is performed. If the test is being performed, the test result recording process is performed. Processing,
Acquires the location identifier indicating the insertion position of those said activation command, it is determined whether or not the location identifier obtained is stored in the test result storing means, and outputs the determination result, and the test results search process ,
Acquiring the location identifier indicating the insertion location of the activation instruction, recording the acquired location identifier in the test result storage means, the test result recording process,
A program that causes a computer to execute.

Images