CN114416537A - Unit testing method, server, client and storage medium - Google Patents

Abstract

The invention relates to a unit testing method, a server, a client and a storage medium, wherein the method comprises the following steps: responding to a dependency configuration instruction which is sent by a client and aims at a plurality of sub-modules and a parent module, and establishing the dependency relationship between the plurality of sub-modules and the parent module; receiving a unit test request aiming at a sub-module to be tested, which is sent by a client; responding to the unit test request, and determining an associated development code according to the dependency relationship; testing the sub-module to be tested operation unit to obtain code coverage rate; and sending the code coverage rate to the client. In the scheme, the dependency relationship is established between the multiple sub-modules and the parent module, the associated development codes under the parent module and having a calling relationship with the sub-modules to be tested can be determined according to the dependency relationship, and the obtained code coverage rate is the coverage condition of all source codes related to the functions of the sub-modules to be tested, so that the accuracy of code coverage rate test is improved.

Description

A unit testing method, server, client and storage medium

technical field

The invention relates to the field of computer vision, in particular to a unit testing method, a server, a client and a storage medium.

Background technique

Code coverage refers to the degree of coverage of the test code. When doing unit testing, code coverage is often used as a measure of how good the test is.

With the wide application of microservice architecture development technology, a project often contains multiple modules for decomposing management and development. Usually the source code is placed in a module directory, and the unit test code is placed in another module directory, so that only the coverage of the unit test code in the current module directory can be counted, and the unit test code needs to be counted for all Coverage of the source code involving the current module functionality. Therefore, this module isolation can lead to inaccurate code coverage tests.

SUMMARY OF THE INVENTION

The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the first aspect of the present invention proposes a unit testing method, which is applied to a server, and the method includes:

In response to the dependency configuration instruction sent by the client for multiple submodules and the parent module, establishing the dependency relationship between the multiple submodules and the parent module;

receiving a unit test request sent by the client for the submodule to be tested; the submodule to be tested is at least one submodule of the plurality of submodules;

In response to the unit test request, determine the associated development code according to the dependency relationship; the associated development code is the development code that has a calling relationship with the submodule to be tested in the plurality of submodules;

Run a unit test on the submodule to be tested to obtain code coverage; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code;

Send the code coverage to the client.

Optionally, in response to the unit test request, running a unit test on the submodule to be tested includes:

In response to the unit test request, determine a submodule having a calling relationship with the submodule to be tested from the plurality of submodules, and obtain an associated submodule;

Obtain the development code that has a calling relationship with the submodule to be tested from the associated submodule, and obtain the associated development code;

Pull the development code of the submodule to be tested;

Using the unit test code of the submodule to be tested, run a unit test on the development code of the submodule to be tested and the associated development code;

Obtain the coverage rate of the unit test code relative to the development code of the submodule to be tested and the associated development code to obtain the code coverage rate.

Optionally, the pulling the development code of the submodule to be tested includes:

Obtain the pre-configured Git server address corresponding to the development code of the submodule to be tested;

Pull the development code of the submodule to be tested from the Git server address to the local server.

A second aspect of the present invention provides a unit testing method, which is applied to a client, and the method includes:

Receive dependency configuration operations for multiple submodules and parent modules, and generate dependency configuration instructions;

sending the dependency configuration instruction to the server, so that the server establishes the dependencies between the multiple submodules and the parent module;

In response to the unit test request operation for the submodule to be tested, a test request is generated, and the test request is sent to the server; the submodule to be tested is at least one submodule of the plurality of submodules;

Receive the code coverage data sent by the server; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code; the associated development code is one of the multiple submodules The development code that has a calling relationship with the submodule to be tested.

Optionally, before generating the test request in response to the unit test request operation for the submodule to be tested, the method further includes:

In response to the selection operation for the submodule, a submodule to be tested is determined.

Optionally, before determining the submodule to be tested in response to the selection operation for the submodule, it also includes:

A test service configuration operation for the multiple sub-modules is received; the test service configuration operation includes a configuration operation for the test environment, code type, listening port, and Git server address corresponding to the development code.

A third aspect of the present invention provides a server, where the server includes:

a dependency establishment module, used for establishing the dependency relationship between the multiple submodules and the parent module in response to the dependency configuration instructions sent by the client for multiple submodules and the parent module;

a request receiving module, configured to receive a unit test request sent by the client for the submodule to be tested; the submodule to be tested is at least one submodule of the plurality of submodules;

a code determination module, configured to determine an associated development code according to the dependency relationship in response to the unit test request; the associated development code is a development code that has a calling relationship with the submodule to be tested among the plurality of submodules;

A test module, configured to run unit tests on the submodule to be tested to obtain code coverage; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code ;

A sending module, configured to send the code coverage to the client.

Optionally, the test module is specifically used for:

In response to the unit test request, determine a submodule having a calling relationship with the submodule to be tested from the plurality of submodules, and obtain an associated submodule;

Obtain the development code that has a calling relationship with the submodule to be tested from the associated submodule, and obtain the associated development code;

Pull the development code of the submodule to be tested;

Using the unit test code of the submodule to be tested, run a unit test on the development code of the submodule to be tested and the associated development code;

Obtain the coverage rate of the unit test code relative to the development code of the submodule to be tested and the associated development code to obtain the code coverage rate.

Optionally, the test module is specifically used for:

Obtain the pre-configured Git server address corresponding to the development code of the submodule to be tested;

Pull the development code of the submodule to be tested from the Git server address to the local server.

A fourth aspect of the present invention provides a client, where the client includes:

The operation receiving module is used to receive dependency configuration operations for multiple sub-modules and parent modules, and generate dependency configuration instructions;

an instruction sending module, configured to send the dependency configuration instruction to the server, so that the server establishes the dependencies between the multiple submodules and the parent module;

A request sending module, configured to generate a test request in response to a unit test request operation for the submodule to be tested, and send the test request to the server; the submodule to be tested is at least one of the multiple submodules submodule;

A data receiving module for receiving code coverage data sent by the server; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code; the associated development code is The development code in the plurality of submodules that has a calling relationship with the submodule to be tested.

Optionally, the client further includes:

A submodule determination module, configured to determine a submodule to be tested in response to a selection operation for the submodule.

Optionally, the client further includes:

The configuration operation receiving module is configured to receive the test service configuration operation for the multiple submodules; the test service configuration operation includes the configuration operation for the test environment, code type, listening port, and Git server address corresponding to the development code.

A fifth aspect of the present invention provides a computer-readable storage medium, the storage medium stores at least one instruction, at least one piece of program, code set or instruction set, the at least one instruction, the at least one piece of program, the code The set or instruction set is loaded and executed by the processor to implement the unit testing method as described in the first aspect and/or the second aspect.

According to the specific embodiments provided by the present invention, the present invention has the following technical effects:

The unit testing method provided by the embodiment of the present invention establishes the dependency relationship between multiple submodules and the parent module in response to the dependency configuration instruction sent by the client for multiple submodules and the parent module; The unit test request; the submodule to be tested is at least one submodule among the multiple submodules; in response to the unit test request, the associated development code is determined according to the dependency relationship; the associated development code is one of the multiple submodules A development code that has a calling relationship with the submodule to be tested; run a unit test on the submodule to be tested to obtain code coverage; the code coverage is the development code of the unit test code relative to the submodule to be tested and the coverage of the associated development code; send the code coverage to the client. In this solution, multiple submodules have established dependencies with the parent module, and the associated development code under the parent module that has a calling relationship with the submodule to be tested can be determined according to the dependency relationship, and the obtained code coverage is all related to the submodule to be tested. The coverage of the source code of the module function improves the accuracy of the code coverage test.

Additional aspects and advantages of the present invention will be set forth, in part, from the following description, and in part will be apparent from the following description, or may be learned by practice of the invention.

Description of drawings

In order to illustrate the technical solutions of the present invention more clearly, the following will briefly introduce the accompanying drawings that are required to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

1 is a flow chart of steps of a unit testing method provided by an embodiment of the present invention;

2 is a flowchart of steps of another unit testing method provided by an embodiment of the present invention;

3 is a structural block diagram of a server according to an embodiment of the present invention;

FIG. 4 is a structural block diagram of a client according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present invention.

The present specification provides method operation steps as described in the embodiments or flow charts, but more or less operation steps may be included based on routine or non-creative work. When an actual system or server product is executed, it can be executed sequentially or in parallel (for example, in a parallel processor or multi-threaded processing environment) according to the embodiments or the methods shown in the accompanying drawings.

FIG. 1 is a flowchart of steps of a unit testing method provided by an embodiment of the present invention. This method can be applied to the server, including the following steps:

Step 101: In response to a dependency configuration instruction sent by a client for multiple submodules and a parent module, establish a dependency relationship between the multiple submodules and the parent module.

In the embodiment of the present invention, a code coverage test platform is established. In the web client of the platform, the name of the parent module can be input, and a plurality of sub-modules corresponding to the parent module can be configured, and the dependency configuration instruction can be generated through the corresponding control. Client sends to server. After receiving the dependency configuration instruction, the server establishes dependencies between multiple submodules and the parent module.

Step 102: Receive a unit test request sent by the client for the sub-module to be tested; the sub-module to be tested is at least one sub-module of the multiple sub-modules.

The submodule to be tested is selected by the user from multiple submodules on the client side. After the client selects the submodule to be tested, click Generate Unit Test Report to send a unit test request for the submodule to be tested to the server.

Here, at least one sub-module or a combination of all sub-modules can be selected for unit testing, so as to avoid the problem of not being able to select sub-modules to run all tests, resulting in a large running workload, improving testing efficiency and avoiding unnecessary waste of computing resources.

Step 103: In response to the unit test request, determine an associated development code according to the dependency relationship; the associated development code is a development code of the multiple submodules that has a calling relationship with the submodule to be tested.

After receiving the unit test request, the server determines the associated development code corresponding to the submodule to be tested. The associated development code is the development code in the multiple submodules under the parent module that has a calling relationship with the submodule to be tested.

A plurality of submodules all have a dependency relationship with the parent module, so the associated submodule associated with the function of the submodule to be tested can be determined through the dependency relationship, and then the associated development code can be determined from the associated submodule.

For example, the parent module is car rental, and the sub-modules are modules such as login, registration, ordering, car-hailing, settlement, payment, and membership purchase. Each sub-module is a functional module under the parent module. If the sub-module to be tested is a settlement sub-module, the sub-modules associated with the sub-module to be tested include login, order placement, payment and other sub-modules, and the development code associated with the settlement sub-module is obtained from the associated sub-module to obtain the associated development code.

Optionally, in response to the unit test request, running a unit test on the submodule to be tested includes the following steps A1-A5:

A1, in response to the unit test request, determine a submodule that has a calling relationship with the submodule to be tested from the plurality of submodules, and obtain an associated submodule;

A2, obtain the development code that has a calling relationship with the submodule to be tested from the associated submodule, and obtain the associated development code;

A3. Pull the development code of the submodule to be tested;

A4, using the unit test code of the submodule to be tested, run the unit test on the development code of the submodule to be tested and the associated development code;

A5. Obtain the coverage rate of the unit test code relative to the development code of the submodule to be tested and the associated development code to obtain the code coverage rate.

In steps A1-A5, the code coverage describes the proportion and extent of the source code in the program being tested, and the obtained proportion is called the code coverage. Here, the coverage ratio of the unit test code to the development code of the submodule to be tested and the associated development code is taken as the code coverage ratio.

Specifically, after the test runs, the coverage data of the unit test can be obtained by executing the JaCoCo plug-in. JaCoCo (Java Code Coverage, java code coverage) is a widely used java coverage testing tool. It uses the ASM (bytecode engine) library to modify and generate java bytecodes by injecting bytecodes. Thereby recording the execution data of the program, it will not change the behavior of the original code.

Optionally, the pulling of the development code of the submodule to be tested includes the following steps A31-A32:

A31. Obtain a pre-configured Git server address corresponding to the development code of the submodule to be tested;

A32. Pull the development code of the submodule to be tested from the Git server address to the local server.

In steps A31-A32, the user pre-configures the Git server address corresponding to the development code of the submodule to be tested on the client, and when running the test, first pulls the development code of the submodule to be tested from the address to the local server, Only then can test cases and development code be run on the local server.

In addition, the test code can also be stored on the Git server, and the test code can also be pulled from the Git server address to run the test case.

Step 104: Run a unit test on the submodule to be tested to obtain a code coverage; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code.

Unit testing is writing test code to detect specific, unambiguous, fine-grained functionality. Unit testing can be used to ensure the correctness of the current code, and to ensure the correctness of the code in the future when it is fixed, improved or refactored. Coverage refers to the degree of code coverage. A common measure is statement coverage, which is used to measure whether each executable statement in the code under test has been executed, and branch coverage, which is used to measure whether each branch of the program is determined. have been tested, as well as condition coverage, which measures whether each subexpression result in the decision was tested, and function coverage, which measures how many of the defined functions were called.

The code coverage in this embodiment of the present invention may represent at least one of the above coverages.

When running the unit test, not only test the development code of the submodule to be tested, but also test the associated development code. The code coverage obtained in this way is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code. Rate.

Optionally, run unit tests on the development code of the submodule to be tested and the associated development code, including:

A test case is executed on the development code of the submodule to be tested and the associated development code in the local server through moven.

Specifically, the test runner maven-surefire-plugin is used to run test cases. By default, the test target of maven-surefire-plugin will automatically execute all test classes in the test source path that conform to a set of naming patterns.

Step 105: Send the code coverage to the client.

Maven integrates with the open source test coverage testing tool Cobertura through the cobertura-maven-plugin, which can generate code coverage reports for Maven projects with simple commands.

In the embodiment of the present invention, after the user clicks the corresponding option of the client to run the unit test, the server receives the test instruction, automatically executes the pre-written test case, and automatically generates a code coverage report.

The server sends the code coverage report to the client for the user to view and use.

In addition, the email sending class can be automatically written in the test code, so that the email can be automatically sent to the corresponding personnel to visually check the code coverage report.

In the embodiment of the present invention, the unit test multi-module coverage test is combined with the development unit test code and the development code of the module to be tested is compared with the associated development code, which reduces manual verification steps, removes redundant work, improves test work efficiency, and realizes Comparison of unit test coverage; and, the present invention can effectively count the line coverage of functional codes in unit tests, the function coverage in code methods, the code branch coverage and the code statement coverage to quantify the adequacy of the test. . In addition, by running the unit test code in each line of business test, in the detailed report, you can effectively check whether the code coverage involved in the test is covered and whether the core scenario is covered, which is used to ensure the correctness of the current code, code repair, improvement or re-engineering. correctness in the future.

To sum up, the unit testing method provided by the embodiment of the present invention establishes the dependency relationship between multiple submodules and the parent module in response to the dependency configuration instructions sent by the client for multiple submodules and the parent module; The unit test request of the test submodule; the submodule to be tested is at least one submodule of the multiple submodules; in response to the unit test request, the associated development code is determined according to the dependency relationship; the associated development code is the multiple submodules. The development code in the submodules that has a calling relationship with the submodule to be tested; run unit tests on the submodule to be tested to obtain code coverage; the code coverage is the unit test code relative to the submodule to be tested The development code and the coverage of the associated development code; send the code coverage to the client. In this solution, multiple submodules have established dependencies with the parent module, and the associated development code under the parent module that has a calling relationship with the submodule to be tested can be determined according to the dependency relationship, and the obtained code coverage is all related to the submodule to be tested. The coverage of the source code of the module function improves the accuracy of the code coverage test.

FIG. 2 is a flowchart of steps of a unit testing method provided by an embodiment of the present invention. This method can be applied to the client and includes the following steps:

Step 201: Receive dependency configuration operations for multiple submodules and parent modules, and generate dependency configuration instructions.

In the client in the code coverage test platform, you can enter the name of the parent module, and configure multiple submodules corresponding to the parent module, and generate dependency configuration instructions through corresponding controls, which are sent from the client to the server.

Step 202: Send the dependency configuration instruction to the server, so that the server establishes the dependencies between the multiple submodules and the parent module.

After receiving the dependency configuration instruction, the server establishes dependencies between multiple submodules and the parent module. Specifically, configure coverage dependencies under the parent pom file and child pom file corresponding to the development code.

Step 203 , in response to the unit test request operation for the submodule to be tested, generate a test request, and send the test request to the server; the submodule to be tested is at least one submodule of the plurality of submodules.

The submodule to be tested is selected by the user from multiple submodules on the client side. After the client selects the submodule to be tested, click the Generate Unit Test Report option to send a unit test request for the submodule to be tested to the server. .

Step 204: Receive the code coverage data sent by the server; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code; the associated development code is the multiple The development code in each submodule that has a calling relationship with the submodule to be tested.

In the embodiment of the present invention, after the user clicks the corresponding option of the client to run the unit test, the server receives the test instruction, automatically executes the pre-written test case, and automatically generates a code coverage report.

The server sends the code coverage report to the client for the user to view and use.

Through the report, you can not only visually view the unit test coverage data of each submodule, but also check the total unit test coverage data of all submodules. At the same time, the unit test coverage data can be used as the entry threshold for smoke test testing, integrated in the automated construction platform to form an automated quality control system. From the detailed data of the report, we can also check and fill in the gaps for the uncovered code, so as to achieve the full coverage of the test scenario and the improvement of the code coverage. Counting and viewing unit test coverage data of code under multiple modules is the core value embodiment of the entire inventive solution.

First, visually check the unit test coverage code rate under multiple modules. Through the integrated statistical report, you can intuitively see whether the unit test code written by the development and the development function code are completely covered, and whether there are any omissions, thereby effectively improving the code test coverage rate.

Secondly, visually and effectively check whether the unit test code and the development code of the corresponding interface are completely covered. Through multi-module code coverage, the coverage of unit test code and development code can be compared, covering the entire business line process, effectively replacing manual testing in smoke testing, improving test efficiency and improving test quality, so as to visually see the missing code in the business, and then Guarantee product quality.

Again, intuitively and effectively check whether the unit test code and the new code are completely covered. Through the unit test multi-module coverage code rate, the unit test code can be compared with the new code coverage of the development, and the comparison of the new code in the coverage development can avoid the omission of the new code in the testing process.

Optionally, before generating the test request in response to the unit test request operation for the submodule to be tested, the method further includes:

In response to the selection operation for the submodule, a submodule to be tested is determined.

In the embodiment of the present invention, at least one sub-module or a combination of all sub-modules can be selected as the sub-module to be tested on the client page, so as to avoid problems such as the inability to select sub-modules to make all tests run, resulting in a large running workload, etc. Test efficiency and avoid unnecessary waste of computing resources.

Optionally, before determining the submodule to be tested in response to the selection operation for the submodule, it also includes:

A test service configuration operation for the multiple sub-modules is received; the test service configuration operation includes a configuration operation for the test environment, code type, listening port, and Git server address corresponding to the development code.

In this embodiment of the present invention, a configuration operation can be performed on the test service of each submodule on the client page, including configuration operations on the test environment, code type, listening port, and Git server address corresponding to the development code.

Specifically, the test environment refers to the general term for computer hardware, software, network equipment, and historical data necessary to complete the software testing work; the code type refers to the type of development code; the listening port refers to the port corresponding to the server deployed by the development service .

To sum up, in this embodiment of the present invention, a dependency configuration operation for multiple submodules and a parent module is received, and a dependency configuration instruction is generated; the dependency configuration instruction is sent to the server, so that the server establishes dependencies between multiple submodules and the parent module. relationship; in response to the unit test request operation for the submodule to be tested, generate a test request, and send the test request to the server; the submodule to be tested is at least one submodule among multiple submodules; receive the code coverage sent by the server The code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code; the associated development code is the development code of multiple submodules that has a calling relationship with the submodule to be tested. In this solution, multiple submodules have established dependencies with the parent module, and the associated development code under the parent module that has a calling relationship with the submodule to be tested can be determined according to the dependency relationship, and the obtained code coverage is all related to the submodule to be tested. The coverage of the source code of the module function improves the accuracy of the code coverage test.

FIG. 3 is a structural block diagram of a server according to an embodiment of the present invention.

The server 300 includes:

A dependency establishment module 301, configured to establish a dependency relationship between the multiple submodules and the parent module in response to the dependency configuration instructions sent by the client for multiple submodules and the parent module;

A request receiving module 302, configured to receive a unit test request sent by the client for the submodule to be tested; the submodule to be tested is at least one submodule of the multiple submodules;

A code determination module 303, configured to determine the associated development code according to the dependency relationship in response to the unit test request; the associated development code is the development code that has a calling relationship with the submodule to be tested among the multiple submodules ;

A testing module 304, configured to run a unit test on the submodule to be tested to obtain code coverage; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code Rate;

A sending module 305, configured to send the code coverage to the client.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

FIG. 4 is a structural block diagram of a client according to an embodiment of the present invention.

The client 400 includes:

The operation receiving module 401 is used for receiving dependency configuration operations for multiple submodules and parent modules, and generating dependency configuration instructions;

An instruction sending module 402, configured to send the dependency configuration instruction to the server, so that the server establishes the dependency between the multiple submodules and the parent module;

The request sending module 403 is configured to generate a test request in response to a unit test request operation for the submodule to be tested, and send the test request to the server; the submodule to be tested is at least one of the multiple submodules a submodule;

A data receiving module 404, configured to receive code coverage data sent by the server; the code coverage is the coverage of the unit test code relative to the development code of the submodule to be tested and the associated development code; the associated development code Develop code that has a calling relationship with the sub-module to be tested among the multiple sub-modules.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In another embodiment provided by the present invention, there is also provided a device, the device includes a processor and a memory, the memory stores at least one instruction, at least a piece of program, a code set or an instruction set, the at least one One instruction, the at least one piece of program, the code set or the instruction set are loaded and executed by the processor to implement the unit testing method described in the embodiments of the present invention.

In yet another embodiment provided by the present invention, a computer-readable storage medium is also provided, wherein the storage medium stores at least one instruction, at least one piece of program, code set or instruction set, the at least one instruction, all the The at least one piece of program, the code set or the instruction set is loaded and executed by the processor to implement the unit testing method described in the embodiments of the present invention.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), among others.

It should be noted that, in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any relationship between these entities or operations. any such actual relationship or sequence exists. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

Each embodiment in this specification is described in a related manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for related parts, please refer to the partial descriptions of the method embodiments.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims (13)

1. A unit testing method is applied to a server side, and the method comprises the following steps:

responding to a dependency configuration instruction which is sent by a client and aims at a plurality of sub-modules and a parent module, and establishing the dependency relationship between the plurality of sub-modules and the parent module;

receiving a unit test request aiming at a sub-module to be tested, which is sent by the client; the sub-module to be tested is at least one sub-module in the plurality of sub-modules;

responding to the unit test request, and determining an associated development code according to the dependency relationship; the associated development code is a development code which has a calling relationship with the sub-module to be tested in the plurality of sub-modules;

testing the sub-module to be tested operation unit to obtain code coverage rate; the code coverage rate is the coverage rate of the unit test code relative to the development code and the associated development code of the sub-module to be tested;

and sending the code coverage rate to the client.

2. The method of claim 1, wherein said running unit tests on said sub-modules under test in response to said unit test requests comprises:

responding to the unit test request, determining a sub-module having a calling relationship with the sub-module to be tested from the plurality of sub-modules, and obtaining an associated sub-module;

acquiring a development code having a calling relationship with the sub-module to be tested from the association sub-module to obtain an association development code;

pulling the development code of the sub-module to be tested;

utilizing the unit test code of the sub-module to be tested to run a unit test on the development code of the sub-module to be tested and the associated development code;

and acquiring the coverage rate of the unit test code relative to the development code of the sub-module to be tested and the associated development code to obtain the code coverage rate.

3. The method of claim 2, wherein pulling development code for the sub-module under test comprises:

acquiring a preset Git server address corresponding to the development code of the sub-module to be tested;

and pulling the development code of the sub-module to be tested from the Git server address to a local server.

4. A unit testing method is applied to a client side, and comprises the following steps:

receiving a dependent configuration operation aiming at a plurality of sub-modules and a parent module, and generating a dependent configuration instruction;

sending the dependency configuration instruction to a server so that the server establishes a dependency relationship between the plurality of sub-modules and the parent module;

responding to unit test request operation aiming at the sub-modules to be tested, generating a test request, and sending the test request to a server; the sub-module to be tested is at least one sub-module in the plurality of sub-modules;

receiving code coverage rate data sent by a server; the code coverage rate is the coverage rate of the unit test code relative to the development code and the associated development code of the sub-module to be tested; the associated development code is a development code which has a calling relationship with the sub-module to be tested in the plurality of sub-modules.

5. The method of claim 4, further comprising, prior to generating a test request in response to a unit test request operation for a sub-module under test:

and determining the sub-module to be tested in response to the selection operation aiming at the sub-module.

6. The method of claim 5, further comprising, prior to determining the sub-module to be tested in response to the selection operation for the sub-module:

receiving test service configuration operations for the plurality of sub-modules; the test service configuration operation comprises configuration operation aiming at test environment, code type, monitoring port and Git server address corresponding to development code.

7. A server, characterized in that the server comprises:

the dependency establishing module is used for responding to a dependency configuration instruction which is sent by a client and aims at a plurality of sub-modules and a parent module, and establishing the dependency relationship between the plurality of sub-modules and the parent module;

the request receiving module is used for receiving a unit test request aiming at the sub-module to be tested, which is sent by the client; the sub-module to be tested is at least one sub-module in the plurality of sub-modules;

the code determining module is used for responding to the unit test request and determining the associated development code according to the dependency relationship; the associated development code is a development code which has a calling relationship with the sub-module to be tested in the plurality of sub-modules;

the testing module is used for testing the sub-module to be tested to obtain the code coverage rate; the code coverage rate is the coverage rate of the unit test code relative to the development code and the associated development code of the sub-module to be tested;

and the sending module is used for sending the code coverage rate to the client.

8. The server-side of claim 7, wherein the testing module is specifically configured to:

responding to the unit test request, determining a sub-module having a calling relationship with the sub-module to be tested from the plurality of sub-modules, and obtaining an associated sub-module;

acquiring a development code having a calling relationship with the sub-module to be tested from the association sub-module to obtain an association development code;

pulling the development code of the sub-module to be tested;

utilizing the unit test code of the sub-module to be tested to run a unit test on the development code of the sub-module to be tested and the associated development code;

and acquiring the coverage rate of the unit test code relative to the development code of the sub-module to be tested and the associated development code to obtain the code coverage rate.

9. The server-side of claim 8, wherein the testing module is specifically configured to:

acquiring a preset Git server address corresponding to the development code of the sub-module to be tested;

and pulling the development code of the sub-module to be tested from the Git server address to a local server.

10. A client, the client comprising:

the operation receiving module is used for receiving the dependent configuration operation aiming at the plurality of sub-modules and the parent module and generating a dependent configuration instruction;

the instruction sending module is used for sending the dependency configuration instruction to a server so that the server establishes the dependency relationship between the plurality of sub-modules and the parent module;

the request sending module is used for responding to unit test request operation aiming at the sub-modules to be tested, generating a test request and sending the test request to the server; the sub-module to be tested is at least one sub-module in the plurality of sub-modules;

the data receiving module is used for receiving the code coverage rate data sent by the server; the code coverage rate is the coverage rate of the unit test code relative to the development code and the associated development code of the sub-module to be tested; the associated development code is a development code which has a calling relationship with the sub-module to be tested in the plurality of sub-modules.

11. The client of claim 10, further comprising:

a submodule determination module for determining a submodule to be tested in response to a selection operation for the submodule.

12. The client of claim 11, further comprising:

a configuration operation receiving module for receiving test service configuration operations for the plurality of sub-modules; the test service configuration operation comprises configuration operation aiming at test environment, code type, monitoring port and Git server address corresponding to development code.

13. A computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the unit testing method of any of claims 1-6.

Images