CN111008147A - Application program testing method, terminal and computer readable storage medium - Google Patents
Application program testing method, terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN111008147A CN111008147A CN201911333810.8A CN201911333810A CN111008147A CN 111008147 A CN111008147 A CN 111008147A CN 201911333810 A CN201911333810 A CN 201911333810A CN 111008147 A CN111008147 A CN 111008147A
- Authority
- CN
- China
- Prior art keywords
- assertion
- program
- test
- tested
- application program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012360 testing method Methods 0.000 claims abstract description 96
- 238000001514 detection method Methods 0.000 claims abstract description 53
- 238000010998 test method Methods 0.000 claims abstract description 7
- 238000000034 method Methods 0.000 claims description 37
- 230000000694 effects Effects 0.000 abstract description 7
- 238000012795 verification Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
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 calling information is matched with the preset assertion calling information, loading the assertion detection identification into a target program corresponding to the calling information; and generating a test report according to the calling information and the assertion detection identifier. The invention also provides a terminal and a computer readable storage medium. The testing method of the application program realizes the assertion positioning of the program to be tested by acquiring the calling information of the program to be tested, matching the calling information with the preset assertion calling information to determine the target program, adding the assertion detection identifier into the target program to mark the assertion, and facilitating a tester to check whether the program to be tested sets the assertion or not to evaluate the testing effect of the program to be tested by checking the calling information of the program to be tested and the test report generated by the assertion detection identifier.
Description
Technical Field
The present invention relates to the field of testing technologies, and in particular, to a method for testing an application program, a terminal, and a computer-readable storage medium.
Background
The basic criterion for measuring the quality of the automatic test case is whether the automatic test case has assertion. Unit testing typically includes assertion verification, i.e.: and verifying the return value of the tested code so as to judge whether the tested code is correct. Assertions, which are assumptions made by a programmer when writing code, are used to capture these assumptions in the code, and thus can be considered as a high-level form of exception handling.
Currently, in the internet industry, programmers often choose not to write assertions, and it is very common to print out the return values directly. In a large software, most unit tests do not have complete assertion, so that partial program defects cannot be detected, and even thousands of unit test cases seriously affect the test effect of the automatic test cases because of no assertion.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a test method, a terminal and a computer readable storage medium of an application program, and aims to solve the problem that a unit test case cannot be detected due to no assertion set, so that the test effect is influenced.
In order to achieve the above object, the present invention provides a method for testing an application program, wherein the method for testing the application program 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 calling information is matched with preset assertion calling information, loading an assertion detection identifier into a target program corresponding to the calling information;
and generating a test report according to the calling information and the assertion detection identifier.
Optionally, before the step of generating the test report according to the invocation information and the assertion detection identifier, the method includes:
executing a program to be tested;
when a return value of an execution result of the target program is acquired, setting the assertion detection mark as that assertion is executed; or
And when the return value of the execution result of the target program is not acquired, setting the assertion detection mark as assertion unexecution.
Optionally, when obtaining a return value of the execution result of the target program, the step of setting the assertion detection flag to be asserted to be executed includes:
when the return value of the execution result of the target program is obtained, comparing the return value of the execution result of the target program with a preset expectation value;
when the return value is matched with a preset expectation value, outputting prompt information meeting the test requirement;
setting the assertion detection flag to be asserted executed.
Optionally, the step of generating a test report according to the invocation information and the assertion detection identifier includes:
and generating a test report according to the calling information, the execution result of the target program and the assertion detection mark.
Optionally, the step of generating a test report according to the invocation information and the assertion detection flag includes:
and outputting the test report.
Optionally, the preset assertion calling information includes default assertion calling information and custom assertion calling information.
In addition, to achieve the above object, the present invention also provides a terminal, including: the test system comprises a memory, a processor and a test program of an application program stored in the memory and capable of running on the processor, wherein the test program of the application program realizes the steps of the test method of the application program when being executed by the processor.
In addition, to achieve the above object, the present invention further provides a computer readable storage medium storing a test program of an application program, which when executed by a processor, implements the steps of the test method of the application program.
According to the testing method of the application program, the calling information of the program to be tested is obtained, when the calling information is matched with the preset assertion calling information, the assertion in the program to be tested is positioned to determine the target program where the assertion is located, the assertion detection mark is added into the target program to mark the assertion, and by checking the calling information of the program to be tested and the test report generated by the assertion detection mark, a tester can know whether the assertion is set in the program to be tested at a glance so as to evaluate the testing effect of the program to be tested, and the testing quality of the program to be tested is improved.
Drawings
Fig. 1 is a schematic hardware structure diagram of a terminal for implementing various embodiments of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a method for testing an application program according to the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a method for testing an application program according to the present invention;
fig. 4 is a flowchart illustrating a method for testing an application according to a third embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the terminal device described in the present invention may include a terminal such as a mobile phone, a tablet computer, a notebook computer, and a palm computer.
It will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for moving purposes.
Please refer to fig. 1, which is a schematic diagram of a hardware structure of a terminal for implementing various embodiments of the present invention, where the terminal may include: memory 101, processor 102, and display unit 103. Those skilled in the art will appreciate that the terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, and that terminals may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The memory 101 stores therein a central control system and a test program of an application program. The processor 102 is a control center of the terminal, and the processor 102 executes a test program of the application program stored in the memory 101 to implement the steps of the embodiments of the test method of the application program of the present invention.
The Display unit 103 includes a Display panel, which may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like, and is configured to output a test result of the test program of the Display application executed by the processor 102.
Referring to fig. 2, fig. 2 is a schematic flowchart illustrating a first embodiment of a method for testing an application program according to the present invention. In this embodiment, the method for testing the application program includes the following steps:
step S10, when a loading instruction of a program to be tested is detected, acquiring calling information of the program to be tested;
the basic standard for measuring the quality of the automated test case is whether the automated test case has an assertion, and the unit test program generally includes assertion verification, where the unit test program refers to a test program that checks and verifies a minimum testable unit in software, for example: taking the program developed in JAVA language as an example, the method, function, etc. are the smallest testable unit. It should be noted that the program to be tested is a test case in an automated test project, and a tester can determine whether the application software or the software system works correctly according to the test case. The calling information is the execution calling path information of the program to be tested, and the execution calling path information comprises a calling class name and a calling function name. The method comprises the steps of obtaining calling information of a program to be tested through obtaining an MAP file of the program to be tested, wherein the MAP file is used for storing information such as a program global symbol, a source file, a code line number and the like, the mapping relation between a function address and a function name is included, and the function name of a function called in the running process of the program to be tested can be obtained based on the MAP file.
Step S20, when the calling information is matched with the preset assertion calling information, loading the assertion detection identification into the target program corresponding to the calling information;
and step S30, generating a test report according to the calling information and the assertion detection identification.
It should be noted that the preset assertion calling information includes default assertion calling information and custom assertion calling information. The self-defined assertion calling information can be configured by a user in advance according to needs through a configuration file. It is understood that the preset assertion calling information may be stored in any device that can be acquired by the assertion detecting apparatus, and the device may be a server or a client device of a developer. Because there are multiple groups or multiple groups of programs to be tested, i.e. test cases, in the automated test project, the preset assertion calling information is an assertion calling path information set. Whether the call information of the program to be tested is matched with the preset assertion call information or not is obtained through a matching result of the execution call path information of the program to be tested and the preset assertion call path information, and it can be understood that when the matching result is matched, an assertion verification method is arranged in the program to be tested, so that the assertion in the program to be tested is positioned, a target program where the assertion is located is determined, and then an assertion detection identifier is loaded to the target program to mark whether the assertion exists in the program to be tested or not, wherein the assertion detection identifier can be an annotation identifier; the test result can also be a buried point, the buried point is realized by an assertion class transformer class, and the assertion detection identifier is loaded to the target program through a transform interface provided by an API (application programming interface) before the program to be tested is compiled, so that the assertion in the program to be tested is marked.
Generating a test report according to the calling information and the assertion detection identification, wherein the test report can pass through a preset test report format, and correspondingly outputting the calling information and the assertion detection identification to an area associated with the preset test report format respectively; the test report may also be generated in a form of a data table by directly associating and storing the call information and asserting the detection identifier and then indirectly exporting the detection identifier, and it is understood that the test report may be in an electronic form or a paper form, and the specific implementation of this step is not limited in this embodiment. Optionally, the test report is output after the test report is generated, and the test report can be directly output to a display screen of the assertion detection device; the address of the target server may also be obtained according to the configuration file, and the test report is uploaded to the server.
In the technical scheme disclosed in this embodiment, by obtaining the calling information of the program to be tested, when the calling information matches with the preset assertion calling information, that is, by locating the assertion in the program to be tested to determine the target program where the assertion is located, the assertion detection identifier is added to the target program to mark the assertion, and by looking up the test report generated by the calling information of the program to be tested and the assertion detection identifier, a tester can easily and clearly know whether the assertion is set by the program to be tested so as to evaluate the test effect of the program to be tested, and the test quality of the program to be tested is improved.
Referring to fig. 3, fig. 3 is a flowchart illustrating a second embodiment of a testing method for an application program according to the present invention. In this embodiment, step S30 is preceded by:
step S40, executing the program to be tested;
step S50, when the return value of the execution result of the target program is obtained, setting the assertion detection mark as assertion executed; or
In 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 unexecution.
The return value of the execution result of the program under test may be a basic type of return value, for example: boolean, character, byte, integer, etc., and may also be extended type return values, i.e.: the return value is an object. In an actual application process, even if assertion verification is set in the program to be tested, it is not known whether the call information of the program to be tested, that is, the execution call information of the program to be tested, has execution assertion or not in the actual execution process of the program to be tested. And in the early stage, positioning the assertion in the program to be tested to determine the target program where the assertion is located, loading the assertion detection identifier to the target program, and judging whether assertion verification is executed according to whether a return value of an execution result of the target program where the assertion is located is received or not when the program to be tested is executed. It is understood that when a return value is received, the assertion is called to be executed, and the assertion detection identifier is set to be executed so as to mark that an execution assertion exists in the program to be tested; when the return value is not received, the assertion is not called to be executed, and the assertion detection identifier is set to be not executed so as to mark that the assertion is not executed in the program to be tested, wherein the assertion detection identifier can indicate that the assertion is executed by setting 'future', for example, the assertion holder.
The step S30 includes: and step S31, generating a test report according to the calling information, the execution result of the target program and the assertion detection mark. Respectively and correspondingly outputting the calling information, the execution result of the target program and the assertion detection identification to an area associated with a preset test report format; the test report may also be generated in a form of a data table indirectly derived after directly associating and storing the call information, the execution result of the target program, and the assertion detection identifier, and it is understood that the test report may be in an electronic form or a paper form, and this embodiment does not limit the specific implementation of this step. Optionally, the test report is output after the test report is generated, and the test report can be directly output to a display screen of the assertion detection device; the address of the target server may also be obtained according to the configuration file, and the test report is uploaded to the server.
In the technical solution disclosed in this embodiment, after executing the program to be tested, it is determined whether the assertion in the program to be tested is called to be executed by obtaining the return value of the execution result of the target program, and when the return value of the execution result of the target program is obtained, that is, when the assertion in the program to be tested is called to be executed, the assertion detection flag is set to be asserted to be executed so as to mark that the assertion is called to be executed, it can be understood that, when the return value of the execution result of the target program is not obtained, the assertion detection flag is set to be asserted to be not executed so as to mark that the assertion is not called to be executed, so that on the basis that the assertion is set in the program to be tested, it is possible to detect whether the assertion in the program to be tested is called to be executed, and finally, by checking the generated test report, it is, the test effect of the program to be tested is improved.
Referring to fig. 4, fig. 4 is a flowchart illustrating a third embodiment of a testing method for an application according to the present invention. In this embodiment, step S50 includes:
step S51, when the return value of the execution result of the target program is acquired, comparing the return value of the execution result of the target program with a preset expected value;
step S52, when the return value is matched with the preset expectation value, outputting prompt information meeting the test requirement;
step S53, setting the assertion detection flag to be asserted executed.
It should be noted that the assertion verification method for unit test is based on the general concept that an automated method is adopted to automatically acquire and store the expected value corresponding to a specific program to be tested and a specific parameter value thereof in advance, and the expected value is used as the expected value preset during assertion verification processing. Because the preset expectation value can be automatically obtained through a program, the problem that errors are easy to occur due to manual writing of assertion verification statements can be avoided when assertion verification processing is carried out, and the effect of reducing the workload is achieved. It is understood that the predetermined expected value may be stored in any device that can be obtained by the assertion verifying apparatus, and the device may be a server or a client device of a developer. In the implementation process, the storage location of the expected value may be specified in a manner of configuring parameters, for example: a storage location option may be provided in the assertion verification means.
In the process of unit testing, errors may occur in the program to be tested, which may cause an exception to be thrown. Therefore, there may be an exception to the return value of the program under test in addition to the normal return value when the program under test is running normally. Unlike errors, exceptions are handled by the program itself. The program can perform corresponding subsequent processing according to the captured specific exception. Similarly, after receiving a return value of an execution result of a target program in the program to be tested, whether the target program is normally executed or not can be known by comparing the return value with a preset expectation value, when the return value is matched with the preset expectation value, normal execution of the target program can be directly known by outputting prompt information meeting the test requirement, the assertion detection identifier is set to be asserted for execution, and whether the target program in the test program is executed or not can be obtained by the assertion detection identifier.
In the technical solution disclosed in this embodiment, whether the target program is normally executed or not can be known by comparing the return value of the execution result of the target program with the preset expected value, and when the return value matches the preset expected value, that is, when the target program is normally executed and the execution return value of the target program in the program to be tested is indicated to meet the test requirement, the tester can quickly know that the target program is normally executed and meets the test requirement by outputting the prompt information.
The present invention also provides a terminal, comprising: the testing system comprises a memory, a processor and a testing program of an application program stored in the memory and capable of running on the processor, wherein the testing program of the application program realizes the steps of the testing method of the application program in any embodiment when being executed by the processor.
The present invention further provides a computer-readable storage medium, on which a test program of an application program is stored, and when the test program of the application program is executed by a processor, the steps of the method for testing the application program in any of the above embodiments are implemented.
In the embodiments of the terminal and the computer-readable storage medium provided by the present invention, all technical features of the embodiments of the method for testing an application program are included, and the contents of the expansion and the explanation of the specification are basically the same as those of the embodiments of the method for testing an application program, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a controlled terminal, or a network device) to execute the method of each embodiment of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (8)
1. A method for testing an application program is characterized by comprising 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 calling information is matched with preset assertion calling information, loading an assertion detection identifier into a target program corresponding to the calling information;
and generating a test report according to the calling information and the assertion detection identifier.
2. The method for testing an application program according to claim 1, wherein the step of generating a test report based on the invocation information and the assertion detection flag is preceded by the steps of:
executing a program to be tested;
when a return value of an execution result of the target program is acquired, setting the assertion detection mark as that assertion is executed; or
And when the return value of the execution result of the target program is not acquired, setting the assertion detection mark as assertion unexecution.
3. The method for testing an application program according to claim 2, wherein the step of setting the assertion detection flag to assert that has been executed when obtaining the return value of the execution result of the target program includes:
when the return value of the execution result of the target program is obtained, comparing the return value of the execution result of the target program with a preset expectation value;
when the return value is matched with a preset expectation value, outputting prompt information meeting the test requirement;
setting the assertion detection flag to be asserted executed.
4. The method for testing an application program according to claim 2, wherein the step of generating a test report based on the invocation information and the assertion detection flag comprises:
and generating a test report according to the calling information, the execution result of the target program and the assertion detection mark.
5. The method for testing an application program according to any one of claims 1 to 4, wherein the step of generating a test report according to the invocation information and the assertion detection flag is followed by:
and outputting the test report.
6. The method for testing an application program according to claim 1, wherein the preset assertion call information includes default assertion call information and custom assertion call information.
7. A terminal, characterized in that the terminal comprises: memory, a processor and a test program of an application program stored in the memory and executable on the processor, the test program of the application program, when executed by the processor, implementing the steps of the test method of the application program according to any of claims 1 to 6.
8. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a test program of an application program, which when executed by a processor implements the steps of the test method of the application program according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911333810.8A CN111008147B (en) | 2019-12-20 | 2019-12-20 | Application program testing method, terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911333810.8A CN111008147B (en) | 2019-12-20 | 2019-12-20 | Application program testing method, terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008147A true CN111008147A (en) | 2020-04-14 |
| CN111008147B CN111008147B (en) | 2023-12-26 |
Family
ID=70116780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911333810.8A Active CN111008147B (en) | 2019-12-20 | 2019-12-20 | Application program testing method, terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008147B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112116439A (en) * | 2020-08-10 | 2020-12-22 | 杭州优行科技有限公司 | Clearing and settlement testing method, device, terminal and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8127275B1 (en) * | 2007-04-18 | 2012-02-28 | Parasoft Corporation | System and method for recording the state of variables and objects when running unit tests |
| CN102609352A (en) * | 2011-01-19 | 2012-07-25 | 阿里巴巴集团控股有限公司 | Parallel testing method and parallel testing server |
| CN105760292A (en) * | 2014-12-18 | 2016-07-13 | 阿里巴巴集团控股有限公司 | Assertion verification method and device for unit testing |
| CN110427188A (en) * | 2019-08-02 | 2019-11-08 | 深圳前海微众银行股份有限公司 | It is single to survey configuration method, device, equipment and the storage medium for asserting program |
| CN110532185A (en) * | 2019-08-29 | 2019-12-03 | 中国工商银行股份有限公司 | Test method, device, electronic equipment and computer readable storage medium |
| CN110569194A (en) * | 2019-09-09 | 2019-12-13 | 五八有限公司 | interface testing method and device, electronic equipment and storage medium |
-
2019
- 2019-12-20 CN CN201911333810.8A patent/CN111008147B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8127275B1 (en) * | 2007-04-18 | 2012-02-28 | Parasoft Corporation | System and method for recording the state of variables and objects when running unit tests |
| CN102609352A (en) * | 2011-01-19 | 2012-07-25 | 阿里巴巴集团控股有限公司 | Parallel testing method and parallel testing server |
| CN105760292A (en) * | 2014-12-18 | 2016-07-13 | 阿里巴巴集团控股有限公司 | Assertion verification method and device for unit testing |
| CN110427188A (en) * | 2019-08-02 | 2019-11-08 | 深圳前海微众银行股份有限公司 | It is single to survey configuration method, device, equipment and the storage medium for asserting program |
| CN110532185A (en) * | 2019-08-29 | 2019-12-03 | 中国工商银行股份有限公司 | Test method, device, electronic equipment and computer readable storage medium |
| CN110569194A (en) * | 2019-09-09 | 2019-12-13 | 五八有限公司 | interface testing method and device, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112116439A (en) * | 2020-08-10 | 2020-12-22 | 杭州优行科技有限公司 | Clearing and settlement testing method, device, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008147B (en) | 2023-12-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109542761B (en) | Software quality evaluation method, device and storage medium | |
| US8397104B2 (en) | Creation of test plans | |
| CN109726107A (en) | Test method, device, equipment and storage medium | |
| CN107656872B (en) | Software testing method, device, equipment and computer storage medium | |
| CN111459495B (en) | Unit test code file generation method, electronic device and storage medium | |
| CN110532185B (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| US10209984B2 (en) | Identifying a defect density | |
| US20010028359A1 (en) | Test support apparatus and test support method for GUI system program | |
| US8661414B2 (en) | Method and system for testing an order management system | |
| CN110879781A (en) | Program debugging method and device, electronic equipment and computer readable storage medium | |
| CN110704311B (en) | Application program testing method and device, electronic equipment and readable storage medium | |
| US9779014B2 (en) | Resilient mock object creation for unit testing | |
| US11422917B2 (en) | Deriving software application dependency trees for white-box testing | |
| CN111382077A (en) | Application program crash reason positioning method and device, electronic equipment and storage medium | |
| CN109189688B (en) | Test case script generation method and device and electronic equipment | |
| CN107450909A (en) | The treating method and apparatus of validity check is integrated for SDK | |
| CN111008147B (en) | Application program testing method, terminal and computer readable storage medium | |
| CN112216337A (en) | Firmware parameter detection method and device and firmware setting method | |
| US8464103B2 (en) | Generating a functional coverage model from a trace | |
| CN116860608A (en) | Interface testing method and device, computing equipment and storage medium | |
| CN116756037A (en) | Abnormal code positioning system, method, equipment and computer readable storage medium | |
| KR20120111618A (en) | Apparatus and method for testing plc command | |
| CN114238110A (en) | Software application testing method, device, equipment and storage medium | |
| CN112015658A (en) | Method and device for generating software integration test case | |
| CN109165127B (en) | Problem interface positioning method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |