CN106294130A - A kind of unit test method and device - Google Patents

Abstract

The invention discloses a unit testing method and device, comprising: determining a target unit to be tested; generating a first document file according to a function corresponding to the target unit, and the first document file includes: at least one input variable , and the output variable corresponding to the at least one input variable; according to each test value corresponding to each input variable in the first document file, generate the expected value of the output variable; store the attribute information corresponding to the target unit into the second document file, and compile the attribute information in the second document file; test the compiled second document file to obtain the actual test value; according to the expected value and the Actual test values to generate test results. The invention can reduce the workload of unit testing.

Description

A unit testing method and device

technical field

The invention relates to the technical field of software, in particular to a unit testing method and device.

Background technique

Unit testing is the most targeted, comprehensive, and thorough systematic testing of the smallest testable unit in a software program to verify the logical correctness of the software program and ensure that the behavior of the written software program satisfies the requirements of the programmer. specific needs. Unit testing can fully discover bugs (loopholes) in the software program during the software program development stage, so as to ensure the quality and efficiency of the software program.

At present, the unit test is mainly implemented manually. The unit test implemented manually mainly includes: completing a piece of software program and compiling the piece of software program; Modify the existing loopholes, and then compile the software program after modification until the compilation is passed. For the software program that has passed the compilation, input the variable value and run the operation to determine the test result. It can be seen that the workload of unit testing in the prior art is huge.

Contents of the invention

The embodiment of the present invention provides a unit testing method and device, so as to reduce the workload of unit testing.

In the first aspect, the embodiment of the present invention provides a method for unit testing, the method comprising:

Identify the target units that need to be tested;

According to the function corresponding to the target unit, a first document file is generated, and the first document file includes: at least one input variable and an output variable corresponding to the at least one input variable;

generating an expected value of the output variable according to each test value corresponding to each input variable in the first document file;

storing attribute information corresponding to the target unit in a second document file, and compiling the attribute information in the second document file;

performing a test on the compiled second document file to obtain an actual test value;

A test result is generated based on the expected value and the actual test value.

Preferably,

Before the determination of the target unit to be tested, it further includes: determining a plurality of minimum units corresponding to the software program to be tested; compiling the software program; performing static analysis on the compiled software program; according to the analysis As a result, it is determined that there is no minimum unit of loopholes;

The determining the target unit that needs to be tested includes: determining the minimum unit without loopholes as the target unit.

Preferably,

It further includes: setting the number threshold;

Before generating the expected value of the output variable, it further includes: according to each test value corresponding to each input variable in the first document file, determining to execute the test script item for generating the expected value of the output variable number; when the determined number of test scripts is greater than the number threshold, the number of test scripts is divided into at least two groups; for each group, perform the generation of the expected value of the output variable; Wherein, the number of test scripts is the product of the number of test values corresponding to each input variable.

Preferably, the test results include: comparison results between the expected value and the actual test value, test reports and test coverage documents; wherein, the test reports include: total number of vulnerabilities, total number of serious vulnerabilities, type of vulnerabilities, unit The total workload of the test and the analysis of the cause of the vulnerability; the test coverage document includes: the percentage of the test coverage, the execution status of each line of code, and the unexecuted code;

Preferably, the second document file includes: the definition of input variables, the definition of output variables, the definition of types, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit.

In a second aspect, an embodiment of the present invention provides a device for unit testing, which includes:

Determine the unit, used to determine the target unit that needs to be tested;

The first generation unit is configured to generate a first document file according to the function corresponding to the target unit; then, the first document file includes: at least one input variable and an output variable corresponding to the at least one input variable ; According to each test value corresponding to each input variable in the first document file, generate the expected value of the output variable;

a compiling unit, configured to store attribute information corresponding to the target unit in a second document file, and compile the attribute information in the second document file;

a test unit, configured to test the compiled second document file to obtain actual test values;

A second generating unit, configured to generate a test result according to the expected value and the actual test value.

Preferably,

Further includes:

The analysis unit is used to determine a plurality of minimum units corresponding to the software program to be tested; compile the software program; perform static analysis on the compiled software program; determine the minimum unit without loopholes according to the analysis results; Wherein, the determining unit is specifically configured to: determine the smallest unit without loopholes as the target unit.

Preferably,

Further includes:

The storage unit is used to store the set number threshold;

Further includes:

A division unit, configured to determine the number of test scripts for executing the expected value of the output variable that is generated according to each test value corresponding to each input variable in the first document file; after the determined number of test scripts When greater than the number of thresholds, the number of test scripts is divided into at least two groups; for each group, perform the generation of the expected value of the output variable; wherein, the number of test scripts is each input Variables correspond to the product of the number of test values.

Preferably, the test results include: a comparison result between the expected value and the actual test value, a test report and a test coverage document; wherein,

The test report includes: the total number of vulnerabilities, the total number of serious vulnerabilities, the types of vulnerabilities, the total workload of unit testing, and the analysis of the causes of vulnerabilities;

The test coverage document includes: the percentage of test coverage, the execution status of each line of code, and unexecuted code.

Preferably, the second document file includes: the definition of input variables, the definition of output variables, the definition of types, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit.

It can be seen that the embodiment of the present invention provides a unit testing method and device. Firstly, the target unit to be tested is determined, and according to the function corresponding to the target unit, a function including at least one input variable and the corresponding input variable is generated. The first documentation file for the output variable. Input each test value of each input variable in the first document file, generate the expected value of the output variable according to the test value, then store the attribute information corresponding to the target unit in the second document file, and Compile the second document file until the compilation is passed. Test the second document file after the compilation is passed to obtain an actual test value, compare the actual test value with the expected value, and generate a test result. This unit test method realizes a semi-automatic operation, Less hands-on time for testers and therefore less effort for unit testing.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are For some embodiments of the present invention, those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a kind of flow chart of unit testing method provided by one embodiment of the present invention;

Fig. 2 is another kind of unit test method flowchart provided by one embodiment of the present invention;

FIG. 3 is a hardware architecture diagram of a device where a device is located according to an embodiment of the present invention;

Fig. 4 is a structural diagram of a unit testing device provided by an embodiment of the present invention;

FIG. 5 is a structural diagram of another unit testing device provided by an embodiment of the present invention;

Fig. 6 is a structural diagram of another unit testing device provided by an embodiment of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work belong to the protection of the present invention. scope.

As shown in Figure 1, the embodiment of the present invention provides a unit testing method, which may include the following steps:

Step 101: Determine the target unit to be tested;

Step 102: Generate a first document file according to the function corresponding to the target unit, and the first document file includes: at least one input variable and an output variable corresponding to the at least one input variable;

Step 103: Generate the expected value of the output variable according to each test value corresponding to each input variable in the first document file;

Step 104: storing the attribute information corresponding to the target unit in a second document file, and compiling the attribute information in the second document file;

Step 105: Test the compiled second document file to obtain an actual test value;

Step 106: Generate a test result according to the expected value and the actual test value.

According to the above embodiment, the target unit to be tested is first determined, and a first document file including at least one input variable and an output variable corresponding to the at least one input variable is generated according to the function corresponding to the target unit. Input each test value corresponding to each input variable in the first document file, generate the expected value of the output variable according to the test value, and then store the attribute information corresponding to the target unit in the second document file, And compile the second document file until the compilation is passed. Test the second document file after the compilation is passed to obtain an actual test value, compare the actual test value with the expected value, and generate a test result. This unit test method realizes a semi-automatic operation, Less hands-on time for testers and therefore less effort for unit testing.

In one embodiment of the present invention, before determining the target unit to be tested, it is necessary to statically analyze the software program, manually exclude the smallest unit with loopholes in the software program, and the smallest unit without loopholes. The target units that need to be tested are identified in the unit, including:

Determining multiple minimum units corresponding to the software program to be tested; compiling the software program; performing static analysis on the compiled software program; determining the minimum unit without loopholes according to the analysis results;

The determining the target unit that needs to be tested includes: determining the minimum unit without loopholes as the target unit.

According to the above-mentioned embodiment, at first all minimum units in the software program to be tested shall be determined, the software program shall be compiled, and the loopholes such as lexical errors and grammatical errors existing in the software program shall be checked, and then the existence of all such loopholes shall be ruled out The part of the program with the above-mentioned loopholes, statically analyze the remaining part of the software program, manually perform lexical analysis, syntax analysis, and static error analysis on the remaining software programs to find out the loopholes, and then eliminate the part with the above-mentioned loopholes program, and all the smallest units in the remaining part of the software program are the smallest units without loopholes, and the determination of the target units to be tested is determined in these smallest units without loopholes. It can be seen that before determining the target unit that needs to be tested, the software program is compiled and statically analyzed to ensure that the determined target unit is determined in the part of the smallest unit that does not have loopholes, so it can reduce The workload of unit testing.

In one embodiment of the present invention, in the unit test process, if the amount of data tested is very large, then the speed of the unit test will be affected, so at this time it is necessary to limit the amount of data tested each time to ensure that the unit test can be performed quickly. The completion of the test, then it is necessary to pre-set the threshold of the number of tests to ensure that the number of tests is within a certain threshold and ensure that the unit test can be completed quickly. include:

Set the number threshold;

Before generating the expected value of the output variable, according to each test value corresponding to each input variable in the first document file, determine the number of test scripts for executing the generation of the expected value of the output variable; When the determined number of test scripts is greater than the number threshold, divide the number of test scripts into at least two groups; for each group, perform the generation of the expected value of the output variable; wherein, the The number of test scripts mentioned above is the product of the number of test values corresponding to each input variable.

According to the above-mentioned embodiment, the number of thresholds can be preset, and the number of test scripts that execute the generation of the expected value of the output variable is determined according to each test value corresponding to each input variable in the first document file, Compare the number of test scripts of the expected value with the set number threshold, and when the determined number of test scripts is greater than the number threshold, divide the number of test scripts into at least two grouping; for each grouping, perform the generating the expected value of the output variable. After the number of test scripts is grouped, the corresponding codes in each group of test scripts can be grouped and tested to reduce the amount of data for each test, thus improving the speed of unit testing.

In one embodiment of the present invention, the test results of the target unit include: comparison results between the expected value and the actual test value, test reports and test coverage documents, testers can find out from the above test results Vulnerabilities, and according to the specific results, make targeted modifications to each vulnerability. include:

The test results include: comparison results between the expected value and the actual test value, test reports and test coverage documents; wherein, the test reports include: total number of vulnerabilities, types of vulnerabilities, total unit test workload and causes of vulnerabilities At least one of the analysis; the test coverage document includes: at least one of the percentage of test coverage, the execution of each line of code and the unexecuted code;

According to the above-mentioned embodiment, the tester finds the required test result in the target document among the three test result documents of the expected value and the actual test value comparison result, test report and test coverage document according to specific needs , which reduces the search time for testers to find test results.

In one embodiment of the present invention, the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit are all written into the second documents, including:

The second document file includes: the definition of input variables, the definition of output variables, the definition of types, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit.

According to the above-mentioned embodiment, the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit are all placed in the second document, The integrity of the attribute information defined by the target unit is guaranteed, and it is convenient for testers to compile the second document.

In order to make the purpose, technical solution and advantages of the present invention clearer, below in conjunction with the method for unit testing shown in Figure 2, taking a target unit in the testing software program as an example, the method for unit testing provided by the embodiment of the present invention will be further described in detail.

As shown in Figure 2, an embodiment of the present invention provides another unit testing method, which may include the following steps:

Step 201: Determine multiple minimum units corresponding to the software program to be tested and compile the software program.

A software program to be tested is determined, a plurality of minimum units in the software program are determined, and the software program is compiled. The minimum unit is the minimum detectable unit in the software program. For example, if the programming language is C language, then the minimum unit to be tested is a function, and if the programming language is C++, then the minimum unit to be tested is Units are classes. For example, if it is determined that the programming of the software program to be tested is C language, then it is necessary to determine a plurality or all of the minimum units in the software program, such as determining that there are function 1, function 2, function 3, and so on in the software program. Function 50, a total of 50 minimum units. After confirming and compiling the software program as a whole, find loopholes such as lexical errors and grammatical errors in the software program. The loopholes may be code duplication, missing codes, or undefined codes. After the compilation is completed, if there are loopholes in the code of the three smallest units of function 3, function 6, and function 15, then the tester must eliminate this part of the code with errors, and modify the vulnerability of this part of the code, and the remaining part The software program is the part without bugs.

Step 202: Perform static analysis on the compiled software program and determine the smallest unit without loopholes according to the analysis result.

For software programs without vulnerabilities after compiling and excluding codes with vulnerabilities, for example, after excluding the codes of the three smallest units of function 3, function 6, and function 15 in the above example, it is necessary to perform manual static analysis on the remaining software programs , the testers manually check for code duplication, missing codes, or undefined codes. After the static analysis is over, they find that there are loopholes in the code of function 24, function 35, and the two smallest units. Then the testers will Exclude this part of the code with errors, and modify this part of the code for vulnerabilities, and the software program without vulnerabilities after the static analysis excludes the code with vulnerabilities is the smallest unit without vulnerabilities determined according to the analysis results.

Step 203: Determine the target unit to be tested.

The determination of the target unit to be tested is determined as the target unit among the smallest units without loopholes after static analysis of the software program. For example, after the software program is statically analyzed, it is found that function 1, function 2, function 10, function 27, etc. are the smallest units without loopholes, so it can be used in function 1, function 2, function 10, function 27, etc. Among the smallest units without vulnerabilities, determine function 2 as the target unit to be tested.

Step 204: Set the number threshold.

The threshold of the number of bars can be determined by the tester according to the specific situation of the test, for example, the threshold of the number of bars can be set to 10, 20, 100, etc.

Step 205: Generate a first document file according to the function corresponding to the target unit.

The first document file includes: at least one input variable, and an output variable corresponding to the at least one input variable;

For example, if the function corresponding to the target unit is function 2, then the generated first document file can be an EXCEL form, and in this EXCEL form, at least one input variable of function 2 and the at least one input variable of function 2 are included. An output variable corresponding to an input variable. For example, the input variable A, the input variable B, and the output variable C corresponding to the input variable obtained in the EXCEL sheet.

Step 206: According to each test value corresponding to each input variable in the first document file, and determine the number of test scripts to execute to generate the expected value of the output variable.

Each test value corresponding to each input variable is input in the first document file, and the number of test scripts executed to generate the expected value of the output variable is obtained according to the product of the number of test values corresponding to each input variable. For example, the test value of the input variable A is 3, the test value of the input variable B is 2, and the test value of the input variable C is 4, so the number of test scripts that execute the described generation of the expected value of the output variable is 3*2*4=24 pieces.

Step 207: When the determined number of test scripts is greater than the set number threshold, perform: divide the number of test scripts into at least two groups.

For example, after determining the number of test scripts, the number of determined test scripts will be grouped when the number of test scripts is greater than the set number threshold, if it is less than the set number threshold When determining the number of test scripts as described above, there is no need to group them. For example, the set number threshold is 25. When the number of test scripts is determined to be 20, it is determined that the number of test scripts 20 is less than the set number threshold 25. Then the number of test scripts does not need to be grouped, but when it is determined When the number of test scripts is 50, it is determined that the number of test scripts 50 is greater than the set number threshold 25, then the number of test scripts will be grouped, and the number of groups can be grouped by testers according to specific needs. Can be divided into 2 groups, can also be divided into 3 groups.

Step 208: Generate the expected value of the output variable according to each test value corresponding to each input variable in the first document file.

According to each test value corresponding to each input variable input in the first document, the expected value of the output variable is generated. The test value is calculated according to the function corresponding to the determined target unit to generate the expected value of the output variable.

Step 209: Store the attribute information corresponding to the target unit in a second document file, and compile the attribute information in the second document file.

The second document file includes: the definition of input variables, the definition of output variables, the definition of types, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit.

For example, the second document file can be a TXT file. If the target unit is determined to be function 1, then the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function and each input variable of function 1 Each corresponding test value will be written into the second document file: this TXT file, and then compile all the attribute information about function 1 in the TXT file to find out the existence of lexical errors, grammatical errors and other loopholes , this vulnerability may be code duplication, code is not fully written, missing code, or code is undefined. Then modify the found loopholes, and then compile the second document file after the modification is completed, and repeat this cycle until the second document file is compiled successfully.

Step 210: Test the compiled second document file to obtain actual test values.

For the compiled second document file, the tester will use a certain test script to run the test to obtain the actual test value.

For example, for function 1, after compiling, the tester will use the determined test script to run the test on the second document file, and obtain the corresponding actual test value according to each test value corresponding to each input variable.

Step 211: Generate a test result according to the expected value and the actual test value.

The expected value and the actual test value comparison result, test report and test coverage document; wherein, the test report includes: at least one of the total number of vulnerabilities, the type of vulnerabilities, the total workload of unit testing, and the analysis of the causes of vulnerabilities ; The test coverage document includes: at least one of the percentage of test coverage, the execution status of each line of code and unexecuted code;

For example, the comparison result between the expected value and the actual test value can have two situations, including: the comparison expected result is completely consistent with the actual result without any error; and/or the comparison expectation result There is an error within a certain precision with the determined actual result, and the expected result of the comparison is also considered to be consistent with the actual result. For example, if the expected value of function 1 is 5, and the actual test value is also 5, then it is considered consistent and there is no loophole. For example, if the expected value of function 1 is 5, and the actual test value is 8, then it is considered inconsistent and there are loopholes, and testers need to solve and modify the corresponding loopholes based on this result. In addition, as mentioned above, there is an error within a certain accuracy between the expected result and the determined actual result. For example, it can be set that the error within 0.5 is consistent. For example, the expected value of function 1 is 5, and the actual test value is also 5.4. Then it is considered consistent and there is no loophole. The comparison result between the expected value and the actual test value can be written into the first file, which is an EXCEL table.

The test report includes: at least one of the total number of vulnerabilities, the type of vulnerabilities, the total workload of the unit test and the analysis of the causes of the vulnerabilities; for example, the test report can be an EXCEL form, such as after the test of the determined target unit function 1 is completed , in the form of a table to display the total number of vulnerabilities, the types of vulnerabilities, the total workload of unit testing, and the analysis of the causes of the vulnerabilities. The analysis of the causes of the vulnerabilities is given by the testers based on the specific conditions of the test report.

The test coverage document includes: at least one of the percentage of test coverage, the execution status of each line of code and the unexecuted code; for example, after the test of the determined target unit function 1 is completed, a TXT text to generate this test coverage document, the document will give the percentage of test coverage, this percentage is given according to the specific situation of the actual test, such as 80%. The execution status of each line of code will write the untested code lines into this test coverage document, so that testers can know which codes have not been tested.

As shown in FIG. 3 and FIG. 4 , the embodiment of the present invention provides a unit testing device. The device embodiments can be implemented by software, or by hardware or a combination of software and hardware. From the perspective of hardware, as shown in Figure 3, it is a hardware structure diagram of the device where a unit test device is provided in the embodiment of the present invention, except for the processor, memory, network interface, and non-volatile memory shown in Figure 3 In addition to the volatile memory, the device where the device in the embodiment is located may generally include other hardware, such as a forwarding chip responsible for processing packets, and the like. Taking software implementation as an example, as shown in Figure 4, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for operation by the CPU of the device where it is located.

A unit testing device provided by an embodiment of the present invention, referring to FIG. 4 , includes:

Determining unit 401, configured to determine the target unit to be tested;

The first generating unit 402 is configured to generate a first document file according to the function corresponding to the target unit; then, the first document file includes: at least one input variable and an output corresponding to the at least one input variable variable; generating an expected value of the output variable according to each test value corresponding to each input variable in the first document file;

A compiling unit 403, configured to store attribute information corresponding to the target unit in a second document file, and compile the attribute information in the second document file;

a testing unit 404, configured to test the compiled second document file to obtain an actual test value;

The second generation unit 405 is configured to generate a test result according to the expected value and the actual test value.

In one embodiment of the present invention, as shown in Figure 5, the unit testing device may further include:

The analysis unit 501 is used to determine a plurality of minimum units corresponding to the software program to be tested; compile the software program; perform static analysis on the compiled software program; determine the minimum unit without loopholes according to the analysis results ;

Wherein, the determining unit 401 determining the target unit that needs to be tested includes: determining a minimum unit without a loophole as the target unit.

In one embodiment of the present invention, as shown in Figure 6, the unit testing device may further include:

A storage unit 601, configured to store the set number threshold;

The dividing unit 602 is configured to determine the number of test scripts that execute the test scripts that generate the expected values of the output variables according to each test value corresponding to each input variable in the first document file; When the number is greater than the number threshold, the number of test scripts is divided into at least two groups; for each group, the expected value of the output variable is generated; wherein, the number of test scripts is each The input variable corresponds to the product of the number of test values.

In one embodiment of the present invention, the test results include: comparison results between the expected value and the actual test value, test reports and test coverage documents; wherein, the test reports include: total number of vulnerabilities, types of vulnerabilities, At least one of the total unit test workload and vulnerability analysis; the test coverage document includes: at least one of the percentage of test coverage, the execution of each line of code, and unexecuted code;

In an embodiment of the present invention, the second document file includes: the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function, and each corresponding to each input variable in the function corresponding to the target unit. test value.

In summary, each embodiment of the present invention can at least achieve the following beneficial effects:

1. In the embodiment of the present invention, first determine the target unit to be tested, and generate a first document including at least one input variable and an output variable corresponding to the at least one input variable according to the function corresponding to the target unit document. Input each test value corresponding to each input variable in the first document file, generate the expected value of the output variable according to the test value, and then store the attribute information corresponding to the target unit in the second document file, And compile the second document file until the compilation is passed. Test the second document file after the compilation is passed to obtain an actual test value, compare the actual test value with the expected value, and generate a test result. This unit test method realizes a semi-automatic operation, Less hands-on time for testers and therefore less effort for unit testing.

2. In the embodiment of the present invention, it is first necessary to determine all the smallest units in the software program to be tested, compile the software program, check the loopholes such as lexical errors and grammatical errors in the software program, Then get rid of that part of program that has said loophole, carry out static analysis to remaining that part of software program, manually carry out lexical analysis, grammatical analysis, static error analysis to described remaining software program to find out loophole, then rule out existence of said loophole loopholes, and all the smallest units in the remaining part of the software program are the smallest units without loopholes, and the determination of the target unit to be tested is determined in these smallest units without loopholes of. It can be seen that before determining the target unit that needs to be tested, the software program is compiled and statically analyzed to ensure that the determined target unit is determined in the part of the smallest unit that does not have loopholes, so it can reduce The workload of unit testing.

3. In the embodiment of the present invention, the threshold value of the number of items can be preset, and according to each test value corresponding to each input variable in the first document file, determine and execute the test that generates the expected value of the output variable The number of scripts, comparing the number of test scripts of the expected value with the set number threshold, when the determined number of test scripts is greater than the threshold, the test scripts will be The data is divided into at least two groupings; for each grouping, the generating the expected value of the output variable is performed. After the number of test scripts is grouped, the corresponding codes in each group of test scripts can be grouped and tested to reduce the amount of data for each test, thus improving the speed of unit testing.

4. In the embodiment of the present invention, the tester finds out in the target documents among the three test result documents of the expected value and the actual test value comparison result, test report and test coverage document according to specific needs. required test results, reducing the search time for testers to find test results.

5. In the embodiment of the present invention, the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit are all placed in the second In the first document, the integrity of the attribute information defined by the target unit is guaranteed, which is convenient for testers to compile the second document.

The information exchange and execution process among the units in the above-mentioned device are based on the same concept as the method embodiment of the present invention, and the specific content can refer to the description in the method embodiment of the present invention, and will not be repeated here.

It should be noted that in this article, 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 that there is a relationship between these entities or operations. There is no such actual relationship or sequence. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional same elements in the process, method, article or apparatus comprising said element.

Those of ordinary skill in the art can understand that all or part of the steps to realize the above method embodiments can be completed by program instructions related hardware, and the aforementioned programs can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that the above descriptions are only preferred embodiments of the present invention, and are only used to illustrate the technical solution of the present invention, and are not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (10)

1. A method of unit testing, comprising:

determining a target unit to be tested;

generating a first document file according to the function corresponding to the target unit, wherein the first document file comprises: at least one input variable and an output variable corresponding to the at least one input variable;

generating an expected value of the output variable according to each test value corresponding to each input variable in the first document file;

storing the attribute information corresponding to the target unit into a second document file, and compiling the attribute information in the second document file;

testing the compiled second document file to obtain an actual test value;

and generating a test result according to the expected value and the actual test value.

2. The method of claim 1,

before the determining the target unit needing to be tested, further comprising: determining a plurality of minimum units corresponding to the software program to be tested; compiling the software program; performing static analysis on the compiled software program; determining a minimum unit without a vulnerability according to an analysis result;

the determining of the target unit needing to be tested comprises the following steps: and determining the minimum unit without the vulnerability as the target unit.

3. The method of claim 1,

further comprising: setting a number threshold;

prior to the generating the expected value of the output variable, further comprising: determining the number of test scripts for executing the expected values of the generated output variables according to the test values corresponding to the input variables in the first document file; when the number of the test scripts is larger than the number threshold value, dividing the number of the test scripts into at least two groups; performing the generating an expected value of the output variable for each packet; and the number of the test scripts is the product of the number of the test values corresponding to each input variable.

4. The method of claim 1, wherein the test results comprise: comparing the expected value with the actual test value, and testing report and test coverage rate document; wherein,

the test report includes: at least one of total number of vulnerabilities, vulnerability type, total workload of unit testing and vulnerability cause analysis;

the test coverage document comprising: at least one of a percentage of coverage, execution of each line of code, and unexecuted code is tested.

5. The method of any of claims 1-4, wherein the second document file comprises: and the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit.

6. A unit testing apparatus, comprising:

the determining unit is used for determining a target unit to be tested;

the first generation unit is used for generating a first document file according to the function corresponding to the target unit; the first document file comprises: at least one input variable and an output variable corresponding to the at least one input variable; generating an expected value of the output variable according to each test value corresponding to each input variable in the first document file;

the compiling unit is used for storing the attribute information corresponding to the target unit into a second document file and compiling the attribute information in the second document file;

the test unit is used for testing the compiled second document file to obtain an actual test value;

and the second generating unit is used for generating a test result according to the expected value and the actual test value.

7. The unit testing device of claim 6,

further comprising:

the analysis unit is used for determining a plurality of minimum units corresponding to the software program to be tested; compiling the software program; performing static analysis on the compiled software program; determining a minimum unit without a vulnerability according to an analysis result;

the determining unit is specifically configured to: and determining the minimum unit without the vulnerability as the target unit.

8. The unit testing device of claim 6,

further comprising:

a storage unit for storing a set number threshold;

further comprising:

the dividing unit is used for determining the number of test scripts for executing the expected value of the output variable according to each test value corresponding to each input variable in the first document file; when the number of the test scripts is larger than the number threshold value, dividing the number of the test scripts into at least two groups; performing the generating an expected value of the output variable for each packet; and the number of the test scripts is the product of the number of the test values corresponding to each input variable.

9. The unit testing apparatus of claim 6, wherein the test results comprise: comparing the expected value with the actual test value, and testing report and test coverage rate document; wherein,

the test report includes: at least one of total number of vulnerabilities, vulnerability type, total workload of unit testing and vulnerability cause analysis;

the test coverage document comprising: at least one of a percentage of coverage, execution of each line of code, and unexecuted code is tested.

10. A unit testing device according to any of claims 6-9, wherein the second document file comprises: and the definition of the input variable, the definition of the output variable, the definition of the type, the main body of the function and each test value corresponding to each input variable in the function corresponding to the target unit.