KR20240169464A - Method and apparaus for displaying the result of unit test and code coverage - Google Patents

Abstract

A test result display method according to the present invention includes a receiving step of receiving a unit test execution result from a unit test execution device, a first merging step of merging test case execution results for each test unit based on the unit test execution result, a second merging step of merging code coverage results for each test unit, and a display step of displaying the merged test case execution result and the merged code coverage result. According to this, the test results of each software unit can be merged in real time on a team testing server and checked on a dashboard. In addition, an integrity check is performed to check whether a test target and a test case are performed under the same conditions, thereby ensuring the integrity of the test result.

Description

METHOD AND APPARAUS FOR DISPLAYING THE RESULT OF UNIT TEST AND CODE COVERAGE

The present invention relates to the field of software development and testing, and more particularly, to a method and device for merging and displaying individual unit test results and code coverage results in real time in large-scale software development.

In the software development process, unit testing is essential to ensure software quality. Multiple developers or testers create and run unit tests for each development or target. However, it can be difficult to check the overall test results of such software. Most systems are configured to manage unit tests written by each developer or tester in a configuration management server through a version control system such as GIT or SVN, and to perform all tests in batches in a continuous integration environment.

There are several problems with this conventional test configuration. First, each test that has been executed more than once must be re-executed on the server, which wastes resources due to unnecessary re-execution. Second, if regression testing is performed daily, the test results of the entire software can be confirmed only after a day. Here, the test results are success/failure/error and code coverage. Code coverage is the result obtained when a test is performed, and it represents information about which code the test performed. Code coverage is a measure used to measure the quality of software testing, and means the ratio of the source code of a program that has been tested, and is usually expressed as a percentage.

In other words, the current method of checking the overall results through batch execution has the problem of wasting resources and delaying result confirmation, and a way to solve this needs to be sought.

Korean Patent Publication No. 10-2165037 (registered on October 6, 2020)

The present invention has been made in consideration of the above-described problems, and an object of the present invention is to provide a method and device capable of merging and displaying unit test and code coverage results in real time during software development.

A test result display method according to the present invention for achieving the above object includes: a receiving step for receiving a unit test execution result from a unit test execution device; a first merging step for merging test case execution results for each test unit based on the unit test execution result; a second merging step for merging code coverage results for each test unit; and a display step for displaying the merged test case execution result and the merged code coverage result.

And, it may further include an integrity judgment step for judging whether the results to be merged in the first merging step and the second merging step are derived from the same test subject.

Additionally, the integrity judgment step can judge integrity based on whether test subject information received from one unit test execution device matches test subject information received from another unit test execution device.

In addition, the integrity judgment step can judge integrity based on whether the hash value of the test subject information received from each unit test execution device matches the hash value obtained from a separate configuration management system.

Additionally, the test case execution result may include success/failure/error status and test target information.

Additionally, the second merge step can merge the syntax, branch, MC/DC coverage, function and function call coverage for each test target unit.

Meanwhile, a test result display device according to the present invention for achieving the above purpose includes: a test result receiving module for receiving a unit test execution result from a unit test performing device; a first merging module for merging test case execution results for each test unit based on the unit test execution result; a second merging module for merging code coverage results for each test unit; and a display module for displaying the merged test case execution result and the merged code coverage result.

And, it may further include an integrity check module that determines whether the results to be merged in the first merge module and the second merge module are derived from the same test subject.

Additionally, the integrity check module can determine integrity based on whether test subject information received from one unit test execution device matches test subject information received from another unit test execution device.

In addition, the integrity check module can determine integrity based on whether the hash value of the test subject information received from each unit test execution device matches the hash value obtained from a separate configuration management system.

Additionally, if the target information or the hash value matches, the test result can be approved, and if the target information or the hash value does not match, the received unit test execution result can be deleted.

Additionally, the test case execution result may include success/failure/error status and test target information.

Additionally, the second merge module can merge syntax, branch, MC/DC coverage, function and function call coverage for each test target unit.

Additionally, the display module can be installed on the dashboard.

According to the method of the present invention, unit test and code coverage results can be merged and displayed in real time during software development.

Figure 1 is a flowchart illustrating a method for displaying unit test and code coverage results according to the present invention.
FIG. 2 is a flowchart showing an integrity check step in a method for displaying unit test and code coverage results according to the present invention.
FIG. 3 is a block diagram showing the configuration of a display device for unit testing and code coverage results according to the present invention.
Figure 4 is a detailed configuration diagram of a display system for unit testing and code coverage results according to the present invention.

The detailed description of the present invention set forth below refers to the accompanying drawings, which illustrate specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the invention, while different from each other, are not necessarily mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention with respect to one embodiment. It should also be understood that the positions or arrangements of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the detailed description set forth below is not intended to be limiting, and the scope of the invention is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled, if appropriately described. Like reference numerals in the drawings designate the same or similar functions throughout the several aspects.

Figure 1 is a flowchart illustrating a method for displaying unit test and code coverage results according to the present invention.

A method for displaying unit test and code coverage results according to the present invention allows test results of each unit for software to be merged in real time on a team testing server and checked on a dashboard, and includes each step of FIG. 1.

First, the unit test execution result is received from the unit test execution device (S110). The unit test execution device may be a terminal of each developer or tester. The terminal may be implemented in various forms such as a PC (Personal Computer), a notebook, a laptop, a tablet PC, etc., and is not limited to a specific terminal.

When the team testing server receives the unit test results executed in each unit test execution device, it merges the test case execution results for each test unit based on the unit test execution results (S120). Specifically, the team testing server calculates the sum of the test case execution results for each test unit. This is called the first merging step. Here, the test case execution results may include success/failure/error status and test target information.

And, the team testing server merges the code coverage results for each test unit (S130). Specifically, the team testing server merges the code coverage results using a separate code coverage merge module. This is called the second merge step. The second merge step can merge the syntax, branch, MC/DC coverage, function, and function call coverage for each test target unit.

The first and second merge steps may be performed at different times or simultaneously.

Finally, the merged test case execution results and the merged code coverage results are displayed (S140). That is, the results of the first merge step and the results of the second merge step are output on the dashboard, allowing the user to check them in real time.

Fig. 2 is a flowchart showing an integrity check step in a method for displaying unit test and code coverage results according to the present invention. Steps S210 and S220 of Fig. 2 correspond to steps S110 and S120/S130 of Fig. 1, respectively, and therefore, redundant description is omitted.

In Fig. 2, after the first merge step and the second merge step are performed, an integrity verification step is further performed. That is, an integrity judgment step for determining whether the results to be merged in the first and second merge steps are derived from the same test subject can be further performed.

The integrity judgment step can judge integrity based on whether test subject information received from one unit test execution device matches test subject information received from another unit test execution device.

In addition, the integrity judgment step can judge integrity based on whether the hash value of the test subject information received from each unit test execution device matches the hash value obtained from a separate configuration management system.

As a result of the integrity judgment, if it is determined that integrity is recognized, the test result is approved (S230), and if it is determined that integrity is not recognized, the test result is deleted (S240).

According to the present invention, the test results of each software unit are merged in real time on the team testing server and can be checked on the dashboard. Specifically, unit tests are executed on the PC of each developer or tester, and the test results of each PC are transmitted to the team testing server. The team testing server calculates the sum of the test case execution results for each test unit, and also merges the code coverage results through a separate code coverage merge module. The merged test and code coverage results are displayed on the dashboard in real time. In addition, an integrity check is performed to check whether the test target and the test case were performed under the same conditions, thereby ensuring the integrity of the test results.

The system includes a team testing server, a separate calculation and merge module included in the team testing server, and a dashboard. The dashboard displays the merged test results, the sum of test case execution results, and the merged code coverage. This will be described in more detail with reference to Figures 3 and 4.

FIG. 3 is a block diagram showing the configuration of a display device for unit testing and code coverage results according to the present invention.

A display device (1000) for unit test and code coverage results according to the present invention includes a test result receiving module (1010), an integrity check module (1020), a first merge module (1030), a second merge module (1040), and a display module (1050). The display device (1000) for unit test and code coverage results according to the present invention may be a team testing server that receives test results from a unit test execution device (1100).

The test result receiving module (1010) receives the unit test execution results from the unit test execution device (1100). Meanwhile, the unit test execution device (1100) may be an individual PC that directly performs the unit test, and includes a test subject information extraction module for integrity check, a test result and code coverage result transmission module, etc.

The first merge module (1030) merges the test case execution results for each test unit based on the unit test execution results. That is, the first merge module (1030) calculates the sum of the test results. The test case execution results may include success/failure/error status and test target information.

The second merge module (1040) merges code coverage results for each test unit. The second merge module (1040) can merge syntax, branch, MC/DC coverage, function, and function call coverage for each test target unit.

The integrity check module (1020) determines whether the results to be merged in the first merge module (1030) and the second merge module (1040) are derived from the same test subject. That is, the integrity check module (1020) checks the integrity from the test subject information. The integrity check module (1020) may be a module that extracts the test subject information from the configuration management system and checks the integrity.

The integrity check module (1020) determines integrity based on whether test subject information received from one unit test execution device matches test subject information received from another unit test execution device.

Additionally, the integrity check module (1020) may determine integrity based on whether the hash value of the test subject information received from each unit test execution device matches the hash value obtained from a separate configuration management system.

At this time, if the target information or the hash value matches, the test result can be approved, and if the target information or the hash value does not match, the received unit test execution result can be deleted.

The display module (1050) displays the merged test case execution results and the merged code coverage results. The display module (1050) is provided in the dashboard, and the user can view the dashboard and understand the test results in real time.

Figure 4 is a detailed configuration diagram of a display system for unit testing and code coverage results according to the present invention.

The system illustrated in Figure 4 merges the test results and code coverage of each unit of software in real time on a team testing server and allows them to be checked on a dashboard. The main operations of this system are as follows.

1. Run unit tests in real time on each developer or tester's PC.

(1) Developers and testers perform unit tests on each test subject and the results are recorded.

(2) Unit test results include information such as success/failure/error status, code coverage, and test target.

(3) Test subject information is extracted from the development environment by the test subject information extraction module for integrity check.

① Test target information includes information such as source code analysis information and file hash values to specify the software component under test.

2. Send test results from each PC to the team testing server

(1) After completing the unit test, the test results and code coverage results are transmitted to the team testing server through the test results and code coverage results transmission module on the individual PC of the developer or tester.

(2) The transmission module transmits test results and code coverage results along with test target information to the team testing server.

3. Calculate the sum of test case execution results for each test unit on the team testing server.

(1) The test result sum calculation module of the team testing server receives test results from each PC and calculates the sum of the test case execution results for each test unit.

4. Merge code coverage results on the team testing server

(1) The team testing server merges code coverage results using a separate code coverage merge module.

(2) The code coverage merge module merges the statement, branch, MC/DC, function, and function call coverage for each unit under test.

(3) In particular, MC/DC coverage uses additional information such as test case results and source code analysis information for each test case when merging.

5. Real-time display of merged test and code coverage results on the dashboard

(1) Merged test results and code coverage results are displayed in real time on the dashboard server.

(2) The dashboard provides an interface where users can view the test results of the entire software, including success/failure/error status and code coverage.

(3) Developers or testers can immediately check the overall software test results.

Meanwhile, to ensure the integrity of the test results, the system checks whether the test results to be merged are derived from the same test subject. Integrity checks are required to ensure that the test subject and test cases are performed under the same conditions.

This system performs integrity checks using the following two methods:

1. Direct reception: A module that checks the integrity of information received from individual PCs.

(1) The team testing server compares the test target information received from each PC with the information received from other PCs to verify integrity.

① If the information matches, approve the test results for further processing (calculate total and merge)

② If the information does not match, delete the test results.

2. Integration with configuration management system: Extract test subject information and check integrity from configuration management system.

(1) Check whether the hash value of the test target information received from each PC matches the hash value obtained from the configuration management system.

① If the information matches, approve the test results for further processing (calculate total and merge)

② If the information does not match, delete the test results.

According to the present invention, the test results of each software unit are merged in real time on the team testing server and can be checked on the dashboard. Specifically, unit tests are executed on the PC of each developer or tester, and the test results of each PC are transmitted to the team testing server. The team testing server calculates the sum of the test case execution results for each test unit, and also merges the code coverage results through a separate code coverage merge module. The merged test and code coverage results are displayed on the dashboard in real time. In addition, an integrity check is performed to check whether the test target and the test case were performed under the same conditions, thereby ensuring the integrity of the test results.

The method for displaying unit test and code coverage results according to the embodiments described above may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable recording medium may include program commands, data files, data structures, etc., alone or in combination. The program commands recorded on the medium may be those specially designed and configured for the present invention or may be those known to and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program commands such as ROMs, RAMs, flash memories, etc. Examples of the program commands include not only machine language codes generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc. The above hardware devices may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

The method of displaying unit test and code coverage results according to the various embodiments described above can also be implemented in the form of a computer program or application executed by a computer and stored in a recording medium.

Although the above has been described focusing on the embodiments, this is only an example and does not limit the present invention, and those with ordinary skill in the art to which the present invention pertains will recognize that various modifications and applications not exemplified above are possible without departing from the essential characteristics of the present embodiments. For example, each component specifically shown in the embodiments can be modified and implemented. In addition, the differences related to such modifications and applications should be interpreted as being included in the scope of the present invention defined in the appended claims.

1000: Display of unit test and code coverage results
1010: Test result receiving module
1020: Integrity Check Module
1030: First Merge Module
1040: 2nd merge module
1050: Display Module
1100: Unit Test Executor

Claims (14)

A receiving step for receiving unit test execution results from a unit test execution device;
A first merging step for merging test case execution results for each test unit based on the above unit test execution results;
A second merge step for merging the code coverage results for each of the above test units; and
A test result display method comprising: a display step for displaying merged test case execution results and merged code coverage results; In the first paragraph,
A test result display method further comprising an integrity judgment step for judging whether the results to be merged in the first merging step and the second merging step are derived from the same test subject. In the second paragraph,
The above integrity judgment step is:
A test result display method that determines integrity based on whether test subject information received from one unit test execution device matches test subject information received from another unit test execution device. In the second paragraph,
The above integrity judgment step is:
A test result display method that determines integrity based on whether the hash value of the test subject information received from each unit test execution device matches the hash value obtained from a separate configuration management system. In the first paragraph,
The above test case execution result is a test result display method including success/failure/error status and test target information. In the first paragraph,
The above second merge step is a test result display method that merges the syntax, branch, MC/DC coverage, function and function call coverage for each test target unit. A test result receiving module that receives unit test execution results from a unit test execution device;
A first merge module that merges test case execution results for each test unit based on the above unit test execution results;
A second merge module that merges the code coverage results for each of the above test units; and
A test result display device including a display module that displays merged test case execution results and merged code coverage results. In Article 7,
A test result display device further comprising an integrity check module that determines whether the results to be merged in the first merge module and the second merge module are derived from the same test subject. In Article 8,
The above integrity check module,
A test result display device that determines integrity based on whether test subject information received from one unit test execution device matches test subject information received from another unit test execution device. In Article 8,
The above integrity check module,
A test result display device that determines integrity based on whether the hash value of the test subject information received from each unit test execution device matches the hash value obtained from a separate configuration management system. In clause 9 or 10,
A test result display device that approves a test result if the target information or the hash value matches, and deletes the received unit test execution result if the target information or the hash value does not match. In Article 7,
The above test case execution results are displayed on a test result display device including success/failure/error status and test subject information. In Article 7,
The above second merge module is a test result display device that merges the syntax, branch, MC/DC coverage, function and function call coverage for each unit under test. In Article 7,
The above display module is a test result display device equipped on the dashboard.

Images