WO2023217118A1

WO2023217118A1 - Code test method and apparatus, and test case generation method and apparatus

Info

Publication number: WO2023217118A1
Application number: PCT/CN2023/092939
Authority: WO
Inventors: 张剑飞; 周海莲; 周智泉; 赵红兵
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2022-05-10
Filing date: 2023-05-09
Publication date: 2023-11-16
Also published as: CN114840427A

Abstract

Disclosed in the present description are a code test method and apparatus, and a test case generation method and apparatus. When a code to be tested is under test, it is possible to accurately determine actual return value types of a generic method which is called during a running process of said code, and a method in which forced type casting occurs, such that said code can be tested on the basis of the determined actual return value types, and the accuracy of a test result is thus improved.

Description

A method and device for code testing and test case generation

Technical field

This description relates to the field of computer technology, and in particular, to a method and device for code testing and test case generation.

Background technique

In the process of software testing, since the method to be tested may have a high dependence on other methods, the tester will not be able to test the method to be tested alone, which will affect the progress of the testing work. Therefore, in order to solve the problem For this problem, software testers usually use Mock services (that is, dependent service substitutes) to replace other methods associated with the method to be tested to test the method to be tested.

However, when using the Mock service, you need to determine the return value type of the method called by the method to be tested. For ordinary methods, you can directly determine the return value type of the method, but for some return values, you need to determine the return value type according to the actual operation. For methods that can only determine the specific type at the time, a type is often randomly determined as the return value type of the method, which reduces the accuracy of the generated test cases and affects the coverage of the test cases.

Therefore, how to effectively determine the return value type of the method to be tested during software testing, and thereby improve the accuracy of the test results of the method to be tested, is an urgent problem that needs to be solved.

Contents of the invention

This specification provides a method and device for code testing and test case generation to partially solve the problem in related technologies of low accuracy of test results caused by returning error type return values.

This manual adopts the following technical solution: This manual provides a code testing method, including: obtaining the code to be tested; according to the type of parameters required for the method called by the code to be tested, and/or testing the code to be tested. The analysis results obtained after analyzing the bytecode corresponding to the code determine the actual return value type corresponding to the method called when testing the code to be tested. The method types of the methods called when testing the code to be tested include: At least one of a generic method and forced type conversion; according to the actual return value type, the test result for the code to be tested is obtained.

Optionally, according to the type of parameters required by the method called by the code to be tested, and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested, it is determined that the code to be tested is method called when The actual return value type corresponding to the method specifically includes: obtaining the code of the method called by the code to be tested; and determining the code of the method called by the code to be tested according to the obtained code of the method called by the code to be tested. The actual return value of the method called, and the association relationship between the parameter type required by the method called by the code to be tested; according to the association relationship, and the type of parameters required by the method called by the code under test, Determine the actual return value type corresponding to the method called when testing the code to be tested.

Optionally, according to the actual return value type, obtain the test result for the code to be tested, which specifically includes: creating a method data structure MethodDescripter structure according to the association relationship, the MethodDescripter structure includes: the actual return of the calling method Value type, the number of times the MethodDescripter structure is called, the method name of the calling method, the class name of the calling method, and the incoming parameters of the calling method; generate the code to be tested based on the MethodDescripter structure and the actual return value type The mock method corresponding to the called method; through the mock method, the test results for the code to be tested are obtained.

Optionally, according to the type of parameters required by the method called by the code to be tested, and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested, it is determined that the code to be tested is The actual return value type corresponding to the method called, specifically includes: by analyzing the bytecode corresponding to the code to be tested, determining that the method type from the method called by the code to be tested is forced type conversion The method is used as the target method; when testing the code to be tested, the actual return value type corresponding to the method called by the code to be tested is determined according to the target method.

Optionally, when testing the code to be tested, before determining the actual return value type corresponding to the method called by the code to be tested according to the target method, the method further includes: converting the The corresponding relationship between the code line number corresponding to the target method in the code to be tested and the actual return value type after forced type conversion of the return value of the target method is saved; when testing the code to be tested, According to the target method, determine the actual return value type corresponding to the method called by the code to be tested, specifically including: if during the testing process of the code to be tested, determine the method called by the code to be tested The code line number of the forced type conversion method is used as the target line number; according to the target line number, the actual return value type corresponding to the method called by the code to be tested is queried from the pre-saved correspondence relationship.

Optionally, according to the actual return value type, obtaining the test result for the code to be tested specifically includes: querying the actual return value corresponding to the method called by the code to be tested from the pre-saved correspondence relationship Type, generate a mock method corresponding to the method called by the code to be tested; use the mock method to obtain test results for the code to be tested.

This manual provides a method for generating test cases, including: obtaining each test case; for each test Use case, through the above code testing method, test the set code to obtain the test results corresponding to the test case; according to the test results corresponding to each test case, determine whether the preset test conditions are met; if it is determined that the preset test conditions are not met, test conditions, regenerate each test case, and test the set code according to each regenerated test case until the test condition is met, and obtain the test case generated when the test condition is met.

Optionally, regenerating each test case specifically includes: selecting at least some test cases from each test case and combining them in pairs to obtain each test case combination; for each test case combination, combining the two test cases included in the test case combination. Parameters of the same type in each test case are weighted to obtain a regenerated test case.

Optionally, regenerating each test case specifically includes: selecting at least some test cases from each test case; for each selected test case, numerically adjusting at least some parameters included in the test case, and/or Adjust the code to be tested contained in the test case to obtain a regenerated test case.

This specification provides a code testing device, including: an acquisition module, used to obtain the code to be tested; a determination module, used to determine the type of parameters required by the method called by the code to be tested, and/or to determine the The analysis results obtained after analyzing the bytecode corresponding to the code to be tested determine the actual return value type corresponding to the method called when the code to be tested is tested, and the method type of the method called when the code to be tested is tested. It includes: at least one of a generic method and forced type conversion; a test module, used to obtain test results for the code to be tested according to the actual return value type.

Optionally, the determination module is specifically configured to obtain the code of the method called by the code to be tested; and determine the code of the method called by the code to be tested according to the obtained code of the method called by the code to be tested. The relationship between the actual return value of the method called during testing and the type of parameters required by the method called by the code to be tested; according to the relationship, and the type of parameters required by the method called by the code under test , determine the actual return value type corresponding to the method called when testing the code to be tested.

Optionally, the test module is specifically configured to create a method data structure MethodDescripter structure according to the association relationship. The MethodDescripter structure includes: the actual return value type of the calling method, the number of times the MethodDescripter structure is called, and the method of calling the method. name, the class name of the calling method, and the incoming parameters of the calling method; according to the MethodDescripter structure and the actual return value type, a mock method corresponding to the method called by the code to be tested is generated; through the mock method , to obtain the test results for the code to be tested.

Optionally, the determination module is specifically configured to determine, from the methods called by the code to be tested, that the method type is a forced type conversion method by analyzing the bytecode corresponding to the code to be tested, as target Method; when testing the code to be tested, determine the actual return value type corresponding to the method called by the code to be tested according to the target method.

Optionally, the device further includes: an analysis module, configured to compare the code line number corresponding to the target method in the code to be tested with the actual return value of the return value of the target method after forced type conversion. The corresponding relationship of the types is saved; the determination module is specifically used to determine, during the testing process of the code to be tested, that the method called by the code to be tested is the code line number of the forced type conversion method, as the target Line number; according to the target line number, query the actual return value type corresponding to the method called by the code to be tested from the pre-saved correspondence.

Optionally, the test module is specifically configured to generate the actual return value type corresponding to the method called by the code to be tested based on the query from the pre-saved correspondence relationship, and generate the return value type corresponding to the method called by the code to be tested. Mock method; through the mock method, test results for the code to be tested are obtained.

This manual provides a device for generating test cases, including: a use case acquisition module, used to obtain each test case; a use case testing module, used to test the set code for each test case through the above code testing method , obtain the test results corresponding to the test case; the judgment module is used to determine whether the preset test conditions are met based on the test results corresponding to each test case; the generation module is used to re-run the test when it is determined that the test conditions are not met. Each test case is generated, and the set code is tested according to each regenerated test case until the test condition is met, and the test case generated when the test condition is met is obtained.

Optionally, the generation module is specifically configured to select at least some test cases from each test case and combine them in pairs to obtain each test case combination; for each test case combination, combine the two test case combinations included in the test case combination. Parameters of the same type in the test case are weighted to obtain a regenerated test case.

Optionally, the generation module is specifically configured to select at least some test cases from each test case; for each selected test case, numerically adjust at least some parameters contained in the test case, and/or The code to be tested contained in the test case is adjusted to obtain a regenerated test case.

This specification provides a computer-readable storage medium. The storage medium stores a computer program. When the computer program is executed by a processor, the above code testing and test case generation methods are implemented.

This specification provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the above code testing and test case generation methods are implemented.

At least one of the above technical solutions adopted in this manual can achieve the following beneficial effects: The first method of code testing is to obtain the code to be tested, and then determine the code to be tested based on the type of parameters required by the method called by the code to be tested and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested. The actual return value type corresponding to the method called during testing. The method type of the method called when testing the code to be tested includes at least one of calling a generic method and forced type conversion, and based on the actual return value type, the specific return value type is obtained. Test results of the code under test.

As can be seen from the above method, when testing the code to be tested, the actual return value type of the generic method called during the running process of the code to be tested and the method where forced type conversion occurs can be accurately determined, so that the actual return value type can be determined based on The determined actual return value type is used to test the code to be tested, thereby improving the accuracy of the test results.

Description of the drawings

The drawings described here are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation of this specification. In the attached picture:

Figure 1 is a schematic flow chart of a code testing method provided in this manual;

Figure 2 is a schematic diagram of the method for determining the actual return value type of the generic method provided in this specification;

Figure 3 is a schematic flow chart of a test case generation method provided in this manual;

Figure 4 is a schematic diagram of a code testing device provided in this specification;

Figure 5 is a schematic diagram of a device for generating test cases provided in this specification;

FIG. 6 is a schematic diagram of an electronic device corresponding to FIG. 1 provided in this specification.

Detailed ways

In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only some of the embodiments of this specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this specification.

The technical solutions provided by each embodiment of this specification will be described in detail below with reference to the accompanying drawings.

Figure 1 is a schematic flow chart of a code testing method provided in this manual, including the following steps S101 Go to S103.

S101: Obtain the code to be tested.

In this manual, the tester can test the code of the software to be tested based on the testing requirements. Specifically, the tester can first determine a part of the code from the code of the software to be tested as the code to be tested, and then the code to be tested can be Conduct tests to obtain test results for the code to be tested.

The code to be tested may refer to a collection of codes that are part of the code of the software to be tested. For example, the code to be tested may be one or more classes to be tested (a class here refers to a A custom reference data type, the class encapsulates the code corresponding to several attributes and methods). Another example: the code to be tested can also be one or more methods (i.e., a collection of code statements) contained in the code of the software to be tested. , these code statements together perform a function (the method is contained in the class or object of the class) corresponding code.

In this specification, the execution subject of the method for implementing code testing may refer to a designated device such as a terminal device installed on the business platform, or may refer to a terminal device such as a desktop computer, laptop computer, etc. For the convenience of description, only Taking the terminal device as the execution subject as an example, the code testing method provided in this manual will be explained.

Therefore, after receiving the test instruction sent by the tester, the terminal device can first obtain the code to be tested, and then test the code to be tested to obtain the test results of the code to be tested.

S102: Based on the type of parameters required for the method called by the code to be tested and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested, determine the parameters used when the code to be tested is tested. The actual return value type corresponding to the called method. The method type of the method called when testing the code to be tested includes at least one of a generic method and forced type conversion.

When the code under test is running, the terminal device can intercept the calling instructions of the method called by the code under test during running, and determine the method type of the method called by the code under test during running based on the intercepted calling instructions.

Among them, the method type of the method called by the code under test during the running process can be a generic method (that is, a method whose incoming parameters are of uncertain type) and a forced type conversion (that is, a method where a forced type conversion occurs during the calling process). method, in which the forced type conversion occurs when the original return value type of the method is converted into at least one of another data type).

It should be noted that the interception in the above content is not interception in the literal sense, but monitoring the calling instructions of the method called by the code under test during the running process, through the method of dynamic proxy. A method similar to the interception effect.

Based on the introduction of the above method types, this manual mainly focuses on determining the actual return value types of the above two method types, that is, the generic method and the forced type conversion. Therefore, the following will focus on how to determine the two method types. The actual return value type of the method is explained in detail.

For generic methods, the terminal device can obtain the code of the generic method called in the code to be tested after intercepting the calling instruction of the generic method in the code to be tested. The code of the generic method called determines the relationship between the actual return value type of the method called when the code to be tested is tested, and the required parameter type of the method called by the code to be tested, and then based on the determined relationship, Determine the actual return value type corresponding to the generic method called when testing the code to be tested, as shown in Figure 2.

Figure 2 is a schematic diagram of a method for determining the actual return value type of a generic method provided in this specification.

As can be seen from Figure 2, the terminal device can monitor the calling instructions of the method under test when the code under test is running, and then can obtain the calling instructions in the code under test before the called method is executed. The code of the generic method called, so as to conduct a generic analysis of the code of the generic method called by the code to be tested, and determine the various actual return value types of the generic method called when the code to be tested is tested, The association between the various parameter types required by the generic method called by the code under test (that is, the parameter types that need to be passed in when the code under test calls the method).

Further, the terminal device can create a MethodDescripter structure for each method data structure according to the determined association relationship (for each incoming parameter type of the generic method, the incoming parameter type corresponds to the actual The combination of return value types corresponds to a MethodDescripter structure), and then based on the intercepted calling instructions, the actual parameters passed in when the code under test calls the generic method can be determined, and based on the parameters passed in, the query can be performed in each MethodDescripter structure. The MethodDescripter structure that matches the passed-in parameter can then determine the actual return value type of the generic method called when testing the code to be tested.

Among them, the MethodDescripter structure includes: the actual return value type of the calling method, the number of times the MethodDescripter structure is called, the method name of the calling method, the class name of the calling method, the incoming parameters of the calling method, and the unique identification ID of the MethodDescripter structure.

Further, the terminal device can generate a mock method corresponding to the method called by the code to be tested based on the MethodDescripter structure that matches the incoming parameter, and then can simulate and generate the return value of the method called by the code to be tested through the mock method. To get the test results for the code to be tested.

It should be noted that since the same generic method may be called multiple times in the code to be tested, When generating the mock method corresponding to the generic method, you need to assemble the mock statements in the order in which the MethodDescripter structure is called according to the number of times the MethodDescripter structure is called, and generate the mock method.

For methods where forced type conversion occurs, the terminal device can determine that the method type from the method called by the code to be tested is mandatory by analyzing the bytecode corresponding to the code to be tested in advance. The method of type conversion is used as the target method, and the corresponding relationship between the code line number corresponding to the target method in the code to be tested and the actual return value type after forced type conversion of the return value of the target method is saved (taking into account that it is saved to The data in the hash table is easy to read, and the corresponding relationship here can be saved in the hash table).

After completing the storage of the above correspondence, the terminal device can determine the actual return value type based on the above correspondence during the code testing process. Specifically, after intercepting the calling instruction of the forced type conversion method called in the code to be tested, the method information of the calling method can be obtained. The method information here includes: the code of the calling method, and the context information of the calling method, where, The context information of the calling method includes: the variable object defined by the calling method, the scope chain of the calling method (i.e., the sequence linked list for finding variables in the calling method), the caller's calling code (i.e., the calling code of the generic method or The code of the method where the cast occurs), etc.

Further, the terminal device can determine the code line number of the method called by the code to be tested where the forced type conversion occurs based on the obtained method information of the calling method, as the target line number, and then based on the target line number, from the pre-saved code where the forced type conversion occurs The type conversion method can query the corresponding code line number in the code to be tested and the actual return value type after the forced type conversion of the return value of the method where the forced type conversion occurs. The actual return value type corresponding to the type conversion method.

Since in actual applications, when performing bytecode analysis on the code to be tested, all the forced conversion methods contained in the code to be tested may not be identified. This will lead to the possibility that during the actual code testing process, it may not be possible to use The code line number of the method in the code to be tested where forced conversion occurs, and the actual return value type corresponding to the method called by the code under test that requires forced type conversion is queried from the pre-saved correspondence.

For this situation, in this manual, the terminal device can arbitrarily select a data type from the preset type pool as a candidate return value type, and then use the candidate return value type as the code to be tested when testing. The actual return value type of the method where the forced type conversion occurs, and the test results based on the candidate return value type are obtained. Then, based on the test results, it can be judged whether the candidate return value type is the forced type called when testing the code to be tested. The actual return value type of the converted method; if not, select a return value type from the type pool again as a candidate return value type until it is determined that the candidate return value type is the one called when testing the code to be tested. to the actual return value type of the method.

The data types in the type pool in the above content may be predetermined by the terminal device before the code to be tested is run. Specifically, the terminal device can analyze the bytecode corresponding to the code to be tested and determine all the data types contained in the code to be tested. After that, the determined data types contained in the code to be tested can be saved to a predetermined data type. Set the type in the pool.

As can be seen from the above content, the terminal device can accurately determine the actual return value type of the generic method called during the running of the code under test and the method where forced type conversion occurs, so that it can Based on the determined actual return value type, the code to be tested is tested, thereby improving the accuracy of the test results.

In practical applications, the above code testing method can not only be used to test the code to be tested, but can also be used to generate test cases, that is, through the above code testing method, to build a test case that can achieve a variety of test goals (the goals here can be Refers to some preferred test cases (when the coverage of various types of code to be tested reaches a preset threshold). The method of generating test cases is described in detail below, as shown in Figure 3.

Figure 3 is a schematic flowchart of a test case generation method provided in this specification, including the following steps S301 to S304.

S301: Obtain each test case.

In this specification, the terminal device can obtain the code association information of the code to be tested before testing the code to be tested, and then generate each test case based on the code to be tested and the association information of the code to be tested, where the code association information It can be, for example, document information of the code to be tested, context information of the code to be tested, etc.

S302: For each test case, use the above code testing method to test the code to be tested and obtain the test results corresponding to the test case.

For each test case, the terminal device can run the test case through the above code testing method to test the setting code contained in the test case and obtain the test results corresponding to the test case, where the setting code It can refer to the code to be tested, or it can refer to any piece of code (for example, the code that has been tested, or it can be used as the setting code, and then by using the method of testing the setting code, some optimal test cases are finally obtained. ) The test results here refer to the testing effect of the code to be tested, such as: line coverage of the code to be tested, method coverage of the code to be tested, exception coverage of the code to be tested, etc.

The initial test cases generated by the terminal device usually cannot achieve the multiple preset test goals well. Therefore, iteration based on these initial test cases is also needed to optimize each initial test case and finally achieve the target to be tested. The test goals of the code, among which, the specific process of iterating on each test case is as follows: steps to achieve.

S303: Determine whether the preset test conditions are met based on the test results corresponding to each test case.

S304: If it is determined that the test conditions are not met, regenerate each test case, and test the code to be tested based on each regenerated test case until the test conditions are met. When the test conditions are met, the test conditions are met. Generated test cases.

The terminal device determines whether the preset test conditions are met based on the test results of each test case. If it is determined that the test conditions are not met, each test case is regenerated, and the code to be tested is tested based on the regenerated test cases until the test conditions are met. Until the test conditions are met, the test cases generated when the test conditions are met are obtained.

Among them, the preset test conditions can be formulated according to the test requirements, for example: the line coverage of the code to be tested reaches the preset threshold, and another example: the number of iterations reaches the preset threshold, etc.

In the above content, the method of regenerating each test case can be to sort the test cases according to the test results of each test case (for example, sort according to the line coverage of the code to be tested), and according to the sorted test cases , filter out each basic test case.

Further, the terminal device can select at least some basic test cases from each basic test case and combine them in pairs to obtain each test case combination, and for each test case combination, according to the test case combination, among the two basic test cases The included parameters of the same type are weighted to obtain regenerated test cases.

In addition, the terminal device can also select at least some basic test cases from each basic test case, and for each selected basic test case, numerically adjust the parameters included in the basic test case, and/or change the The code under test contained in the basic test case is adjusted to regenerate each test case.

In addition, since during the running of the test case, the generic method called for the code under test usually has multiple types of parameters that can be passed in, therefore, the terminal device can also generate parameters based on the test case during running. The MethodDescripter structure contains: the actual return value type of the calling method, the number of times the MethodDescripter structure is called, the method name of the calling method, the class name of the calling method, the type of parameters passed in by the calling method, and regenerates each test case to treat Test each incoming parameter type of the generic method called by the test code, as well as the actual return value type.

It should be noted that the above three methods can be used individually to regenerate each test case, or can be used together to regenerate test cases.

As can be seen from the above content, the terminal device can generate initial test cases for the set code and pass them through In the process of testing the set code through each initial test case, each initial test case is optimized through iteration based on the test results of each initial test case, so that the final generated test case can test the set code. Code, conduct comprehensive testing, thereby improving testing results.

The above is a code testing method provided by one or more embodiments of this specification. Based on the same idea, this specification also provides a corresponding code testing device and a test case generation device, as shown in Figures 4 and 5.

Figure 4 is a schematic diagram of a code testing device provided in this specification, including: an acquisition module 401, used to obtain the code to be tested; a determination module 402, used to determine the type of parameters required by the method called by the code to be tested. , and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested, determine the actual return value type corresponding to the method called when the code to be tested is tested, when the code to be tested is tested The method type of the called method includes: at least one of a generic method and forced type conversion; the testing module 403 is used to obtain test results for the code to be tested according to the actual return value type.

Optionally, the determination module 402 is specifically configured to obtain the code of the method called by the code to be tested; and determine the code of the method called by the code to be tested according to the obtained code of the method called by the code to be tested. The actual return value of the method called during code testing is related to the parameter type required by the method called by the code to be tested; according to the related relationship, and the parameters required by the method called by the code to be tested. Type, determine the actual return value type corresponding to the method called when testing the code to be tested.

Optionally, the test module 403 is specifically configured to create a method data structure MethodDescripter structure according to the association relationship. The MethodDescripter structure includes: the actual return value type of the calling method, the number of times the MethodDescripter structure is called, and the method of calling the method. name, the class name of the calling method, and the incoming parameters of the calling method; according to the MethodDescripter structure and the actual return value type, a mock method corresponding to the method called by the code to be tested is generated; through the mock method , to obtain the test results for the code to be tested.

Optionally, the determination module 402 is specifically configured to determine, from the methods called by the code to be tested, that the method type is a forced type conversion method by analyzing the bytecode corresponding to the code to be tested. , as the target method; when testing the code to be tested, determine the actual return value type corresponding to the method called by the code to be tested according to the target method.

Optionally, the device further includes: an analysis module 404, configured to compare the code line number corresponding to the target method in the code to be tested with the actual return value of the target method after forced type conversion. The corresponding relationship between the value types is saved; the determination module 402 is specifically used to determine if during the testing process of the code to be tested, The method called by the code to be tested is determined to be the code line number of the forced type conversion method as the target line number; according to the target line number, the code called by the code to be tested is queried from the pre-saved correspondence. The actual return value type corresponding to the method.

Optionally, the testing module 403 is specifically configured to generate a response value corresponding to the method called by the code to be tested based on querying the actual return value type corresponding to the method called by the code to be tested from the pre-saved correspondence relationship. The mock method; through the mock method, the test results for the code to be tested are obtained.

Figure 5 is a schematic diagram of a test case generation device provided in this specification, including: a use case acquisition module 501, used to obtain each test case; a use case testing module 502, used for each test case, through the above code testing method , test the set code to obtain the test results corresponding to the test case; the judgment module 503 is used to determine whether the preset test conditions are met based on the test results corresponding to each test case; the generation module 504 is used to determine whether When the test conditions are not met, each test case is regenerated, and the set code is tested according to each regenerated test case until the test condition is met, and the test generated when the test condition is met is obtained. Example.

Optionally, the generation module 504 is specifically configured to select at least some test cases from each test case and combine them in pairs to obtain each test case combination; for each test case combination, combine the two test case combinations included in the test case combination. Parameters of the same type in each test case are weighted to obtain a regenerated test case.

Optionally, the generation module 504 is specifically configured to select at least some test cases from each test case; for each selected test case, numerically adjust at least some parameters included in the test case, and/or Adjust the code to be tested contained in the test case to obtain a regenerated test case.

This specification also provides a computer-readable storage medium that stores a computer program. The computer program can be used to execute the method of code testing and test case generation provided in Figure 1 above.

This specification also provides a schematic structural diagram of the electronic device shown in FIG. 6 corresponding to FIG. 1 . As shown in Figure 6, at the hardware level, the electronic device includes a processor, internal bus, network interface, memory and non-volatile memory, and of course may also include other hardware required for business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to implement the method of code testing and test case generation described in Figure 1 above. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logical unit, and may also be hardware or logic device.

In the 1990s, improvements in a technology could clearly be distinguished from improvements in hardware (e.g., Improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method processes). However, with the development of technology, many improvements in today's method processes can be regarded as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement of a method flow cannot be implemented using hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic functions are determined by the user programming the device. Designers can program themselves to "integrate" a digital system on a PLD, instead of asking chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. Before compiling, The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL). There is not only one type of HDL, but many types, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used The most popular ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that by simply logically programming the method flow using the above-mentioned hardware description languages and programming it into the integrated circuit, the hardware circuit that implements the logical method flow can be easily obtained.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, For Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, computer examples For example, it may be a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any of these devices. Any combination of equipment.

For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and/or hardware.

Those skilled in the art will understand that embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, random access memory (RAM), and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is a computer-readable medium Qualitative examples.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

Those skilled in the art will appreciate that embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

This specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through communications networks. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

The above descriptions are only examples of this specification and are not intended to limit this specification. Various modifications and variations may occur to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of the claims of this specification.

Claims

A method of code testing, including:

Get the code to be tested;

According to the type of parameters required for the method called by the code to be tested, and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested, determine the method called when the code to be tested is tested. The actual return value type corresponding to the method. The method type of the method called when testing the code to be tested includes: at least one of a generic method and forced type conversion;

According to the actual return value type, the test result for the code to be tested is obtained.
The method of claim 1, determining the location of the method according to the type of parameters required by the method called by the code to be tested and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested. Describe the actual return value type corresponding to the method called when testing the code to be tested, including:

Obtain the code of the method called by the code to be tested;

According to the obtained code of the method called by the code under test, determine the actual return value type of the method called when the code under test is tested, and the type of parameters required by the method called by the code under test. connection relation;

According to the association relationship and the types of parameters required by the method called by the code to be tested, the actual return value type corresponding to the method called when the code to be tested is tested is determined.
The method of claim 2, obtaining test results for the code to be tested according to the actual return value type, specifically including:

According to the association relationship, a method data structure MethodDescripter structure is created. The MethodDescripter structure includes: the actual return value type of the calling method, the number of times the MethodDescripter structure is called, the method name of the calling method, the class name of the calling method, and the name of the calling method. Pass in parameters;

According to the MethodDescripter structure and the actual return value type, generate a mock method corresponding to the method called by the code to be tested;

Through the mock method, test results for the code to be tested are obtained.
The method of claim 1, determining the location of the method according to the type of parameters required by the method called by the code to be tested and/or the analysis results obtained after analyzing the bytecode corresponding to the code to be tested. Describe the actual return value type corresponding to the method called when testing the code to be tested, including:

By analyzing the bytecode corresponding to the code to be tested, it is determined that the method type is a forced type conversion method from the methods called by the code to be tested, and is used as the target method;

When testing the code to be tested, determine where the code to be tested is based on the target method. The actual return value type corresponding to the called method.
The method of claim 4, when testing the code to be tested, determining based on the target method that before the actual return value type corresponding to the method called by the code to be tested, the method also include:

Save the corresponding relationship between the code line number corresponding to the target method in the code to be tested and the actual return value type of the return value of the target method after forced type conversion;

When testing the code to be tested, determine the actual return value type corresponding to the method called by the code to be tested based on the target method, specifically including:

During the testing process of the code to be tested, the code line number of the method called by the code to be tested is determined to be a method of forced type conversion, and is used as the target line number;

According to the target line number, the actual return value type corresponding to the method called by the code to be tested is queried from the pre-saved correspondence relationship.
The method of claim 5, obtaining test results for the code to be tested according to the actual return value type, specifically including:

Generate a mock method corresponding to the method called by the code to be tested based on querying the actual return value type corresponding to the method called by the code to be tested from the pre-saved correspondence;

Through the mock method, test results for the code to be tested are obtained.
A method of test case generation, including:

Get each test case;

For each test case, test the setting code through the method described in any one of the above claims 1 to 6, and obtain the test results corresponding to the test case;

Based on the test results corresponding to each test case, determine whether the preset test conditions are met;

If it is determined that the test conditions are not met, each test case is regenerated, and the set code is tested according to each regenerated test case until the test conditions are met, and the generated code generated when the test conditions are met is obtained. Test cases.
According to the method of claim 7, regenerating each test case specifically includes:

Select at least some test cases from each test case and combine them in pairs to obtain each test case combination;

For each test case combination, the parameters of the same type in the two test cases included in the test case combination are weighted to obtain a regenerated test case.
According to the method of claim 7, regenerating each test case specifically includes:

Select at least some test cases from each test case;

For each selected test case, numerically adjust at least some of the parameters included in the test case, and/or adjust the code to be tested included in the test case to obtain a regenerated test case.
A device for code testing, including:

Obtain module, used to obtain the code to be tested;

Determining module, configured to determine the location of the code under test based on the type of parameters required by the method called by the code under test and/or the analysis results obtained after analyzing the bytecode corresponding to the code under test. The actual return value type corresponding to the method called during testing. The method type of the method called when testing the code to be tested includes: at least one of a generic method and forced type conversion;

A testing module, configured to obtain test results for the code to be tested based on the actual return value type.
The device according to claim 10, the determining module is specifically configured to obtain the code of the method called by the code to be tested; and determine the code of the method called by the code to be tested based on the obtained code. The actual return value of the method called when the code to be tested is tested, and the relationship between the parameter types required by the method called by the code to be tested; according to the relationship, and the method called by the code to be tested The type of required parameters determines the actual return value type corresponding to the method called when testing the code to be tested.
The device according to claim 11, the test module is specifically configured to create a method data structure MethodDescripter structure according to the association relationship, the MethodDescripter structure includes: the actual return value type of the calling method, the number of times the MethodDescripter structure is called , the method name of the calling method, the class name of the calling method, and the incoming parameters of the calling method; according to the MethodDescripter structure and the actual return value type, generate a mock method corresponding to the method called by the code to be tested; Through the mock method, test results for the code to be tested are obtained.
The device according to claim 10, the determination module is specifically configured to determine that the method type from the method called by the code to be tested is mandatory by analyzing the bytecode corresponding to the code to be tested. The method of type conversion serves as the target method; when testing the code to be tested, the actual return value type corresponding to the method called by the code to be tested is determined according to the target method.
The device of claim 13, further comprising:

An analysis module, configured to save the corresponding relationship between the code line number corresponding to the target method in the code to be tested and the actual return value type of the return value of the target method after forced type conversion;

The determination module is specifically configured to determine, during the testing process of the code to be tested, the code line number in which the method called by the code to be tested is a forced type conversion method, as the target line number; according to the target line number number, and query the actual return value type corresponding to the method called by the code to be tested from the pre-saved correspondence relationship.
The device according to claim 14, the test module is specifically configured to: according to the pre-saved corresponding The actual return value type corresponding to the method called by the code to be tested is queried in the relationship, and a mock method corresponding to the method called by the code to be tested is generated; through the mock method, a test for the code to be tested is obtained result.
A device for generating test cases, including:

The use case acquisition module is used to obtain each test case;

The use case testing module is used to test the setting code for each test case through the method described in any one of the above claims 1 to 6, and obtain the test results corresponding to the test case;

The judgment module is used to determine whether the preset test conditions are met based on the test results corresponding to each test case;

A generation module, configured to regenerate each test case when it is determined that the test conditions are not met, and test the set code based on the regenerated test cases until the test conditions are met, and all test cases are obtained. Test cases generated when describing test conditions.
The device according to claim 16, the generating module is specifically configured to select at least some test cases from each test case and combine them in pairs to obtain each test case combination; for each test case combination, combine the test case combinations The parameters of the same type in the two test cases contained in are weighted to obtain a regenerated test case.
The device according to claim 16, the generating module is specifically configured to select at least some test cases from each test case; for each selected test case, perform numerical adjustment on at least some parameters contained in the test case. , and/or adjust the code to be tested contained in the test case to obtain a regenerated test case.
A computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the method described in any one of claims 1 to 9 is implemented.
An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the method of any one of claims 1 to 9 is implemented.