KR102016472B1 - Method and apparatus for measuring code coverage and computer readable recording medium having program the same - Google Patents

Abstract

Code coverage measuring apparatus of the present invention comprises: a source code acquisition unit for acquiring a second source code including a change portion generated by changing at least a portion of the first source code; And a source code processor configured to generate change coverage information by performing a second test on the changed part, wherein the first source code is a code coverage measuring device that is a first test target to generate full coverage information. .

Description

METHOD AND APPARATUS FOR MEASURING CODE COVERAGE AND COMPUTER READABLE RECORDING MEDIUM HAVING PROGRAM THE SAME}

The present invention relates to a method and apparatus for measuring code coverage and a computer readable recording medium having recorded thereon a program for executing the same.

In the related art, a process of checking a test performance of a source code written for verifying a program under development is performed by a user in a program development process.

However, when performing a test on such source code, there is a disadvantage that a lot of time and cost are wasted due to repeated test execution. In particular, even when the modified source code is repeatedly tested in the entire source code, this problem is more highlighted, and the need to perform the test only on the modified part is on the rise.

Code coverage measurement method according to the present invention is to reduce the code coverage measurement time by performing a test only for the changed source code.

In addition, by transmitting the output source code information or coverage information to the outside through the communication unit, the external user can monitor the test performance or the measurement of the source code in real time, and can easily check the result.

In addition, the code coverage measuring apparatus 200 of the present invention automatically measures the coverage without the user's intervention, so that the user concentrates only on test execution.

And, it aims to perform the test efficiently by using the configuration management tool.

The apparatus for measuring code coverage according to the present invention changes to a source code acquisition unit for acquiring a second source code including a change portion generated by changing at least one portion of the first source code, and performing a second test on the change portion. A source code processor for generating coverage information; And the first source code is a code coverage measurement device that is a first test target to generate full coverage information.

According to the code coverage measurement method according to the present invention, since the code coverage test part does not need to be tested again, there is an advantage of reducing the code coverage measurement time of the source code.

In addition, by transmitting the output source code information or coverage information to the outside through the communication unit, an external user can monitor the test performance or measurement of the source code in real time, and can easily check the result.

In addition, the code coverage measuring apparatus 200 of the present invention automatically measures the coverage without the user's intervention, so that the user can concentrate on only performing the test.

In addition, the configuration management tool can be used to perform the test efficiently.

1 is a view of the first source code and the second source code implemented in the code coverage measurement apparatus 200 according to an embodiment of the present invention.
2 is a block diagram of a code coverage measurement apparatus 200 according to an embodiment of the present invention.
3 is a flowchart of a method for measuring code coverage according to an embodiment of the present invention.
4 and 5 are diagrams for explaining the overall coverage information and the change coverage information according to an embodiment of the present invention.
FIG. 6A illustrates a result of function coverage derivation due to performing an iterative test. FIG.
6B is a diagram of a shape module 610 generated through a build process for compiling source code and making an application in a user interface environment.
FIG. 6C illustrates a test performance result for an application including a plurality of shape modules 610.
7 is a diagram of a data transmission / reception system with an external device of the code coverage measuring device 200.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, detailed descriptions of preferred embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that reference numerals and like elements among the drawings are denoted by the same reference numerals as much as possible even if they are shown in different drawings. For reference, in the following description of the present invention, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. Hereinafter, a method of measuring code coverage according to an embodiment of the present invention will be described with reference to the accompanying drawings.

1 is a diagram of a first source code and a second source code performed by the code coverage measuring apparatus 200 according to an embodiment of the present invention.

Code coverage measurement apparatus 200 according to an embodiment of the present invention is a device installed with a program such as LDRA, VectorCAST, CodeScroll Controller Tester for measuring code coverage (code coverage). In addition, the code coverage measuring apparatus 200 is a device which is driven by a predetermined operating system and which can install and edit software, and includes predetermined program modules or hardware. Any device having a memory unit and a microprocessor can be used as the code coverage measuring apparatus 200 according to an exemplary embodiment of the present invention.

Code coverage is one of the indicators of how good a test is when discussing a test of software. In other words, how much of the code itself was executed when testing software. Therefore, as a result of the test, the execution part and the non-execution part may be included, and the execution part of the entire code is defined as code coverage. In particular, according to an embodiment of the present invention, the code coverage may include full coverage information, which is execution rate information for the entire code, and change coverage information, which is execution rate information for the changed part.

The first source code shown in FIG. 1 is an initial test target for deriving entire coverage information, and the second source code is a target for retesting for deriving change coverage information based on a changed portion of the first source code. May be code. Here, the first source code includes at least one function, and some of the functions (function c, function d) are changed to generate a change part, and the second source code includes the change part. The first function illustrated in FIG. 1 is a target function that can be modified by forming a part of the first source code, and the second function may be a separate function added to the first function or a function in which at least a part of the first function is changed. .

The entire coverage information may be derived by first performing a test on the first source code, and the change coverage information may be derived by performing a test on the second source code again.

2 is a block diagram of a code coverage measurement apparatus 200 according to an embodiment of the present invention.

Code coverage measurement apparatus 200 according to an embodiment of the present invention may include a source code acquisition unit 210, a source code reading unit 220 and a source code processing unit 230.

The source code acquisition unit 210 acquires a second source code including a change portion generated by changing at least one portion of the first source code. Here, the first source code is a first test target for deriving total coverage information, and the second source code is a second test target for deriving change coverage information based on a changed part in the first source code. May be code.

The source code reading unit 220 compares the first source code with the second source code, and reads the changed portion of the second source code. Specifically, the generation of the changed part may be read by comparing at least one function included in the first source code with at least one function included in the second source code.

When the source code processor 230 determines that the second source code includes the changed part, the source code processor 230 performs the test on the changed part to generate the change coverage information.

3 is a flowchart illustrating a code coverage measurement method according to an embodiment of the present invention.

As shown in FIG. 3, the source code acquisition unit 210 according to an embodiment of the present invention may acquire a second source code (S301). The second source code of the present invention may include a change portion generated by changing at least one portion of the first source code.

According to an exemplary embodiment of the present invention, the first source code is a first test target for deriving total coverage information, and the second source code is for deriving change coverage information based on a changed part of the first source code. It may be a code to be subjected to the second test. In this case, the first source code may be a code that first performs a first test (preliminary test) or a code that has not undergone the first test, and generates full / change coverage information according to whether the first source code is tested. This will be described later with reference to FIG. 3. In this case, the first test may be defined as a test for the first source code, and the second test may be defined as a test for the second source code.

Meanwhile, the first source code of the present invention is a code acquired by the code coverage measuring apparatus 200 to perform a test, and may be a code previously stored in the code coverage measuring apparatus 200 or a code acquired from external devices 710 and 720. have. For example, the first external device 710 according to the embodiment of the present invention may include a server or a terminal (eg, a mobile terminal such as a pc or a smartphone or a tablet pc) as an apparatus for operating a shape management tool. The second external device 720 may be a device for changing the first source code, and may include a developer PC and a mobile terminal. Accordingly, the first source code may be acquired by the first external device 710 and changed through the second external device 720, or may be acquired and changed by the second external device 720. A detailed description thereof will be described later with reference to FIG. 7.

On the other hand, the second source code includes a change portion generated by changing at least a portion of the first source code, the source code reading unit 220 according to an embodiment of the present invention is at least included in the first source code The generation of the changed part may be read by comparing one function with at least one function included in the second source code. (S302, S303) For example, the function included in the first source code and the second source code may be read. The functions included in each function can be compared in a one-to-one correspondence, and the signature (function name, parameter type, order, etc.) of each function can be read to determine whether a change portion is generated in the second source code. Can be. That is, the generation of the changed part may be determined by comparing the function name of the second function and the function name of the first function one by one.

At this time, a second function in which a part of the first function included in at least a portion of the first source code illustrated in FIG. 1 is changed (C-> C ') is generated, or a new separate second in addition to the first function. If the function (E) is generated, the source code reading unit 220 is a change (C ') or added to the function (E), the change portion is generated in the second source code to be subjected to the second test You can judge.

For example, as shown in FIG. 4, when at least a portion of the first source code of FIG. 4A is changed to generate a changed portion as shown in FIG. 4B, the source code reading unit 220 may perform the function foo (FIG. 4B). ) And the function foo () of FIG. 4A can be compared with each other to determine the change of some source code, thereby determining the generation of the change part. Similarly, the source code reading unit 220 compares the function hoo () of FIG. 4B with the source code of FIG. 4A and adds a new function hoo (), and may determine the generation of the changed part.

As a result of the determination by the source code reading unit 220, when it is determined that the second source code includes the changed part, the source code processing unit 230 may perform a test on the changed part (S304). According to an embodiment of the present invention, the test may be performed only on the changed part, and the additional test may not be performed on the remaining unchanged code part. In addition, the source code processor 230 may determine whether there is a grammatical error in the changed part when performing a test on the changed part of the second source code. For example, by checking the punctuation marks, such as colon and semicolon included in the changed source code, the grammatical error of the changed part can be checked, and if there is no grammatical error, the test execution can be continued.

In addition, when testing a change part, source code may be executed in real time on a virtual machine to derive coverage information. Such a virtual machine may be a virtual machine suitable for a language (eg, c, c ++, java, etc.) of a program including source code. In addition, the result of the execution of the virtual machine may be output on the web and provided to the user.

In the case of one embodiment of the present invention, by performing the test only for the changed part, it is possible to reduce the inconvenience caused by unnecessary test execution, it is possible to reduce the cost required to perform the test.

Meanwhile, the source code processor 230 may generate change coverage information by performing a test on the changed portion (S305). The change coverage information according to an embodiment of the present invention may include change function information or change line information, the change function information may be execution ratio information of a second function, and the change line information is included in the second function. It may be execution rate information of a line. In this case, a function is a module for defining a function of source code by configuring a programming language such as c, c ++, JAVA, and the like. As shown in FIG. Can be defined as the same module. In addition, the coding line is a string unit of the source code included in each of these functions, and each string may be interpreted by a parser, and 134 to 184 illustrated in FIG. 5 may be defined as coding lines in string units. Can be.

The above-described change function information is information on the execution ratio of the second function, and information on the execution ratio of the second function may mean information on the number of the second functions actually executed among the total number of the second functions by performing the test. In addition, the change line information is execution rate information of the coding line included in the second function, and the information about the execution rate of the coding line means information of lines actually executed among the coding lines constituting the second function by performing a test. can do. That is, when the test is performed, all of the source codes to be tested may not be executed, and the information on the actual executed source code among the change information may be confirmed through the change coverage information.

For example, FIG. 5 is a second source code including a change part, and illustrates that the void calculateEmptyBlock function is a second function. In the test performed in FIG. 5A, all of the second function, calculate calculateEmptyBlock, is executed. In FIG. 5B, the change function information (change function coverage) may represent 100%. FIG. 5B is an example of coverage information according to an embodiment of the present invention. In FIG. 5A, lines actually executed among the total number of coding lines 149 to 166 included in the second function of FIG. 5A are changed line information (change line coverage). 72.73%. More specifically, the coding lines 149 to 166 included in the second function include an area to be tested and an empty area not to be tested, and 11 of the 17 coding lines except for 6, which are empty areas, are tested. A target, 72.73%, can be derived for eight of the actual executed lines except three of the non-executed lines.

5B also shows examples of a plurality of pieces of information included in the overall coverage information for the first source code when the second source code does not include the change portion.

 For example, the function coverage may indicate the ratio of the execution function among the total functions included in the first source code, and the line coverage may indicate the ratio of the executed line among the coding lines included in the entire function. Also, statement coverage is ";" The condition coverage may represent the ratio of execution statements among all statements defined and separated, and the condition coverage may represent the ratio of condition statements executed among all condition statements defined and defined by conditions such as IF, WHILE, FOR, and SWITCH. In addition, the function call coverage may indicate the ratio of the execution function among the functions which are the call subjects, and the entry coverage may indicate the ratio of the execution function among the called functions, that is, the called function.

The second source code and the change coverage information may be output on the web in the form as shown in FIGS. 5A and 5B (S306). The code coverage measurement apparatus 200 of the present invention may transmit the output source code information or coverage information to the outside through a communication unit (not shown) when the wired / wireless network is connected. This allows external users to easily verify the results by monitoring the source code and performing real-time monitoring of coverage measurements.

On the other hand, when the source code reading unit 220 compares at least one function included in the first source code with at least one function included in the second source code, and reads the generation of the changed part, the changed part is not generated. If not, the source code processor 230 may read the entire coverage information or output the entire coverage information by performing a new test according to whether or not the first source code has been previously tested. That is, when the first source code is a code that has already been tested, the entire coverage information stored in the memory unit (not shown) may be loaded (S307 and S308). In this case, the total coverage information is information representing a ratio of the execution code among the entire code of the first source code, and means a plurality of pieces of information included in the entire coverage information of FIG. 5B. On the other hand, when the first source code is a code that has not been tested, new full coverage information may be generated by performing a new test on the first source code. (S310, S311) In the above two cases, the code The coverage measurement apparatus 200 may output the first source code and the entire coverage information as illustrated in FIG. 5B on the web (S309).

In this case, the source code processor 230 may generate a plurality of total coverage information through a plurality of test processes. For example, as shown in FIG. 6A, 40% of the functional coverage (A, B, C, D, and E define functions, respectively, A and E execution of 5) can be derived by performing the first test. The function coverage information of 60% may be derived by performing second and third order tests, respectively, and the respective function coverage information may be accumulated and stored in the memory unit. In addition, when all functions are executed, it may be stored as final function coverage information (100%). In addition, the first test, the second test, and the third test mentioned above may be included in the first test of the present invention described above.

The accumulated function coverage information is stored separately in the memory unit, so that the code coverage measuring apparatus 200 may recall the stored function coverage information at any time. That is, even after the third test is performed, the entire coverage information, which is the result of performing the pre-stored first test, may be loaded after initializing the source code.

In addition, this accumulation is automatically performed by the code coverage measurement apparatus 200 without user intervention, so that the user can concentrate on performing the test.

So far, the generation and output of change coverage information and full coverage information have been described. Hereinafter, an example of using the generated coverage information will be described. FIG. 6B is a diagram of a configuration module 610 generated through a build process for compiling source code and making an application in a user interface environment, and illustrates an example of an application running in an account transfer environment. Shown.

As shown in FIG. 6B, the first application (transfer existing service list) may include each shape module 610, and each shape module 610 may include at least one function. Each shape module 610 executes a test to perform 100% total function to represent 100% of total coverage information. At this time, a new application is generated by changing the source code, and the newly formed second application (transfer new service list) may include the first shape module 620 and the second shape module 630. The first shape module 620 does not need to perform a separate test, and the second shape module 630 includes a source code change part to be retested, thereby requiring a separate test. In particular, in the case of FIG. 6B, a case in which the second shape module 630 is generated by a change of an existing shape module is illustrated, or a case in which a new shape module 630 is generated is illustrated. Specifically, the simple variant shape module 630 generates a 50% code change portion, and tests only about 50%, and the comprehensive variant shape module 630 is a newly formed module. Will be performed.

Meanwhile, each application information and code coverage information including the shape modules are separately stored in the memory unit, so that the code coverage measurement apparatus 200 may recall the pre-stored code coverage information at any time.

As shown in FIG. 6C, in a state in which 100% total function is executed by deriving a test for a first application (version 1) including a plurality of shape modules 610 to derive 100% of total coverage information, full coverage After storing information about 100% of information, the source code can be initialized. Subsequently, a new application is generated by changing the source code, and the newly formed second application (version 2) may include a first shape module 620 and a second shape module 630, which will be described above. As shown. The source code processor 230 may derive new coverage information by performing a new test on the second shape module 630, which may also be stored in the memory unit. In this state, if the user wants to retrieve the entire coverage information previously generated, the code coverage measurement apparatus 200 may retrieve the entire coverage information for the previously stored first application version 1 at any time.

So far, the functional configuration of the code coverage measurement apparatus 200 has been described. Hereinafter, a code coverage measurement system through data transmission / reception with external devices 710 and 720 of the code coverage measurement apparatus 200 will be described.

In particular, according to FIG. 7, it is possible to perform an efficient test using a shape management tool. The shape management tool according to the embodiment of the present invention is a kind of software for registering and managing a plurality of version-specific source codes, detecting a change in registered source code, and re-registering the changed source code. CVS, SVN, Git , GitHub, and the like.

As illustrated in FIG. 7, the first external device 710 may include a server or a terminal (eg, a mobile terminal such as a pc or a smartphone or a tablet pc) as a device for operating a shape management tool. The external device 720 is a device for changing the first source code, and may include a developer PC or a mobile terminal. The code coverage measuring apparatus 200 is a device in which a program for measuring code coverage is installed, and may generate overall coverage information or change coverage information.

Each of the devices 710, 720, and 200 constituting the code coverage measurement system of FIG. 7 may perform data transmission / reception through wired communication or wireless communication such as WIFI or LTE.

Meanwhile, as illustrated in FIG. 7, the first external device 710 registers a first source code, which is a test target for deriving total coverage information, through the shape management tool (S711). The shape management tool may be embedded in the first external device 710. Then, the second external device 720 receives the first source code from the first external device 710 and checks out the first source code, thereby modifying a portion of the first source code to generate a change portion for the first source code. It may be (s721). The code coverage measurement apparatus 200 may acquire a second source code including a change portion from the second external device 720 and generate change coverage information based on the change portion. (S201, s202) Such s201 , step s202 includes steps s301 to s311 described above with reference to FIG. 3.

Meanwhile, the code coverage measuring apparatus 200 transmits the second source code including the full / change coverage information or the changed part to the second external device 720, and the second external device 720 based on the information. The first external device 710 may be requested to confirm and / or approve the source code change portion. In this case, the code coverage measurement apparatus 200 may directly transmit a confirmation and / or approval request to the first external device 710 without passing through the second external device 720.

The first external device 710 may determine whether the second source code achieves the change coverage registration criterion based on the request for confirmation and / or approval of the source code change portion (s712). By comparing the change coverage registration criteria previously stored in the first external device 710 with the change coverage information about the newly acquired second source code, it may be determined whether the change coverage information satisfies a predetermined criterion. When the first external device 710 determines that the change coverage information of the second source code satisfies a predetermined criterion, the first external device 710 may transmit the result information on satisfying the predetermined criterion to the second external device 720. In addition, the second external device 720 receives the result information for satisfying the predetermined reference, and transmits the second source code to the first external device 710, so that the first external device 710 receives the second source code. Register (s713).

The above-described embodiments may be implemented in the form of program instructions that can be executed by various computer components, and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination.

Program instructions recorded on the computer-readable recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in the computer software arts.

Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical recording media such as CD-ROMs, DVDs, and magneto-optical media such as floptical disks. optical media) and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to carry out the process according to the invention, and vice versa.

The embodiments of the present invention have been described above with reference to the accompanying drawings, which are merely exemplary and are not intended to limit the present invention, and those skilled in the art do not depart from the essential characteristics of the present embodiment. It will be appreciated that various modifications and applications which are not illustrated above in the scope are possible. For example, each component specifically shown in embodiment can be modified and implemented. And differences relating to such modifications and applications will have to be construed as being included in the scope of the invention defined in the appended claims. Therefore, the spirit of the present invention should not be limited to the embodiments described above, and all of the equivalents or equivalents of the claims, as well as the claims below, are included in the scope of the spirit of the present invention. I will say.

Claims (8)

Acquiring, by the source code acquiring unit, at least one portion of the first source code, the second source code including a change portion generated by the change;
Generating, by a source code processing unit, change code coverage information by performing a partial test on the changed portion; And
And accumulating and storing, by the source code processing unit, a plurality of total code coverage information generated by repeatedly performing the entire test on the first source code.
How to measure code coverage.
The method of claim 1,
The first source code and the second source code include at least one function,
And a source code reading unit, which compares a function of the first source code with a function of the second source code and reads the generation of the changed part.
The method of claim 2,
The modifying portion includes at least one second function,
If the second function is generated, read that the modified part is generated,
The second function is a separate function added to the first function included in at least a portion of the first source code, or the first function is partially changed,
How to measure code coverage.
The method of claim 3, wherein
The change code coverage information includes change function information,
And the change function information is execution ratio information of the at least one second function generated by performing a test on the changed part.
The method of claim 3, wherein
The change code coverage information includes change line information,
The at least one second function comprises a coding line,
And the change line information is information on an execution ratio of the coding line generated by performing a test on the changed part.
delete The method of claim 1,
And the first source code and / or the second source code are acquired from a configuration management tool for managing change information of the source code.
A computer-readable recording medium for recording a computer program for executing the method according to any one of claims 1 to 5.

Images