CN110727597A - Method for completing use case based on log troubleshooting invalid codes - Google Patents
Method for completing use case based on log troubleshooting invalid codes Download PDFInfo
- Publication number
- CN110727597A CN110727597A CN201910978504.3A CN201910978504A CN110727597A CN 110727597 A CN110727597 A CN 110727597A CN 201910978504 A CN201910978504 A CN 201910978504A CN 110727597 A CN110727597 A CN 110727597A
- Authority
- CN
- China
- Prior art keywords
- interface
- test
- test set
- case
- called
- 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
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/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/72—Code refactoring
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a method, a device, equipment and a readable storage medium for completing a use case based on log troubleshooting invalid codes, wherein the scheme comprises the following steps: acquiring a test set of a target module; executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file; determining interfaces which are not called in the execution process of each test case in the test set according to an interface list and a log file recorded with all interfaces of the target module; and deleting the invalid codes of the target module or completing the test set according to the interface which is not called. Therefore, in the process of executing the test case, the interface of the source code of the target module is screened, the interface which is not called is determined, and according to the interface, the invalid code is deleted to reduce the redundancy of the code, or the test case is supplemented to improve the test effect.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for completing a use case based on log troubleshooting invalid codes.
Background
With the continuous increase of the software scale, the detection of software defects is more important, and an unobtrusive small error can cause huge loss. However, the presence of redundant code in programs has long been considered a negligible problem, thought not to be too harmful to the program, and therefore has given little attention. However, it has been found that errors contained in redundant code are also severely compromised and not easily discovered.
In addition, the design of the test case is a process which is simple to detailed and gradually perfected to a great extent, and the test case is designed according to reference materials such as requirement documents, summary design, detailed design and the like. If there are no complete test cases in the test process, the test process is difficult to control or the test results will be unreliable.
Therefore, how to investigate the redundant code completion case is a problem to be solved urgently by the technical personnel in the field.
Disclosure of Invention
The application aims to provide a method, a device, equipment and a readable storage medium for completing a case based on log troubleshooting invalid codes, and the method, the device, the equipment and the readable storage medium are used for solving the problems of low software reliability and poor test effect caused by the current scheme that the troubleshooting of the invalid codes and the completion of test cases cannot be realized. The specific scheme is as follows:
in a first aspect, the present application provides a method for checking an invalid code completion case based on a log, including:
acquiring a test set of a target module;
executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file;
determining interfaces which are not called in the execution process of each test case in the test set according to an interface list recorded with all interfaces of the target module and the log file;
and deleting the invalid codes of the target module or completing the test set according to the interface which is not called.
Preferably, before the obtaining the test set of the target module, the method further includes:
and generating a test case covering all pages and operations of the target module by using the testlink to obtain a test set.
Preferably, before executing each test case in the test set, the method further includes:
and setting middleware for the interface of the target module, wherein the middleware is used for recording the called interface into a log file in the execution process of the test case.
Preferably, the executing each test case in the test set includes:
executing each test case in the test set; and setting a completion mark for each test case when the execution of each test case is completed until all test cases of the test set are executed.
Preferably, the executing each test case in the test set includes:
and responding to the operation of a user on a front-end interface of the platform to execute each test case in the test set.
Preferably, the determining, according to the interface list and the log file recorded with all the interfaces of the target module, an interface that is not called in the execution process of each test case in the test set includes:
traversing an interface list recorded with all interfaces of the target module by using a polling script, and judging whether the currently polled interface exists in the log file;
if the interface does not exist, recording the interface into a target file to serve as the interface which is not called in the execution process of each test case in the test set.
Preferably, the deleting the invalid code of the target module or completing the test set according to the interface that is not called includes:
for each interface which is not called in the target file, judging whether the interface is effective or not according to the function setting of a front-end interface of the platform;
if the interface is valid, completing the test set according to the interface;
and if the target module is invalid, deleting an invalid code corresponding to the interface in the target module.
In a second aspect, the present application provides an apparatus for checking an invalid code completion use case based on a log, including:
a use case acquisition module: the method comprises the steps of obtaining a test set of a target module;
a use case execution module: executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file;
an interface determination module: determining interfaces which are not called in the execution process of each test case in the test set according to an interface list recorded with all interfaces of the target module and the log file;
an interface checking module: and deleting the invalid codes of the target module or completing the test set according to the interface which is not called.
In a third aspect, the present application provides an apparatus for checking an invalid code completion use case based on a log, including:
a memory: for storing a computer program;
a processor: for executing the computer program to implement the steps of a method for completing a use case based on log-based checking of invalid code as described above.
In a fourth aspect, the present application provides a readable storage medium having stored thereon a computer program for implementing, when being executed by a processor, the steps of a method for completing a use case based on log-based checking of invalid code as described above.
The application provides a method, a device, equipment and a readable storage medium for completing a use case based on log troubleshooting invalid codes, and the scheme comprises the following steps: acquiring a test set of a target module; executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file; determining interfaces which are not called in the execution process of each test case in the test set according to an interface list and a log file recorded with all interfaces of the target module; and deleting the invalid codes of the target module or completing the test set according to the interface which is not called. Therefore, in the process of executing the test case, the interface of the source code of the target module is screened, the interface which is not called is determined, and according to the interface, the invalid code is deleted to reduce the redundancy of the code, or the test case is supplemented to improve the test effect.
Drawings
For a clearer explanation of the embodiments or technical solutions of the prior art of the present application, the drawings needed for the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart illustrating an implementation of a first embodiment of a method for checking an invalid code completion case based on a log according to the present application;
fig. 2 is a flowchart illustrating an implementation of a second method for checking an invalid code completion case based on a log according to an embodiment of the present disclosure;
FIG. 3 is a functional block diagram of an embodiment of an apparatus for completing a use case based on a log check invalid code according to the present disclosure;
fig. 4 is a schematic structural diagram of an embodiment of an apparatus for checking an invalid code completion use case based on a log according to the present application.
Detailed Description
The core of the application is to provide a method, a device, equipment and a readable storage medium for completing a case based on log troubleshooting invalid codes, wherein an interface of a target module source code is screened in the process of executing a test case, an interface which is not called is determined, and according to the interface, the invalid codes are deleted to reduce the redundancy of the codes or the test case is completed to improve the test effect.
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, a first embodiment of a method for checking an invalid code completion case based on a log is described below, where the first embodiment includes:
s101, acquiring a test set of a target module;
the target module may specifically be a module for any project in software engineering, and in this embodiment, a corresponding test set is set for each target module, where the test set includes a plurality of test cases for testing the source code interface of the target module. Specifically, a test case is generated by using a case management tool, and all interfaces of the target module are covered as much as possible in the generation process, so that the test set is obtained finally. In the testing process, a pre-generated testing set can be directly obtained.
S102, executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file;
as described above, the present embodiment creates a log file in advance to record the interfaces called by the test cases in the process of executing the test set. Specifically, in this embodiment, a middleware is provided at an interface of the target module to implement the above-mentioned recording operation.
S103, determining interfaces which are not called in the execution process of each test case in the test set according to the interface list recorded with all the interfaces of the target module and the log file;
specifically, in this embodiment, all interfaces in the target module code library are exported as an interface list, and by comparing the interface list with the log file, it can be determined that the target module is not called in the test case execution process.
And S104, deleting the invalid codes of the target module or completing the test set according to the interface which is not called.
The purpose of this embodiment is to delete invalid codes in the target module and obtain a full use case of the target module. Specifically, when the interface which is not called is an invalid interface, deleting an invalid code corresponding to the invalid interface in the target module; and when the interface which is not called is an effective interface, supplementing the test set of the target module according to the interface to finally obtain the full use case of the target module. The invalid code refers to an unnecessary interface or a disused interface generated in the development process, and is not used in the project. The above-mentioned full-quantity case refers to a case that can completely return to the whole module.
Therefore, for the interface that is not called, the embodiment first determines whether the interface is actually valid, that is, whether the interface is used in the project, and if so, the test set can be supplemented to make the interface more complete; otherwise, determining that the code is an invalid code and deleting.
The embodiment provides a method for completing a use case based on log troubleshooting invalid codes, which comprises the following steps: acquiring a test set of a target module; executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file; determining interfaces which are not called in the execution process of each test case in the test set according to an interface list and a log file recorded with all interfaces of the target module; and deleting the invalid codes of the target module or completing the test set according to the interface which is not called. Therefore, in the process of executing the test case, the interface of the source code of the target module is screened, the interface which is not called is determined, and according to the interface, the invalid code is deleted to reduce the redundancy of the code, or the test case is supplemented to improve the test effect.
The second embodiment of the method for checking the invalid code completion case based on the log provided by the present application is described in detail below, and the second embodiment is implemented based on the first embodiment and is expanded to a certain extent based on the first embodiment.
Referring to fig. 2, the second embodiment specifically includes:
s201, generating a test case covering all pages and operations of a target module by using a testlink to obtain a test set;
firstly, preparing a test set, completely preparing a test case of a target module as much as possible, aiming at covering the execution of effective interfaces as much as possible and reducing the single code investigation work in the later period, wherein the process specifically comprises the following steps: preparing a use case of a target module on use case management software, for example, using testlink, wherein the use case is required to cover all pages and operations; and setting a test set, taking testlink as an example, and independently setting the prepared use case into a test set, wherein the purpose is that records exist when the use case is executed later, and the test set can also be used as the basis for later verification.
S202, setting a middleware for an interface of the target module;
the middleware is used for recording the called interface into a log file in the execution process of the test case. Adding middleware to the interface to log all called interfaces, wherein the aim of the process is to: and writing the called interface into a log to prove that the interface is called in the whole use case execution process and provide basis for later polling.
S203, responding to the operation of a user on a front-end interface of the platform to execute each test case in the test set; when the execution of each test case is completed, recording an interface called in the execution process of the test case into a log file, and setting a completion mark for the test case until all test cases of a test set are executed;
specifically, a user may manually execute a use case on the platform front-end interface, in this embodiment, a completion flag is marked on the use case that is passed through execution, and after all use cases in the party test set are executed, a log file recorded with all interfaces that are not called may be obtained.
S204, traversing an interface list recorded with all interfaces of the target module by using a polling script, and judging whether the current polled interface exists in the log file; if not, jumping to S205; if yes, continuing polling until a complete interface list is polled;
s205, recording the interface into a target file to serve as an interface which is not called in the execution process of each test case in the test set;
in this embodiment, all the interfaces in the code library of the target module are exported in advance to form an interface list, and a polling script is prepared, which is used for polling the interfaces in the interface list to determine whether the interfaces exist in the log file, if the interfaces do not exist in the log file, the interfaces are automatically recorded in the target file, and the target file obtained after the polling script runs out is the interface which needs to be checked one by one finally.
S206, judging whether each interface which is not called in the target file is effective according to the function setting of a front-end interface of the platform; if the result is valid, jumping to S207, otherwise jumping to S208;
s207, completing the test set according to the interface;
and S208, deleting the invalid code corresponding to the interface in the target module.
Checking the interfaces in the target file one by one, judging whether the interfaces are effective according to the function setting of the front-end interface of the platform, and supplementing a test set to enable the interfaces to be more complete if the interfaces are effective; otherwise, determining that the code is an invalid code and deleting.
In summary, according to the method for checking the invalid code completion case based on the log, when the interface is called, the invalid code completion case is written into the log file, and the interface in the interface list is compared with the interface list through the polling script, so that the interface which is not called can be determined. In the embodiment, it is determined from the platform front-end interface operation which interfaces are actually used and which interfaces are useless from the interface operation, so that invalid codes are screened out, and in addition, the use case can be more complete.
In the following, a device for repairing a use case based on a log investigation invalid code according to an embodiment of the present application is introduced, and a device for repairing a use case based on a log investigation invalid code described below and a method for repairing a use case based on a log investigation invalid code described above may be referred to correspondingly.
Referring to fig. 3, the apparatus includes:
the use case obtaining module 301: the method comprises the steps of obtaining a test set of a target module;
the use case execution module 302: executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file;
the interface determination module 303: determining interfaces which are not called in the execution process of each test case in the test set according to an interface list recorded with all interfaces of the target module and the log file;
the interface troubleshooting module 304: and deleting the invalid codes of the target module or completing the test set according to the interface which is not called.
In some specific embodiments, the method further comprises:
a test case generation module: and generating a test case covering all pages and operations of the target module by using the testlink to obtain a test set.
In some specific embodiments, the method further comprises:
the middleware sets up the module: and setting middleware for the interface of the target module, wherein the middleware is used for recording the called interface into a log file in the execution process of the test case.
In some specific embodiments, the use case execution module is specifically configured to:
executing each test case in the test set; and setting a completion mark for each test case when the execution of each test case is completed until all test cases of the test set are executed.
In some specific embodiments, the use case execution module is specifically configured to:
and responding to the operation of a user on a front-end interface of the platform to execute each test case in the test set.
In some specific embodiments, the interface troubleshooting module is specifically configured to:
traversing an interface list recorded with all interfaces of the target module by using a polling script, and judging whether the currently polled interface exists in the log file; if the interface does not exist, recording the interface into a target file to serve as the interface which is not called in the execution process of each test case in the test set.
In some specific embodiments, the interface determining module is specifically configured to:
for each interface which is not called in the target file, judging whether the interface is effective or not according to the function setting of a front-end interface of the platform; if the interface is valid, completing the test set according to the interface; and if the target module is invalid, deleting an invalid code corresponding to the interface in the target module.
The device for completing the use case based on the log scrutiny invalid code is used for implementing the method for completing the use case based on the log scrutiny invalid code, and therefore the specific implementation manner in the device can be seen in the embodiment parts of the method for completing the use case based on the log scrutiny invalid code in the foregoing, for example, the use case obtaining module 301, the use case executing module 302, the interface determining module 303 and the interface scrutiny module 304 are respectively used for implementing the steps S101, S102, S103 and S104 in the method for completing the use case based on the log scrutiny invalid code. Therefore, specific embodiments thereof may be referred to in the description of the corresponding respective partial embodiments, and will not be described herein.
In addition, since the device for checking the invalid code completion case based on the log of the embodiment is used for implementing the method for checking the invalid code completion case based on the log, the role of the device corresponds to that of the method, and details are not repeated here.
In addition, the present application further provides an apparatus for checking an invalid code completion use case based on a log, as shown in fig. 4, including:
the memory 100: for storing a computer program;
the processor 200: for executing the computer program to implement the steps of a method for completing a use case based on log-based checking of invalid code as described above.
The memory 100 includes at least one type of readable storage medium, which includes flash memory, hard disks, multimedia cards, card-type memory, magnetic disks, optical disks, and the like. Processor 200 may be, in some embodiments, a central processing unit, controller, microcontroller, microprocessor or other data processing chip that executes program code stored in memory 100 or processes data.
The memory 100 and the processor 200 are connected by a bus, which may be a peripheral component interconnect standard bus or an extended industry standard architecture bus, etc., and which may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 4, but this does not indicate only one bus or one type of bus.
Finally, the present application also provides a readable storage medium having stored thereon a computer program for implementing, when being executed by a processor, the steps of a method for completing a use case based on log-based checking of invalid code as described above.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above detailed descriptions of the solutions provided in the present application, and the specific examples applied herein are set forth to explain the principles and implementations of the present application, and the above descriptions of the examples are only used to help understand the method and its core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A method for checking an invalid code completion case based on a log is characterized by comprising the following steps:
acquiring a test set of a target module;
executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file;
determining interfaces which are not called in the execution process of each test case in the test set according to an interface list recorded with all interfaces of the target module and the log file;
and deleting the invalid codes of the target module or completing the test set according to the interface which is not called.
2. The method of claim 1, prior to said obtaining a test set of target modules, further comprising:
and generating a test case covering all pages and operations of the target module by using the testlink to obtain a test set.
3. The method of claim 2, wherein prior to said executing each test case in the test set, further comprising:
and setting middleware for the interface of the target module, wherein the middleware is used for recording the called interface into a log file in the execution process of the test case.
4. The method of claim 1, wherein said executing each test case in the test set comprises:
executing each test case in the test set; and setting a completion mark for each test case when the execution of each test case is completed until all test cases of the test set are executed.
5. The method of claim 1, wherein said executing each test case in the test set comprises:
and responding to the operation of a user on a front-end interface of the platform to execute each test case in the test set.
6. The method according to any one of claims 1 to 5, wherein the determining, according to the interface list and the log file recorded with all interfaces of the target module, an interface that is not called in the execution process of each test case in the test set comprises:
traversing an interface list recorded with all interfaces of the target module by using a polling script, and judging whether the currently polled interface exists in the log file;
if the interface does not exist, recording the interface into a target file to serve as the interface which is not called in the execution process of each test case in the test set.
7. The method of claim 6, wherein said deleting invalid code of the target module or completing the test set based on the interface that was not invoked comprises:
for each interface which is not called in the target file, judging whether the interface is effective or not according to the function setting of a front-end interface of the platform;
if the interface is valid, completing the test set according to the interface;
and if the target module is invalid, deleting an invalid code corresponding to the interface in the target module.
8. An apparatus for checking an invalid code completion case based on a log, comprising:
a use case acquisition module: the method comprises the steps of obtaining a test set of a target module;
a use case execution module: executing each test case in the test set, determining an interface called in the execution process of the test case, and recording the interface into a log file;
an interface determination module: determining interfaces which are not called in the execution process of each test case in the test set according to an interface list recorded with all interfaces of the target module and the log file;
an interface checking module: and deleting the invalid codes of the target module or completing the test set according to the interface which is not called.
9. An apparatus for completing a use case based on log checking of invalid codes, comprising:
a memory: for storing a computer program;
a processor: for executing the computer program for implementing a method for log-based checking of invalid code completion use cases according to any of claims 1 to 7.
10. A readable storage medium, having stored thereon a computer program for implementing, when being executed by a processor, the steps of a method for completing a use case based on log-based checking of invalid code according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910978504.3A CN110727597B (en) | 2019-10-15 | 2019-10-15 | Method for checking invalid code completion case based on log |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910978504.3A CN110727597B (en) | 2019-10-15 | 2019-10-15 | Method for checking invalid code completion case based on log |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110727597A true CN110727597A (en) | 2020-01-24 |
| CN110727597B CN110727597B (en) | 2023-03-10 |
Family
ID=69221195
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910978504.3A Active CN110727597B (en) | 2019-10-15 | 2019-10-15 | Method for checking invalid code completion case based on log |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110727597B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112416772A (en) * | 2020-11-23 | 2021-02-26 | 中信银行股份有限公司 | Test case completion method and device, electronic equipment and readable storage medium |
| CN112732335A (en) * | 2021-01-12 | 2021-04-30 | 平安资产管理有限责任公司 | Object code extraction method, device, computer equipment and storage medium |
| CN112948258A (en) * | 2021-03-26 | 2021-06-11 | 杭州万高科技股份有限公司 | Code testing method, device, equipment and computer readable storage medium |
| CN113297058A (en) * | 2020-04-27 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Case generation method, test method, device and server |
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
| CN113760690A (en) * | 2020-06-05 | 2021-12-07 | 腾讯科技（深圳）有限公司 | Method and device for analyzing program interface and computer equipment |
Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080172652A1 (en) * | 2007-01-15 | 2008-07-17 | Microsoft Corporation | Identifying Redundant Test Cases |
| CN103235759A (en) * | 2013-05-15 | 2013-08-07 | 百度在线网络技术（北京）有限公司 | Method and device for generating test cases |
| CN103473171A (en) * | 2013-08-28 | 2013-12-25 | 北京信息科技大学 | Coverage rate dynamic tracking method and device based on function call paths |
| GB2508643A (en) * | 2012-12-07 | 2014-06-11 | Ibm | Method for Performing a Regression Test after Modifying Source Code File |
| CN104536895A (en) * | 2015-01-12 | 2015-04-22 | 牟永敏 | Test process tracking method and system for Java function call path |
| US9442830B1 (en) * | 2014-06-25 | 2016-09-13 | Emc Corporation | Automated test coverage analysis, execution and reporting |
| CN106250310A (en) * | 2016-07-25 | 2016-12-21 | 微梦创科网络科技（中国）有限公司 | A kind of method for generating test case and device |
| CN106815138A (en) * | 2015-12-01 | 2017-06-09 | 北京奇虎科技有限公司 | A kind of method and apparatus for generating interface testing use-case |
| CN107368407A (en) * | 2016-05-11 | 2017-11-21 | 北京京东尚科信息技术有限公司 | Information processing method and device |
| CN107423214A (en) * | 2017-04-18 | 2017-12-01 | 恒生电子股份有限公司 | Software regression testing use-case acquisition methods, device and storage medium and electronic equipment |
| CN107436767A (en) * | 2017-07-31 | 2017-12-05 | 杭州安恒信息技术有限公司 | The optimization method that idempotent operates in a kind of asynchronous framework |
| CN107515826A (en) * | 2017-08-28 | 2017-12-26 | 广州阿里巴巴文学信息技术有限公司 | Test case accurate recommendation method, device, system, equipment and storage medium |
| CN107562621A (en) * | 2017-08-28 | 2018-01-09 | 广州阿里巴巴文学信息技术有限公司 | The method and apparatus for determining manual test use-case and tested code incidence relation |
| US20180039570A1 (en) * | 2016-08-05 | 2018-02-08 | International Business Machines Corporation | Prioritizing resiliency tests of microservices |
| CN108763094A (en) * | 2018-06-01 | 2018-11-06 | 百度在线网络技术（北京）有限公司 | Method for generating test case, device, equipment and storage medium |
| CN108874672A (en) * | 2018-06-19 | 2018-11-23 | 腾讯科技（深圳）有限公司 | Application exception localization method, device, equipment and storage medium |
| CN108874680A (en) * | 2018-07-09 | 2018-11-23 | 上海瀚银信息技术有限公司 | A kind of method for testing software and system of automation |
| CN108984388A (en) * | 2018-06-01 | 2018-12-11 | 平安壹钱包电子商务有限公司 | A kind of method and terminal device generating automatic test cases |
| CN109062809A (en) * | 2018-09-20 | 2018-12-21 | 北京奇艺世纪科技有限公司 | Method for generating test case, device and electronic equipment on a kind of line |
| CN109766272A (en) * | 2018-12-26 | 2019-05-17 | 深圳壹账通智能科技有限公司 | Test method, device, terminal and the storage medium of self-service withdrawal application software |
| CN110134584A (en) * | 2019-04-12 | 2019-08-16 | 深圳壹账通智能科技有限公司 | A kind of generation method, device, storage medium and the server of interface testing use-case |
-
2019
- 2019-10-15 CN CN201910978504.3A patent/CN110727597B/en active Active
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080172652A1 (en) * | 2007-01-15 | 2008-07-17 | Microsoft Corporation | Identifying Redundant Test Cases |
| GB2508643A (en) * | 2012-12-07 | 2014-06-11 | Ibm | Method for Performing a Regression Test after Modifying Source Code File |
| CN103235759A (en) * | 2013-05-15 | 2013-08-07 | 百度在线网络技术（北京）有限公司 | Method and device for generating test cases |
| CN103473171A (en) * | 2013-08-28 | 2013-12-25 | 北京信息科技大学 | Coverage rate dynamic tracking method and device based on function call paths |
| US9442830B1 (en) * | 2014-06-25 | 2016-09-13 | Emc Corporation | Automated test coverage analysis, execution and reporting |
| CN104536895A (en) * | 2015-01-12 | 2015-04-22 | 牟永敏 | Test process tracking method and system for Java function call path |
| CN106815138A (en) * | 2015-12-01 | 2017-06-09 | 北京奇虎科技有限公司 | A kind of method and apparatus for generating interface testing use-case |
| CN107368407A (en) * | 2016-05-11 | 2017-11-21 | 北京京东尚科信息技术有限公司 | Information processing method and device |
| CN106250310A (en) * | 2016-07-25 | 2016-12-21 | 微梦创科网络科技（中国）有限公司 | A kind of method for generating test case and device |
| US20180039570A1 (en) * | 2016-08-05 | 2018-02-08 | International Business Machines Corporation | Prioritizing resiliency tests of microservices |
| CN107423214A (en) * | 2017-04-18 | 2017-12-01 | 恒生电子股份有限公司 | Software regression testing use-case acquisition methods, device and storage medium and electronic equipment |
| CN107436767A (en) * | 2017-07-31 | 2017-12-05 | 杭州安恒信息技术有限公司 | The optimization method that idempotent operates in a kind of asynchronous framework |
| CN107562621A (en) * | 2017-08-28 | 2018-01-09 | 广州阿里巴巴文学信息技术有限公司 | The method and apparatus for determining manual test use-case and tested code incidence relation |
| CN107515826A (en) * | 2017-08-28 | 2017-12-26 | 广州阿里巴巴文学信息技术有限公司 | Test case accurate recommendation method, device, system, equipment and storage medium |
| CN108763094A (en) * | 2018-06-01 | 2018-11-06 | 百度在线网络技术（北京）有限公司 | Method for generating test case, device, equipment and storage medium |
| CN108984388A (en) * | 2018-06-01 | 2018-12-11 | 平安壹钱包电子商务有限公司 | A kind of method and terminal device generating automatic test cases |
| CN108874672A (en) * | 2018-06-19 | 2018-11-23 | 腾讯科技（深圳）有限公司 | Application exception localization method, device, equipment and storage medium |
| CN108874680A (en) * | 2018-07-09 | 2018-11-23 | 上海瀚银信息技术有限公司 | A kind of method for testing software and system of automation |
| CN109062809A (en) * | 2018-09-20 | 2018-12-21 | 北京奇艺世纪科技有限公司 | Method for generating test case, device and electronic equipment on a kind of line |
| CN109766272A (en) * | 2018-12-26 | 2019-05-17 | 深圳壹账通智能科技有限公司 | Test method, device, terminal and the storage medium of self-service withdrawal application software |
| CN110134584A (en) * | 2019-04-12 | 2019-08-16 | 深圳壹账通智能科技有限公司 | A kind of generation method, device, storage medium and the server of interface testing use-case |
Non-Patent Citations (2)
| Title |
|---|
| 孙冉;牟永敏;沈美娥;: "面向Python的函数调用路径静态提取方法研究" * |
| 沈晴;牟永敏;: "函数调用路径测试用例自动生成的方法研究" * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297058A (en) * | 2020-04-27 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Case generation method, test method, device and server |
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
| CN113760690A (en) * | 2020-06-05 | 2021-12-07 | 腾讯科技（深圳）有限公司 | Method and device for analyzing program interface and computer equipment |
| CN113760690B (en) * | 2020-06-05 | 2024-09-20 | 腾讯科技（深圳）有限公司 | Method, device and computer equipment for analyzing program interface |
| CN112416772A (en) * | 2020-11-23 | 2021-02-26 | 中信银行股份有限公司 | Test case completion method and device, electronic equipment and readable storage medium |
| CN112732335A (en) * | 2021-01-12 | 2021-04-30 | 平安资产管理有限责任公司 | Object code extraction method, device, computer equipment and storage medium |
| CN112732335B (en) * | 2021-01-12 | 2024-05-31 | 平安资产管理有限责任公司 | Object code extraction method, device, computer equipment and storage medium |
| CN112948258A (en) * | 2021-03-26 | 2021-06-11 | 杭州万高科技股份有限公司 | Code testing method, device, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110727597B (en) | 2023-03-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110727597B (en) | Method for checking invalid code completion case based on log | |
| CN106951345B (en) | Consistency test method and device for disk data of virtual machine | |
| US9262283B2 (en) | Method for reading kernel log upon kernel panic in operating system | |
| US8397104B2 (en) | Creation of test plans | |
| US20150193336A1 (en) | Computing device and method for recording system event logs of computing device | |
| CN103839591A (en) | Automatic fault detection and fault-tolerant circuit of memory as well as control method | |
| CN103778030A (en) | Write-in method, error tracking method and processor for blog subsystem | |
| CN108874441B (en) | Board card configuration method, device, server and storage medium | |
| CN111104246A (en) | Method and device for improving verification efficiency of DRAM error detection and correction, computer equipment and storage medium | |
| CN110597704B (en) | Pressure test method, device, server and medium for application program | |
| CN108255644B (en) | File system recovery method and device | |
| CN114155906A (en) | Data block repairing method, device, equipment and storage medium | |
| CN114385418A (en) | Protection method, device, equipment and storage medium for communication equipment | |
| JP2005149501A (en) | System and method for testing memory with expansion card using dma | |
| CN116930727B (en) | Chip detection method based on circuit board | |
| CN108197041B (en) | Method, device and storage medium for determining parent process of child process | |
| CN103294573B (en) | A kind of intelligent terminal and data back up method thereof | |
| CN109686397B (en) | Memory with self-checking function and its checking method | |
| CN110826114B (en) | User data testing method and device based on SSD after safe erasure | |
| JP2005149503A (en) | System and method for testing memory using dma | |
| CN112463042B (en) | Data volume import data verification method, device, terminal and storage medium | |
| CN110767258B (en) | Data erasure command test method and related device | |
| CN114676049A (en) | Case testing method and device, electronic equipment and storage medium | |
| CN114267402A (en) | Bad storage unit testing method, device, equipment and storage medium of flash memory | |
| CN108231134B (en) | RAM yield remediation method and device |
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 |