CN111008147B - Application program testing method, terminal and computer readable storage medium - Google Patents

Abstract

The invention discloses a test method of an application program, which comprises the following steps: when a loading instruction of a program to be tested is detected, acquiring calling information of the program to be tested; when the call information is matched with preset assertion call information, loading an assertion detection mark into a target program corresponding to the call information; and generating a test report according to the call information and the assertion detection identification. The invention also provides a terminal and a computer readable storage medium. According to the method for testing the application program, the call information of the program to be tested is obtained, the call information is matched with the preset assertion call information to realize the assertion positioning of the program to be tested to determine the target program, the assertion detection mark is added into the target program to mark the assertion, and the test report generated by checking the call information of the program to be tested and the assertion detection mark is convenient for a tester to check whether the program to be tested is provided with the assertion or not so as to evaluate the test effect of the program to be tested.

Description

Test methods, terminals and computer-readable storage media for application programs

Technical field

The present invention relates to the field of testing technology, and in particular, to an application testing method, a terminal and a computer-readable storage medium.

Background technique

The basic criterion for measuring the quality of automated test cases is whether there are assertions in the automated test cases. Unit testing usually includes assertion verification, that is, verifying the return value of the code under test to determine whether the code under test is correct. The so-called assertions refer to some assumptions made by programmers when writing code. Assertions are used to capture these assumptions in the code, so assertions can be regarded as an advanced form of exception handling.

Currently, in the Internet industry, it is very common for programmers to choose not to write assertions but to print the return value directly. In a large software, most unit tests do not make complete assertions, which results in some program defects not being detected. There are even thousands of unit test cases that have no assertions, which seriously affects the testing effect of automated test cases.

The above content is only used to assist in understanding the technical solution of the present invention, and does not represent an admission that the above content is prior art.

Contents of the invention

The main purpose of the present invention is to provide an application program testing method, a terminal and a computer-readable storage medium, aiming to solve the problem that the unit test case does not have an assertion set and the tested program cannot be detected, thus affecting the test effect.

In order to achieve the above object, the present invention provides an application testing method. The steps of the application testing method include:

When detecting the loading instruction of the program to be tested, obtain the calling information of the program to be tested;

When the calling information matches the preset assertion calling information, load the assertion detection identification into the target program corresponding to the calling information;

Generate a test report based on the calling information and the assertion detection identification.

Optionally, before the step of generating a test report according to the call information and the assertion detection identification, the step includes:

Execute the program to be tested;

When the return value of the execution result of the target program is obtained, the assertion detection flag is set to assertion executed; or

When the return value of the execution result of the target program is not obtained, the assertion detection flag is set to assertion not executed.

Optionally, when the return value of the execution result of the target program is obtained, the step of setting the assertion detection flag to assertion executed includes:

When obtaining the return value of the execution result of the target program, compare the return value of the execution result of the target program with a preset expected value;

When the return value matches the preset expected value, a prompt message that meets the test requirements is output;

The assertion detection flag is set to assertion executed.

Optionally, the step of generating a test report based on the call information and the assertion detection identification includes:

Generate a test report based on the calling information, the execution result of the target program, and the assertion detection identification.

Optionally, the step of generating a test report based on the call information and the assertion detection identification includes:

Output the test report.

Optionally, the preset assertion calling information includes default assertion calling information and customized assertion calling information.

In addition, to achieve the above object, the present invention also provides a terminal. The terminal includes: a memory, a processor, and a test program of an application program stored in the memory and capable of running on the processor. The application program has When the test program is executed by the processor, the steps of the test method of the above-mentioned application program are implemented.

In addition, in order to achieve the above object, the present invention also provides a computer-readable storage medium. The computer-readable storage medium stores a test program of the application program. When the test program of the application program is executed by the processor, the test of the above-mentioned application program is realized. Method steps.

The application testing method proposed by the present invention obtains the calling information of the program to be tested, and when the calling information matches the preset assertion calling information, that is, the assertion in the program to be tested is located to determine the target program where the assertion is located. Add the assertion detection flag to the target program to mark assertions. By viewing the call information of the program under test and the test report generated by the assertion detection flag, the tester can easily know at a glance whether the program under test sets assertions so as to evaluate the testing effect of the program under test. , improve the testing quality of the program to be tested.

Description of drawings

Figure 1 is a schematic diagram of the hardware structure of a terminal for implementing various embodiments of the present invention;

Figure 2 is a schematic flow chart of the first embodiment of the application testing method of the present invention;

Figure 3 is a schematic flow chart of a second embodiment of the application testing method of the present invention;

FIG. 4 is a schematic flowchart of a third embodiment of the application testing method of the present invention.

The realization of the purpose, functional features and advantages of the present invention will be further described with reference to the embodiments and the accompanying drawings.

Detailed ways

It should be understood that the specific embodiments described here are only used to explain the present invention and are not intended to limit the present invention.

In the following description, suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present invention and have no specific meaning in themselves. Therefore, "module", "component" or "unit" may be used interchangeably.

Terminals can be implemented in various forms. For example, the terminal devices described in the present invention may include terminals such as mobile phones, tablet computers, notebook computers, and PDAs.

Those skilled in the art will understand that, in addition to being specifically used for mobile-purpose elements, the construction according to embodiments of the present invention can also be applied to fixed-type terminals.

Please refer to FIG. 1 , which is a schematic diagram of the hardware structure of a terminal that implements various embodiments of the present invention. The terminal may include: a memory 101, a processor 102, and a display unit 103. Those skilled in the art can understand that the terminal structure shown in Figure 1 does not constitute a limitation on the mobile terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange different components.

Among them, the memory 101 stores test programs of the central control system and application programs. The processor 102 is the control center of the terminal. The processor 102 executes the application testing program stored in the memory 101 to implement the steps of each embodiment of the application testing method of the present invention.

The display unit 103 includes a display panel, which can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc., and is used to output the test program of the display application to be processed. 102 Test results after execution.

The present invention provides a method for testing an application program. Please refer to FIG. 2 . FIG. 2 is a schematic flow chart of a first embodiment of the method for testing an application program according to the present invention. In this embodiment, the application testing method includes the following steps:

Step S10: When the loading instruction of the program to be tested is detected, the calling information of the program to be tested is obtained;

The basic criterion for measuring the quality of automated test cases is whether there are assertions in the automated test cases. Unit test procedures usually include assertion verification, where unit test procedures refer to test procedures that check and verify the smallest testable unit in the software, for example: Take a program developed in JAVA language as an example. Methods, functions, etc. are the smallest testable units. It should be noted that the program to be tested is the test case in the automated test project, and the tester can determine whether the application software or software system is working correctly based on the test case. The calling information is the execution calling path information of the program to be tested, and the execution calling path information includes the calling class name and the calling function name. The calling information of the program under test can be obtained by obtaining the MAP file of the program under test. The MAP file is used to save information such as program global symbols, source files, and code line numbers, including the mapping relationship between function addresses and function names. The function name of the function called during the running of the program under test can be obtained based on the MAP file.

Step S20: When the calling information matches the preset assertion calling information, load the assertion detection identification into the target program corresponding to the calling information;

Step S30: Generate a test report based on the calling information and the assertion detection identification.

It should be noted that the preset assertion calling information includes default assertion calling information and customized assertion calling information. Among them, the customized assertion calling information can be configured by the user in advance through the configuration file as needed. It can be understood that the preset assertion calling information can be stored in any device that the assertion detection device can obtain, and the device can be either a server or a developer's client device. Since there are multiple groups or multiple test cases of the program to be tested in the automated test project, the preset assertion calling information is a set of assertion calling path information. Whether the calling information of the program under test matches the preset assertion calling information is obtained by the matching result of the execution calling path information of the program under test and the preset assertion calling path information. It can be understood that when the matching result is a match , it indicates that there is an assertion verification method in the program to be tested, which can locate the assertion in the program to be tested and determine the target program where the assertion is located, and then load the assertion detection identifier into the target program to mark whether there is an assertion in the program to be tested, where , the assertion detection identifier can be an annotation identifier; it can also be a buried point, which is implemented through the AssertionClassTransformer class. The assertion detection identifier can be loaded into the target program through the transform interface provided by the API before the program to be tested is compiled. In the test program, to mark the assertions in the program under test.

Generating a test report based on the calling information and the assertion detection identification can use a preset test report format, and the calling information and assertion detection identification can be output to the area associated with the preset test report format respectively; it can also be directly associated After saving the call information and assertion detection identification, the data is indirectly exported in table form to generate a test report. It can be understood that the test report can be in electronic form or in paper form. This embodiment does not limit the specific implementation of this step. Optionally, after generating the test report, the test report can be output directly to the display screen of the assertion detection device; the address of the target server can also be obtained according to the configuration file, and the test report can be uploaded to the server. This embodiment is specific to this step. The implementation is not limited.

In the technical solution disclosed in this embodiment, by obtaining the calling information of the program to be tested, when the calling information matches the preset assertion calling information, that is, the assertion in the program to be tested is located to determine the target program where the assertion is located. The assertion detection flag is added to the target program to mark assertions. By viewing the call information of the program under test and the test report generated by the assertion detection flag, the tester can easily know at a glance whether the program under test sets assertions in order to evaluate the testing effect of the program under test. Improve the testing quality of programs under test.

Based on the above embodiments, a second embodiment of the present invention is proposed. Please refer to FIG. 3 . FIG. 3 is a schematic flow chart of a second embodiment of an application testing method of the present invention. In this embodiment, step S30 includes:

Step S40, execute the program to be tested;

Step S50: When obtaining the return value of the execution result of the target program, set the assertion detection flag to assertion executed; or

Step S60: When the return value of the execution result of the target program is not obtained, the assertion detection flag is set to assertion not executed.

The return value of the execution result of the program under test can be a return value of a basic type, such as Boolean, character, byte or integer, etc., or a return value of an extended type, that is, the return value is an object. In the actual application process, even if the program under test is set with assertion verification, it is impossible to know whether the call information of the program under test, that is, the execution call information of the program under test, has execution assertions during the actual execution of the program under test. In the early stage, the assertion in the program to be tested is determined to determine the target program where the assertion is located. After the assertion detection flag is loaded into the target program, when the program to be tested is executed, the return value of the execution result of the target program where the assertion is located is received based on whether Determine whether assertion verification has been performed. It can be understood that when a return value is received, it indicates that the assertion has been called and executed. By setting the assertion detection flag to Assertion Executed to mark that there is an execution assertion in the program under test; when a return value is not received, it indicates that the assertion If the assertion has not been executed, set the assertion detection flag to Assertion Not Executed to mark that the assertion has not been executed in the program to be tested. The assertion detection flag can be set to "true" to indicate that the assertion has been executed. For example, it can be implemented through the AssertionHolder.setTrue method. , you can set "false" to indicate that the assertion is not executed.

Step S30 includes: step S31, generating a test report based on the call information, the execution result of the target program, and the assertion detection identification. Output the call information, target program execution results, and assertion detection identifiers to the area associated with the preset test report format respectively; you can also directly save the call information, target program execution results, and assertion detection identifiers and then export the data indirectly. The test report is generated in tabular form. It can be understood that the test report can be in electronic form or paper form. This embodiment does not limit the specific implementation of this step. Optionally, after generating the test report, the test report can be output directly to the display screen of the assertion detection device; the address of the target server can also be obtained according to the configuration file, and the test report can be uploaded to the server. This embodiment is specific to this step. The implementation is not limited.

In the technical solution disclosed in this embodiment, after the program to be tested is executed, whether the assertion in the program to be tested is called and executed is determined by obtaining the return value of the execution result of the target program. After obtaining the execution result of the target program, When returning a value, that is, when the assertion in the program under test is called and executed, set the assertion detection flag to Assertion Executed to mark the assertion as being called and executed. It is understandable that when the return value of the execution result of the target program is not obtained , set the assertion detection flag to assertion not executed to mark that the assertion has not been called and executed. In this way, based on the assertion being set in the program to be tested, it can be detected whether the assertion in the program to be tested has been called and executed. Finally, by viewing the generated Test reports allow testers to discover irregularities and missing assertions in the program to be tested, so as to further improve the program to be tested and improve the testing effect of the program to be tested.

A third embodiment of the present invention is proposed based on any of the above embodiments. Please refer to FIG. 4 , which is a schematic flow chart of a third embodiment of an application testing method of the present invention. In this embodiment, step S50 includes:

Step S51: When obtaining the return value of the execution result of the target program, compare the return value of the execution result of the target program with a preset expected value;

Step S52: When the return value matches the preset expected value, output prompt information that meets the test requirements;

Step S53: Set the assertion detection flag to assertion executed.

It should be noted that the overall concept of the assertion verification method for unit testing is to use an automated method to automatically obtain and store the expected values corresponding to the specific program to be tested and its specific parameter values in advance, and use them as predetermined values during assertion verification processing. set expected value. Since the preset expected value can be automatically obtained through the program, when performing assertion verification processing, error-prone problems caused by manually writing assertion verification statements can be avoided, thereby reducing the workload. It can be understood that the preset expected value can be stored in any device that the assertion verification device can obtain, and the device can be either a server or a developer's client device. In the specific implementation process, the storage location of the expected value can be specified in the form of configuration parameters. For example, a storage location option can be set in the assertion verification device.

During unit testing, errors may occur in the program to be tested, causing exceptions to be thrown. Therefore, in addition to the normal return value when the program under test runs normally, the return value of the program under test may have exceptions. Unlike errors, exceptions can be handled by the program itself. The program can perform corresponding subsequent processing based on the specific exception captured. Similarly, after receiving the return value of the execution result of the target program in the program to be tested, whether the target program is executed normally can be known by comparing the return value with the preset expected value. When the return value matches the preset expected value When, you can directly know that the target program is executed normally by outputting prompt information that meets the test requirements, and by setting the assertion detection flag to Assert Executed, you can use the assertion detection flag to obtain whether the target program in the test program has been executed.

In the technical solution disclosed in this embodiment, by comparing the return value of the execution result of the target program with the preset expected value, it can be known whether the target program is executed normally. When the return value matches the preset expected value, that is, the target program is normal. When executed, it indicates that the execution return value of the target program in the program to be tested meets the test requirements. Prompt information is output so that the tester can quickly understand that the target program executes normally and meets the test requirements.

The present invention also provides a terminal. The terminal includes: a memory, a processor, and a test program of an application program stored in the memory and executable on the processor. When the test program of the application program is executed by the processor, any of the above embodiments can be realized. Steps of the application testing method.

The present invention also provides a computer-readable storage medium. The computer-readable storage medium stores a test program of an application program. When the test program of the application program is executed by the processor, the test method of the application program in any of the above embodiments is implemented. step.

The embodiments of the terminal and the computer-readable storage medium provided by the present invention include all the technical features of the above-mentioned embodiments of the application program testing method, and the expansion and explanation content of the description are basically the same as the above-mentioned embodiments of the application program testing method. They are the same and will not be described in detail here.

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

The above serial numbers of the embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product in essence or that contributes to the existing technology. The computer software product is stored in one of the above storage media (such as ROM/RAM, magnetic disc, optical disk), including several instructions to cause a terminal device (which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to execute the method of each embodiment of the present invention.

The above are only preferred embodiments of the present invention, and do not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the description and drawings of the present invention may be directly or indirectly used in other related technical fields. , are all similarly included in the scope of patent protection of the present invention.

Claims (8)

1. An application testing method, characterized in that the application testing method includes: When detecting the loading instruction of the program to be tested, obtain the calling information of the program to be tested, where the calling information is the execution calling path information of the program to be tested; When the calling information matches the preset assertion calling information, it is determined that an assertion verification method is set in the program to be tested; Through the transform interface provided by the API, before the program to be tested is compiled, the assertion detection flag is loaded into the target program corresponding to the call information to mark whether there is an assertion in the program to be tested, wherein the pre- Assume that the assertion call information is a set of assertion call path information, and the assertion detection identification includes an annotation identification or a buried point; Generate a test report based on the calling information and the assertion detection identification. 2. The application testing method according to claim 1, characterized in that, before the step of generating a test report based on the call information and the assertion detection identification, the step includes: Execute the program to be tested; When the return value of the execution result of the target program is obtained, the assertion detection flag is set to assertion executed; or When the return value of the execution result of the target program is not obtained, the assertion detection flag is set to assertion not executed. 3. The application program testing method according to claim 2, wherein the step of setting the assertion detection flag to assertion executed when obtaining the return value of the execution result of the target program includes: : When obtaining the return value of the execution result of the target program, compare the return value of the execution result of the target program with a preset expected value; When the return value matches the preset expected value, a prompt message that meets the test requirements is output; The assertion detection flag is set to assertion executed. 4. The application testing method according to claim 2, wherein the step of generating a test report based on the call information and the assertion detection identification includes: Generate a test report based on the calling information, the execution result of the target program, and the assertion detection identification. 5. The application testing method according to any one of claims 1 to 4, wherein the step of generating a test report based on the call information and the assertion detection identification includes: Output the test report. 6. The application testing method according to claim 1, wherein the preset assertion calling information includes default assertion calling information and customized assertion calling information. 7. A terminal, characterized in that the terminal includes: a memory, a processor, and a test program of an application program stored in the memory and executable on the processor, and the test program of the application program is When the processor is executed, the steps of the testing method of the application program according to any one of claims 1 to 6 are implemented. 8. A computer-readable storage medium, characterized in that a test program of an application program is stored on the computer-readable storage medium. When the test program of the application program is executed by a processor, any of claims 1-6 can be implemented. The steps of an application testing method.