CN114996152A - Unit testing method, device, equipment and medium - Google Patents

Abstract

The embodiments of the present disclosure relate to a unit testing method, device, equipment and medium, wherein the method includes: acquiring basic data of a unit test case; expressing the basic data in a preset format to obtain target data; , after supplementing the context information based on the target data, a unit test case is generated, and a unit test is performed on the software under test based on the unit test case. By adopting the above technical solution, by acquiring the basic data required by the unit test case and expressing the basic data in a preset format, a complete unit test case can be generated and executed based on the basic data in the preset format during the software running process, and the unit test can be executed. During iteration and maintenance, it is only necessary to iterate and maintain the basic data of the unit test case without modifying the code, which greatly reduces the iteration and maintenance cost of the unit test case, thereby improving the coverage and quality of the unit test. Software iteration speed.

Description

A unit testing method, device, equipment and medium

technical field

The present disclosure relates to the technical field of software testing, and in particular, to a unit testing method, apparatus, device and medium.

Background technique

Unit testing can find software defects in the pre-development stage, and can find problems in the early stage of the software development process, ensure the quality of software development, avoid online accidents, and reduce the cost of solving problems. Therefore, unit testing is a very important part of the testing process. important step.

Unit testing generally requires manually writing code and designing unit test cases, and when the software code changes, the code of the unit test cases needs to be modified, and the cost of writing and maintaining is relatively high. In related technologies, unit test cases can be automatically generated at the code level, but the iteration and maintenance of unit test cases still need to be implemented by modifying the code, which requires a lot of manpower and still has the defect of high cost.

SUMMARY OF THE INVENTION

In order to solve the above technical problems, the present disclosure provides a unit testing method, apparatus, device and medium.

An embodiment of the present disclosure provides a unit testing method, the method includes:

Get the basic data of unit test cases;

The basic data is represented in a preset format to obtain target data;

During the running of the software under test, the unit test case is generated after supplementing the context information based on the target data, and the unit test is performed on the software under test based on the unit test case.

Embodiments of the present disclosure also provide a unit testing device, the device comprising:

Get module, used to get the basic data of unit test case;

a format module for representing the basic data in a preset format to obtain target data;

The testing module is used for generating the unit test case after supplementing the context information based on the target data during the running of the software under test, and performing unit testing on the software under test based on the unit test case.

An embodiment of the present disclosure further provides an electronic device, the electronic device includes: a processor; a memory for storing instructions executable by the processor; the processor for reading the memory from the memory The instructions are executable, and the instructions are executed to implement the unit testing method provided by the embodiments of the present disclosure.

An embodiment of the present disclosure further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is used to execute the unit testing method provided by the embodiment of the present disclosure.

Compared with the prior art, the technical solution provided by the embodiment of the present disclosure has the following advantages: the unit testing solution provided by the embodiment of the present disclosure obtains the basic data of the unit test case; expresses the basic data in a preset format to obtain the target data; During the running of the software under test, a unit test case is generated after supplementing the context information based on the target data, and the unit test is performed on the software under test based on the unit test case. With the above technical solution, by acquiring the basic data required by the unit test case and expressing the basic data in a preset format, a complete unit test case can be generated after supplementing the contextual environment information based on the basic data in the preset format during the software running process And execute unit tests. During iteration and maintenance, it is only necessary to iterate and maintain the basic data of unit test cases without modifying the code, which greatly reduces the iteration and maintenance costs of unit test cases, thereby improving the coverage of unit tests. and quality, improving the iteration speed of the software.

Description of drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent when taken in conjunction with the accompanying drawings and with reference to the following detailed description. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

1 is a schematic flowchart of a unit testing method provided by an embodiment of the present disclosure;

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

3 is a schematic diagram of a unit test provided by an embodiment of the present disclosure;

4 is a schematic structural diagram of a unit testing apparatus provided by an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Detailed ways

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for the purpose of A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes, and are not intended to limit the protection scope of the present disclosure.

It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and/or in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this regard.

As used herein, the term "including" and variations thereof are open-ended inclusions, ie, "including but not limited to". The term "based on" is "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below.

It should be noted that concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or interdependence.

It should be noted that the modifications of "a" and "a plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, they should be understood as "one or a plurality of". multiple".

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are only for illustrative purposes, and are not intended to limit the scope of these messages or information.

Unit testing generally requires manually writing code and designing unit test cases. When the code design is complex, the code needs to be refactored before the unit test code is written. In addition, the original code needs to be modified to modify the unit test code. The maintenance cost is high, and the rapid demand Iterative conflict. For example, taking the native test suite XCTest provided by the IOS system as an example, in the process of writing and maintaining unit test cases, developers need to provide context for unit test cases, declare and construct input and output variables, call test methods, and compare outputs. As a result, developers often only care about the input and output of the method under test, but not how these input variables are constructed and how the method is called. Therefore, the current solution inevitably needs to write a lot of redundant code. This redundancy Code inevitably increases the cost of writing and maintaining unit test cases. In addition, at present, unit test cases need to be specially written and maintained by developers. In the process of rapid iteration of software requirements, in order to ensure high-quality unit tests, the iteration and maintenance of unit test cases requires a lot of manpower, which becomes blocking rapid iteration. stumbling block. In related technologies, unit test cases can be automatically generated at the code level, but the iteration and maintenance of unit test cases still need to be implemented by modifying the code, which requires a lot of manpower and still has the defect of high cost.

In order to solve the above problem, an embodiment of the present disclosure provides a unit testing method, which is described below with reference to specific embodiments.

1 is a schematic flowchart of a unit testing method provided by an embodiment of the present disclosure. The method may be executed by a unit testing apparatus, where the apparatus may be implemented by software and/or hardware, and may generally be integrated into an electronic device. As shown in Figure 1, the method includes:

Step 101: Acquire basic data of the unit test case.

Among them, a unit test case can be understood as a code or a specific collection for the specific functions of the software unit, in order to effectively verify the characteristics of the software unit and discover the defects of the software unit code. Test purpose, input data, expected results, etc. Software units can be functions, methods, modules, etc. that make up the software. A software usually consists of a plurality of the above-mentioned software units. Each software unit realizes its own determined function and communicates with other software units through the input and output interfaces provided by it. Call to realize the overall function of the software together. The unit testing method of the embodiment of the present disclosure may be executed by a unit test suite, and the unit test suite may be understood as a comprehensive functional module capable of unit testing one or more softwares.

The basic data may be the necessary data required by the unit test case when testing, and also the data that the developer cares about for the unit test case. In the embodiment of the present disclosure, the basic data may include the name of the unit test method, class information, test object, input Parameters and output expected results; class information can be the class to which the unit test method belongs. The class information is available when the code language of the software under test is Objective-C code language, and can be adapted to be modified when the code language of the software under test is other languages. Other functions or upper-level modules; the test object can be the object that calls the unit test method, the input parameters correspond to the input variables of the specific software unit, and the output expected results correspond to the output variables of the software unit.

In some embodiments, acquiring the basic data of the unit test case may include at least one of the following: collecting the software operation data of the software under test through a collection module, and analyzing the software operation data to obtain the basis of the unit test case data; based on the basic data of the existing unit test case of the software to be tested, use a heuristic algorithm to generate the basic data of the unit test case; in response to the user's input operation, obtain the basic data of the unit test case.

The acquisition module may be a functional module for collecting software operation data, and is set in the unit test suite. The software operation data may be data generated by different software units during the daily operation of the software, and the specific data type is not limited. The heuristic algorithm can be an algorithm constructed based on intuition or experience, which provides a feasible solution for each instance of the combinatorial optimization problem to be solved under acceptable computing time and space, and can be generated by the heuristic algorithm in the embodiment of the present disclosure. The basic data of the new unit test case may include multiple heuristic algorithms, and the embodiment of the present disclosure is not limited. For example, the heuristic algorithm may include a genetic algorithm, a simulated annealing algorithm, an ant colony algorithm, and the like.

When the unit testing device obtains the basic data of the unit test case, one method can collect the software operation data of the software under test through the acquisition module, and obtain the basic data of the unit test case by analyzing the software operation data, for example, in Objective-C language. Taking the software under test as an example, the acquisition module can be the hook objc_msgSend function, which collects the registers and stack context data of the OC method, and parses the context data to obtain the actual parameter list and results of the OC method, that is, the basic data of the unit test case; /C++ and other static languages can achieve a similar effect through instrumentation; another method can be based on the basic data of the existing unit test cases of the software under test, using a heuristic algorithm to generate the basic data of new unit test cases For example, taking the heuristic algorithm as the genetic algorithm as an example, the basic data of each existing unit test case is regarded as a gene segment, and the coverage rate is used as the fitness. The basic data of new unit test cases is continuously generated; another way can respond to the user's input operation to obtain the basic data of the unit test case input by the user. The user is the developer, that is, the developer can manually enter the unit test case. The basic data of , the specific input method is not limited, for example, it can be directly written by the developer, or input through a preset interactive system.

The above three methods can all realize the acquisition of basic data of unit test cases, which improves the efficiency and diversity of basic data acquisition.

Step 102: Represent the basic data in a preset format to obtain target data.

The preset format may be a general data specification or data format, and the preset format in the embodiment of the present disclosure may be a readable data format, that is, the readability is strong, which is helpful for maintaining and Iteration, the specific format of the preset format can be set according to the actual situation, and the specific format is not limited. For example, the preset format can be set to JSON format or table format. The target data can be converted into basic data in a preset format, and the target data supports at least one of the following operations: adding, deleting, and modifying.

In the embodiment of the present disclosure, after acquiring the basic data of the unit test case, the unit testing apparatus may use a preset format to represent the basic data to obtain corresponding target data.

Exemplarily, when the preset format is JSON format, the target data can be represented as follows:

{

In this solution, the basic data of the unit test case is represented in a preset format. On the one hand, because the general data storage format is convenient to store in the database, for example, when the default format is JSON format, many non-relational databases based on document storage support JSON format is used as its data storage format, such as MongoDB, CouchDB, RavenDB, etc.; on the other hand, based on target data in preset formats, such as target data based on JSON format, all test cases belonging to classes and methods can be quickly retrieved, which is convenient for selection. Locally unit tests certain classes and methods.

Step 103 , in the process of running the software under test, generate a unit test case after supplementing the context environment information based on the target data, and perform a unit test on the software under test based on the unit test case.

The software to be tested may be any software that needs to be unit tested, and the type and quantity of the software to be tested are not limited in the embodiments of the present disclosure.

In the embodiment of the present disclosure, the unit testing device can run the software to be tested after expressing the basic data in a preset format, obtain and store the target data, and automatically according to the software to be tested during the running process of the software to be tested. The language feature obtains the corresponding target data, and supplements the context information required by the unit test by parsing the target data to generate a complete unit test case, and executes the unit test method of each software unit to obtain the output test result, and then according to the target data. The expected output results are compared with the output test results to determine whether they meet the expectations, and the unit test results are obtained.

The unit testing solution of the present disclosure can be a code-free automatic execution unit testing solution, which can automatically obtain basic data in a preset format and generate unit test cases during the software running process. The writing and maintenance costs of test cases help developers save manpower and improve unit test coverage and quality.

The unit testing solution provided by the embodiment of the present disclosure obtains the basic data of the unit test case; expresses the basic data in a preset format to obtain the target data; in the process of running the software under test, the unit is generated after supplementing the contextual environment information based on the target data Test cases, and perform unit testing of the software under test based on the unit test cases. With the above technical solution, by acquiring the basic data required by the unit test case and expressing the basic data in a preset format, a complete unit test case can be generated after supplementing the contextual environment information based on the basic data in the preset format during the software running process And execute unit tests. During iteration and maintenance, it is only necessary to iterate and maintain the basic data of unit test cases without modifying the code, which greatly reduces the iteration and maintenance costs of unit test cases, thereby improving the coverage of unit tests. and quality, improving the iteration speed of the software.

Exemplarily, FIG. 2 is a schematic flowchart of another unit testing method provided by an embodiment of the present disclosure. As shown in FIG. 2 , in a feasible implementation manner, when the code language of the software to be tested is a dynamic call type, The context information includes temporary variables, and the above step 103 may include the following steps:

Step 201: Acquire and parse the target data, and obtain the parameter type of the test object, the parameter type of the input parameter, and the parameter value.

Among them, the code language of the software under test is a dynamic call type, which means that functions, methods, etc. in the code of the software under test can dynamically call each other. For example, the Objective-C language and the Python language belong to the dynamic call type. The test object can be the object that calls the unit test method, and also belongs to a kind of parameter; the input parameter corresponds to the input variable of the specific software unit.

When the unit testing device generates a unit test case after supplementing the context information based on the target data during the running of the software to be tested, it can first determine whether the code language of the software to be tested is a dynamic call type, and if so, it can retrieve the data from the database based on the language characteristics. Obtain the required target data, that is, obtain and parse the target data based on functions in the code language, etc., and obtain the parameter type of the test object, the parameter type of the input parameter, and the parameter value for later use. For example, when the code language is the Objective-C language as an example, the target data can be obtained and parsed based on the NSInvocation class of the Objective-C language.

Step 202 , construct a corresponding first temporary variable based on the parameter type of the test object, and construct a second temporary variable of the input parameter based on the parameter type and parameter value of the input parameter.

Among them, the temporary variable can be a variable required when the unit test is executed. When the software is executed, a piece of memory needs to be allocated in the memory to store the parameters during the test. The temporary variable can be a variable corresponding to this piece of memory, and the above construction context environment The meaning is to construct a temporary variable. The temporary variables may include a first temporary variable and a second temporary variable. The first temporary variable may refer to the temporary variable of the test object, and the second temporary variable may be the temporary variable of the input parameter, which is distinguished by the first and the second.

Specifically, the unit testing device can construct a corresponding first temporary variable according to the parameter type of the test object, and can construct a corresponding second temporary variable according to the parameter type and parameter value of the input parameter, and the construction method can adopt related technologies, for example, when If the parameter type of the test object is of type int, you can construct an int variable.

Step 203: Determine the combination of the first temporary variable, the second temporary variable, and the name, class information, and output expected result of the unit test method extracted from the target data as a unit test case.

Step 204: Use the first temporary variable and the second temporary variable as actual parameters of the unit test method, execute the unit test method based on the name and class information of the unit test method, and obtain an output test result.

Among them, the actual parameter can be understood as the parameter transmitted when the function or method is called, and the actual parameter can be constant, variable, expression, etc. The output test result can be a result obtained by the current test.

Specifically, after generating the unit test case, the unit test apparatus may use the above-mentioned first temporary variable and second temporary variable as the actual parameters of the unit test method when the unit test is performed on the software to be tested based on the unit test case. The name and class information are obtained from the unit test method, and parameters are automatically passed to the unit test method and executed, and the output test result is obtained.

Step 205: Compare the output test result with the output pre-start result to obtain the unit test result.

Wherein, the unit test result may be a result that characterizes whether the unit test meets the expectations.

In the embodiment of the present disclosure, after obtaining the output test result, the unit testing apparatus can compare the output expected result in the target data with the output test result to determine whether it meets the expectation, and then obtain the unit test result.

In the above solution, for the code language of the dynamic call type, the context information required by the unit test can be automatically supplemented based on the language characteristics, the unit test is executed to collect the results, the unit test efficiency is improved, and the writing and maintenance cost of the unit test case can be reduced.

In some embodiments, when the code language of the software under test is a non-dynamic calling type, and the context information is the context code, during the running of the software under test, the unit test case is generated after supplementing the context information based on the target data, and Performing a unit test on the software under test based on the unit test case may include: converting target data into code format data corresponding to the code language of the software under test through a preset conversion module, and adding a contextual environment code generation code to the code format data Format unit test cases, and assemble and embed the code format unit test cases into the code of the software under test; during the running process of the software under test, unit tests are performed based on the code format unit test cases.

Among them, the code language of the software under test is a non-dynamic calling type, which means that the functions and methods in the code of the software under test do not support dynamic calling. For example, C language and C++ language are all non-dynamic calling types. The preset conversion module can be a functional module used to perform language conversion on target data and supplement the context code to generate unit test cases. It is set for the software under test whose code language is a non-dynamic call type. For example, it can be a black box function module, which does not affect the maintenance of unit test cases by developers.

Specifically, when the code language of the software to be tested is of a non-dynamic calling type, the unit testing device can convert the target data into data in the same code language as the code language of the software to be tested or the code format data of the intermediate code through a preset preset conversion module, and Add context code to the code format data to obtain unit test cases in code format, assemble the algorithm of the code of the software under test, and temporarily embed the unit test cases in code format into the software, so that during the running process of the software under test , to automatically execute unit tests based on unit test cases in this code format.

In the above solution, for the non-dynamic calling type code language, the unit test case in the form of code can be automatically generated by the conversion module and encapsulated in the code of the software to be tested.

For non-dynamic languages, a scheme can be designed to automatically generate test code based on the input and output of test cases. Test case writers can only care about the input and output of test cases without caring about test code. The automatically generated test code is encapsulated internally, and only the basic data of the unit test case needs to be iterated and maintained during iteration and maintenance, without the need to modify the code, which reduces the iteration and maintenance cost of the unit test case.

Next, the unit testing method of the embodiment of the present disclosure will be further described through a specific example. Exemplarily, FIG. 3 is a schematic diagram of a unit test provided by an embodiment of the present disclosure. As shown in FIG. 3 , a complete unit test process is shown in the figure, and the unfilled part in the figure indicates that the manual intervention of the developer is required. Process, the part with gray fill indicates the process that can be automated, which can include: acquisition of basic data of unit test cases, which can be acquired in three ways in the figure, including: developer input, collection of software operation data and analysis, and inspiration After that, the target data obtained from the basic data can be stored in the unit test case database in the unit test case database; for the software under test that needs to be unit tested, in the process of running the software under test, The target data can be automatically obtained, and the unit test cases generated after supplementing the contextual environment information based on the target data regularly and automatically perform unit tests on the software under test; calculate the pass rate of the unit test cases according to the collected unit test results of each unit test case , to collect the code coverage of unit test execution; after the unit test is executed, software developers can check the unit test cases that fail to execute, evaluate whether they meet the requirements of the new software version, and finally can evaluate the software according to the pass rate of the unit test cases. quality is assessed.

In this solution, by providing a code-free automated unit test suite, the basic data of unit test cases is generated by automatically collecting online software operation data, and combined with the generation of random basic data and manual partial input based on heuristic algorithm, it can comprehensively cover The basic data required by the unit test case, and then automatically supplement the context information to generate the unit test case and execute the unit test. For the developer, the unit test only needs to be entered based on the agreed format. There is no need to write unit test code and rely on native The code test suite reduces the cost of writing unit test cases, and has the ability to automatically generate unit test cases. During iteration and maintenance, only the basic data of the unit test cases need to be iterated and maintained, without the need to modify the code, which can effectively save units The manpower and material resources of test case maintenance and iteration personnel greatly reduce the iteration and maintenance costs of unit test cases, which can effectively improve the coverage and quality of software unit testing, and effectively ensure software quality.

FIG. 4 is a schematic structural diagram of a unit testing apparatus provided by an embodiment of the present disclosure. The apparatus may be implemented by software and/or hardware, and may generally be integrated into an electronic device. As shown in Figure 4, the device includes:

an acquisition module 401, used for acquiring basic data of a unit test case;

a format module 402, configured to represent the basic data in a preset format to obtain target data;

The testing module 403 is configured to generate the unit test case after supplementing the context information based on the target data during the running process of the software under test, and perform unit testing on the software under test based on the unit test case.

Optionally, the obtaining module 401 includes at least one of the following:

The first unit is used to collect the software operation data of the software to be tested through the acquisition module, and analyze the software operation data to obtain the basic data of the unit test case;

The second unit is used to generate the basic data of the unit test case by adopting a heuristic algorithm based on the basic data of the existing unit test case of the software to be tested;

The third unit is configured to acquire the basic data of the unit test case in response to the user's input operation.

Optionally, the basic data includes the name of the unit test method, class information, test objects, input parameters, and output expected results.

Optionally, when the code language of the software under test is a dynamic call type, the context information includes a temporary variable, and the test module 403 includes a generating unit for:

Obtain and parse the target data, and obtain the parameter type of the test object, the parameter type of the input parameter and the parameter value;

A corresponding first temporary variable is constructed based on the parameter type of the test object, and a second temporary variable of the input parameter is constructed based on the parameter type and parameter value of the input parameter, and the temporary variable includes the first temporary variable variable and the second temporary variable;

Determining a combination of the first temporary variable, the second temporary variable, the name of the unit test method extracted from the target data, the class information, and the expected output result as the unit test case .

Optionally, the test module 403 includes an execution unit for:

The first temporary variable and the second temporary variable are used as the actual parameters of the unit test method, and the unit test method is executed based on the name of the unit test method and the class information to obtain an output test result;

The output test result is compared with the output pre-start result to obtain a unit test result.

Optionally, when the code language of the software under test is a non-dynamic calling type, the context information is a context code, and the test module 403 is used for:

The target data is converted into the code format data corresponding to the code language of the software to be tested by the preset conversion module, and the context environment code is added to the code format data to generate a unit test case in the code format, and the code The unit test case assembly in the format is embedded in the code of the software to be tested;

During the running process of the software under test, a unit test is performed based on the unit test case in the code format.

Optionally, the preset format is a readable data format, and the target data supports at least one of the following operations: adding, deleting, and modifying.

The unit testing apparatus provided by the embodiment of the present disclosure can execute the unit testing method provided by any embodiment of the present disclosure, and has functional modules and beneficial effects corresponding to the execution method.

An embodiment of the present disclosure also provides a computer program product, including a computer program/instruction, when the computer program/instruction is executed by a processor, the unit testing method provided by any embodiment of the present disclosure.

FIG. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. Referring specifically to FIG. 5 below, it shows a schematic structural diagram of an electronic device 500 suitable for implementing an embodiment of the present disclosure. The electronic device 500 in the embodiment of the present disclosure may include, but is not limited to, such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), an in-vehicle terminal ( For example, mobile terminals such as car navigation terminals) and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in FIG. 5 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 5 , an electronic device 500 may include a processing device (eg, a central processing unit, a graphics processor, etc.) 501 that may be loaded into random access according to a program stored in a read only memory (ROM) 502 or from a storage device 508 Various appropriate actions and processes are executed by the programs in the memory (RAM) 503 . In the RAM 503, various programs and data necessary for the operation of the electronic device 500 are also stored. The processing device 501 , the ROM 502 , and the RAM 503 are connected to each other through a bus 504 . An input/output (I/O) interface 505 is also connected to bus 504 .

Typically, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speakers, vibration An output device 507 such as a computer; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509 . Communication means 509 may allow electronic device 500 to communicate wirelessly or by wire with other devices to exchange data. While FIG. 5 shows electronic device 500 having various means, it should be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication device 509 , or from the storage device 508 , or from the ROM 502 . When the computer program is executed by the processing device 501, the above-mentioned functions defined in the unit testing method of the embodiment of the present disclosure are executed.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, electrical wire, optical fiber cable, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the client and server can communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and can communicate with digital data in any form or medium (eg, a communications network) interconnected. Examples of communication networks include local area networks ("LAN"), wide area networks ("WAN"), the Internet (eg, the Internet), and peer-to-peer networks (eg, ad hoc peer-to-peer networks), as well as any currently known or future development network of.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or may exist alone without being assembled into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device: acquires the basic data of the unit test case; represents the basic data in a preset format , to obtain target data; in the process of running the software under test, the unit test case is generated after supplementing the context information based on the target data, and the unit test is performed on the software under test based on the unit test case.

Computer program code for performing operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and This includes conventional procedural programming languages - such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (eg, using an Internet service provider through Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented in a software manner, and may also be implemented in a hardware manner. Among them, the name of the unit does not constitute a limitation of the unit itself under certain circumstances.

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), Systems on Chips (SOCs), Complex Programmable Logical Devices (CPLDs) and more.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with the instruction execution system, apparatus or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of the disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, and should also cover, without departing from the above-mentioned disclosed concept, the technical solutions formed by the above-mentioned technical features or Other technical solutions formed by any combination of its equivalent features. For example, a technical solution is formed by replacing the above features with the technical features disclosed in the present disclosure (but not limited to) with similar functions.

Additionally, although operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although the above discussion contains several implementation-specific details, these should not be construed as limitations on the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or logical acts of method, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims (10)

1. A method of unit testing, comprising:

acquiring basic data of a unit test case;

expressing the basic data by adopting a preset format to obtain target data;

and in the running process of the software to be tested, generating the unit test case after supplementing context environment information based on the target data, and executing unit test on the software to be tested based on the unit test case.

2. The method of claim 1, wherein obtaining the base data of the unit test case comprises at least one of:

acquiring software running data of the software to be tested through an acquisition module, and analyzing the software running data to obtain basic data of the unit test case;

generating basic data of the unit test cases by adopting a heuristic algorithm based on the basic data of the existing unit test cases of the software to be tested;

and responding to the input operation of the user, and acquiring basic data of the unit test case.

3. The method of claim 1, wherein the base data includes a name of a unit test method, class information, a test object, input parameters, and an output expected result.

4. The method of claim 3, wherein when the code language of the software under test is a dynamic call type, the context information includes a temporary variable, and generating a unit test case after supplementing the context information based on the target data comprises:

acquiring and analyzing the target data to acquire the parameter type of the test object, the parameter type of the input parameter and the parameter value;

constructing a corresponding first temporary variable based on the parameter type of the test object, and constructing a second temporary variable of the input parameter based on the parameter type and the parameter value of the input parameter, wherein the temporary variable comprises the first temporary variable and the second temporary variable;

and combining the first temporary variable, the second temporary variable, the name of the unit test method extracted from the target data, the class information and the output expected result to determine the unit test case.

5. The method of claim 4, wherein performing unit testing on the software under test based on the unit test cases comprises:

taking the first temporary variable and the second temporary variable as actual parameters of the unit testing method, and executing the unit testing method based on the name of the unit testing method and the class information to obtain an output testing result;

and comparing the output test result with the output pre-starting result to obtain a unit test result.

6. The method of claim 1, wherein when the code language of the software to be tested is a non-dynamic call type, and the context environment information is context environment code, in a process of running the software to be tested, generating the unit test case after supplementing the context environment information based on the target data, and performing unit test on the software to be tested based on the unit test case includes:

converting the target data into code format data corresponding to the code language of the software to be tested through a preset conversion module, adding context environment codes into the code format data to generate unit test cases in a code format, and compiling the unit test cases in the code format to be embedded into the codes of the software to be tested;

and executing unit test based on the unit test case of the code format in the running process of the software to be tested.

7. The method according to any one of claims 1-6, wherein the predetermined format is a data format with readability, and the target data supports at least one of: addition, deletion and modification.

8. A unit testing apparatus, comprising:

the acquisition module is used for acquiring basic data of the unit test case;

the format module is used for representing the basic data by adopting a preset format to obtain target data;

and the test module is used for generating the unit test case after supplementing the context environment information based on the target data in the running process of the software to be tested, and testing the unit execution unit of the software to be tested based on the unit test case.

9. An electronic device, characterized in that the electronic device comprises:

a processor;

a memory for storing the processor-executable instructions;

the processor is configured to read the executable instructions from the memory and execute the instructions to implement the unit testing method of any of claims 1-7.

10. A computer-readable storage medium, characterized in that the storage medium stores a computer program for performing the unit testing method of any of the preceding claims 1-7.

Images