CN106339312B - API test method and system - Google Patents
API test method and system Download PDFInfo
- Publication number
- CN106339312B CN106339312B CN201510422832.7A CN201510422832A CN106339312B CN 106339312 B CN106339312 B CN 106339312B CN 201510422832 A CN201510422832 A CN 201510422832A CN 106339312 B CN106339312 B CN 106339312B
- Authority
- CN
- China
- Prior art keywords
- api
- test
- case
- basic
- generating
- 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.)
- Active
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention relates to an API testing method and system, wherein the method comprises the following steps: loading an entry script; loading a configuration file, a shared function library and a framework module; generating a test case by utilizing a pre-generated API basic case template; executing the test case to obtain an API test result; and outputting the API test result in a log form. The API testing method and the system can improve the efficiency of API testing.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an API testing method and system.
Background
An API (Application Programming Interface) is a predefined function that is intended to provide applications and developers the ability to access a set of routines based on certain software or hardware, without accessing source code. During the running process of the application program, the API interface provided by the application program needs to be tested, for example, during the running process of the game application program, the API provided by the game application program to the lua script call needs to be tested. The Lua script is an embedded scripting language used to control applications, which are interpreted or compiled when called.
In the test process of the API, test cases need to be generated, where a case is an abstract description of a set of action sequences, and when the system executes the action sequences, corresponding results are generated, and the results are fed back to the participants or used as parameters of other cases. The test case refers to a case for testing generated in the API testing process. Because the number of API interfaces provided by the application program is large, and each API interface may need multiple test cases to be verified according to different input and output, the test cases generated by the traditional API test method need to be rewritten with a large number of codes according to different scenes, and the process is very complicated, so that the test efficiency is reduced.
Disclosure of Invention
In view of the above, it is necessary to provide an API testing method and system capable of improving testing efficiency.
An API testing method, the method comprising the steps of:
loading an entry script;
loading a configuration file, a shared function library and a framework module;
generating a test case by utilizing a pre-generated API basic case template;
executing the test case to obtain an API test result;
and outputting the API test result in a log form.
An API testing system, the system comprising:
the loading module is used for loading an inlet script, loading a configuration file, a shared function library and a framework module;
the case initialization module is used for generating a test case by utilizing a pre-generated API basic case template;
the case execution module is used for executing the test case to obtain an API test result;
and the result output module is used for outputting the API test result in a log form.
According to the API test method and the API test system, in the process of testing the API, the pre-generated API basic case template is used for generating the test cases, the test cases can be directly generated by the pre-generated API basic case template for some API test cases, when the test cases are generated for different scenes, the test cases for different scenes can be generated only by slightly changing the codes in the API basic case template, and compared with the traditional mode that a large number of codes need to be written, the API test method and the system can improve the test efficiency.
Drawings
FIG. 1 is a flow diagram of a method for API testing in one embodiment;
FIG. 2 is a schematic diagram of an automated test framework in one embodiment;
FIG. 3 is a flow diagram of a method for API testing in another embodiment;
FIG. 4 is a flow diagram of a method for generating test cases using API base case templates, according to one embodiment;
FIG. 5 is a use case class diagram of an API base use case template in one embodiment;
FIG. 6 is a diagram of an API interface resulting from an output in one embodiment;
FIG. 7 is a flow diagram that illustrates a method for performing performance testing on an API, in accordance with one embodiment;
FIG. 8 is a diagram illustrating monitoring memory data in one embodiment;
FIG. 9 is a schematic diagram of a portion of an API execution log in one embodiment;
FIG. 10 is a flow diagram that illustrates a methodology for stress testing of test cases, under an embodiment;
FIG. 11 is a diagram illustrating associating performance data with test cases, according to one embodiment;
FIG. 12 is a block diagram of the architecture of the API test system in one embodiment;
FIG. 13 is a block diagram showing the structure of an API test system in another embodiment;
FIG. 14 is a block diagram showing the structure of an API test system in still another embodiment;
FIG. 15 is a block diagram showing the structure of an API test system in another embodiment.
Detailed Description
As shown in fig. 1, in one embodiment, there is provided an API testing method, the method comprising:
As shown in fig. 2, in order to implement a framework template for API testing, APICheckMain is an entry script, Base Define is a basic definition, Config is a configuration file, Frame is a framework module, public is a common function library, Test Case is a Test Case, Log is a Log, Mail is Mail push, API _ DoInit is a Case initialization module, API _ DoAction is a Case execution module, API _ doevaluegat is a Test Case verification module, and API _ DoClear is a Test scenario restoration module.
In this embodiment, some key configuration items may be defined by using configuration files, including but not limited to managing all paths of use case files in a table so as to implement execution of use cases only under certain specific paths, managing APIs that need to be executed and APIs that need to be filtered in a table, and setting execution priorities that implement different orders for multiple executions of use cases. For example, the key configuration items are defined as: and only executing the API test in the configuration table or not executing the API test in the configuration table, configuring the case loading directory, configuring the loading time interval of each scene case directory and the loading time interval of each scene case file, the number of executed loops of each API, the execution sequence of the API and the like. The order of API execution includes, among others, cross execution (such as execution in the order of API1- > API2- > API3- > API1- > API2- > API3 …) and loop execution (such as execution in the order of API1- > API1- > API2- > API2- > API3- > API3 …). In a specific example, such as an example of testing an API provided by a game application to a lua script, the key configuration items further include whether or not to start automatic execution after a character logs in a server, how long to start automatic execution, whether or not to test all characters in the current server, and the like.
In this embodiment, the public function library public provides a method for frame general. The Frame module Frame is used for realizing a shared interface and method, and when generating a specific test case, the specific test case is realized on the basis of the base class in the Frame module.
And 130, generating a test case by using the pre-generated API basic case template.
In this embodiment, basic use case templates of each API are generated in advance, and the API basic use case templates specify basic information of use cases. Specifically, the description information of the API is obtained according to an API basic case template, a corresponding test case is generated by using the API name as a file name, and corresponding parameters and related function definitions are modified according to different scenes.
And 140, executing the test case to obtain an API test result.
In this embodiment, when executing the test case, a copy of the test case may be obtained by copying the test case first, and then the copy of the test case may be executed. And in the process of executing the test case copy, initializing API parameters and executing API call to obtain an execution result, judging whether the execution result is consistent with a preset execution result, if so, verifying the API, and otherwise, not verifying the API.
And 150, outputting the API test result in a log form.
In this embodiment, the API test result is finally output in the form of a log, and further, the output log may be pushed in the form of an email.
In the embodiment, in the process of testing the API, the pre-generated API basic case template is used for generating the test cases, for some API test cases, the pre-generated API basic case template can be directly used for generating the test cases, and when the test cases are generated aiming at different scenes, the test cases aiming at different scenes can be generated only by slightly changing the codes in the API basic case template.
In another embodiment, as shown in FIG. 3, an API testing method includes the steps of:
In this embodiment, the description of the entry script, the configuration file, the common function library and the framework module is as described above, and is not repeated here.
And step 306, generating a test case by using the pre-generated API basic case template.
In this embodiment, a test case may be generated according to the basic case template of each API, and then the corresponding parameters and corresponding function definitions may be modified according to the scenario.
At step 308, the API parameters are initialized and API calls are executed.
In this embodiment, after the test case is generated, a copy of the test case is copied to obtain a test case copy, the test case copy is executed, and for the test case copy of the API, the API parameters are initialized and the API call is executed to obtain a result of executing the API call. Taking a game application program as an example, the game application program provides an API interface called by the lua script, the lua script generates a test case, and a calling result is obtained in the process of calling the APIs.
In this embodiment, the execution result logic value of the API may be preset so as to determine the result of executing the API call, and if the execution result matches the execution result logic value, it indicates that the correctness verification of the API passes, otherwise, the verification fails.
At step 312, a clean-up is performed.
And after judging the execution result, cleaning to restore the scene.
And step 314, outputting an execution result log.
In this embodiment, the API test result is finally output in the form of a log, and further, the output log may be pushed in the form of an email.
Further, in an embodiment, as shown in fig. 4, the step of sending out a use case template to generate a test case by using a pre-generated API includes:
And generating a basic case template of each API in advance, and generating an API basic case template script according to the basic case template of each API.
Specifically, in an embodiment, the process of generating the API basic use case template script is as follows: acquiring a base class of a well-defined API test case, wherein the base class comprises case basic information and a case execution sequence; and generating a basic use case template of each API according to the base class, and generating an API basic use case template script.
In this embodiment, the use case basic information includes an API name and API description information, and the use case execution sequence includes initialization, execution, result check, data reduction, and the like, that is, a series of processes of initializing, executing API call, checking the result of API call, and finally performing data reduction when executing the test case of the API are defined in advance. Taking a lua script used in a game application program as an example, as shown in fig. 5, a use case class diagram of an API base use case template is used, a base class defining all API test cases is APICheckTask, and a framework of the API test case template (APICheckTase _ API _ createectype in the class diagram shown in fig. 5) is implemented by a script generateframe.
In this embodiment, the API base template script is read, an unused API list defined by the application program is obtained, the definition description information of the API is obtained from the unused API list, and a test case corresponding to the API is generated according to the definition description information by using the API name as a file name.
And step 406, modifying the corresponding parameters and the corresponding function definitions of the test cases according to the scenes.
In the embodiment, for different scenes, the test cases of the APIs for different scenes can be generated only by modifying the parameters corresponding to the test cases and the corresponding function definitions, that is, the test cases for different scenes can be generated only by modifying a small part of codes in the script, so that the efficiency of API testing is improved.
Further, since the number of APIs that an application can provide calls is very large, how to quickly obtain the API interface provided by the application is a problem to be solved. In one embodiment, the process of obtaining the API interface is: calling a preset registration function, and resolving the API interface name matched with the pattern and the definition realization of the corresponding function according to the function format, wherein the API interface is defined to call the registration function.
In this embodiment, the application defines an API interface calling system function, that is, a registration function, and calling the registration function can be implemented by parsing the API interface name matched with the pattern and defining the corresponding function according to the function format. Taking the example of a game application providing an API for a lua script, the functions called by the lua script all have a uniform format: typedef int (. mua _ cfuct) (lua _ State. L), this function accepts a single parameter lua _ State and outputs the number of return values. The registration function is: void lua register (lua _ State L, const char name, lua _ CFunction f); setting the function f into the global variable name, and realizing through macro definition: in the method, the number of API interfaces acquired by the method is shown in fig. 6, wherein the spaces are preceded by API interface names and followed by lua _ CFunction functions.
Further, besides verifying the correctness of the API (see the flow shown in fig. 1 and fig. 3), the performance of the API can also be verified. As shown in FIG. 7, in one embodiment, the process of validating the performance of the API includes:
In this embodiment, the test cases of each API are executed according to a loop sequence defined in the test framework, for example, according to an order of API1- > API2- > API2- > API2- > API3- > API3 …, n times of polling of each API test case are performed according to the polling times defined in the configuration file, and performance monitoring is started in the execution process, for example, memory data, uplink traffic, downlink traffic, hard disk time, and the like are monitored.
It is understood that the process of verifying the performance of the API may be performed after the step of generating the test case by using the API basic case template, or may be performed after the correctness of the API is verified.
In this embodiment, performance monitoring is started in the execution process, the monitored performance data can be displayed through the interface, and when an abnormality occurs in a certain data, a corresponding time point is obtained. As shown in fig. 8, at 8: 09 memory growth is not released, the time point of occurrence of the exception is 8: and 09 points.
In this embodiment, the test case executing the API outputs an API execution log, and searches for a plurality of test cases of the API executed at a corresponding time point according to the time point where the abnormality occurs. As shown in fig. 9, the test case of the API executed by the time-corresponding frame selection part is the test case with the exception.
Step 708, performing a pressure test on the plurality of test cases, and determining the API causing the performance abnormity and parameter transmission thereof.
In this embodiment, since a plurality of abnormal test cases are obtained according to the time point when the performance data is abnormal, the test cases need to be subjected to a pressure test to find a certain test case with abnormal performance.
Specifically, in an embodiment, as shown in fig. 10, the step of performing a pressure test on the plurality of test cases and determining the API causing the performance to be abnormal and the parameter transmission thereof includes:
In this embodiment, a plurality of test cases are repeatedly executed, and the performance data monitored in the execution process is also displayed through the interface, as shown in fig. 11, which shows the memory data monitored in the execution process.
And step 1004, acquiring a time point corresponding to the performance data with abnormity.
Specifically, monitored performance data may be associated with the API scenario log. In one embodiment, step 1004 specifically includes: graphically displaying the monitored performance data; when the cursor position is at the position where the performance data is abnormal, reading the name of the test case executed at the time point corresponding to the position where the performance data is abnormal, and displaying the name; and associating the performance data monitoring log with the API scene log through a time point.
The API scenario log refers to a log of API execution in a certain scenario. In this embodiment, the API scene log is associated with the performance data record, so that reading of the API function name in the API scene log is supported in the performance data display interface. As shown in fig. 11, when a mouse is used to point to a sharp corner of the memory data, the name of the API function at the corresponding time point, that is, the test case of the API, may be directly displayed in the interface. Therefore, the test case with abnormal performance can be found more intuitively without checking against two data logs, and the test efficiency is improved.
In this embodiment, the API is subjected to performance verification, so that a module with abnormal performance can be found out, a module with a performance problem is subjected to a pressure test, a case script of the API with a problem can be found out, the case script of the API is analyzed, a specific problem can be found out, and the case script of the API is modified. Therefore, the API test is more comprehensive, and the API can be perfected by repairing the case script of the abnormal API. For example, for a certain game application program, in the running process, the API called by the lua script provided by the game application program is tested, and if a memory leak occurs when the API for creating a copy is called, then loop creation check may be performed on each copy in sequence, and finally, it is accurately located that a memory leak occurs when a certain copy is created.
As shown in FIG. 12, in one embodiment, an API testing system is provided, the system comprising:
and the loading module 1202 is used for loading an entry script, a configuration file, a common function library and a framework module.
The use case initialization module 1204 is configured to generate a test case by using a pre-generated API base use case template.
The case execution module 1206 is configured to execute the test case to obtain an API test result.
And a result output module 1208, configured to output the API test result in a log form.
In one embodiment, the use case initialization module 1204 is configured to read an API base use case template script; acquiring definition description information of an API (application program interface) provided by an application program, and generating a test case according to the definition description information; and modifying the corresponding parameters and the related function definitions of the test cases according to the scenes.
In one embodiment, as shown in fig. 13, the API testing system further includes:
a use case template generating module 1203, configured to obtain base classes of the defined API test users, where the base classes include use case basic information and a use case execution sequence; and generating a basic use case template of each API according to the base class, and generating an API basic use case template script.
In one embodiment, the API testing system further comprises:
the API interface obtaining module 1201 is configured to call a preset registration function, and parse the pattern-matched API interface name and the definition implementation of the corresponding function according to the function format, where the API interface is defined to call the registration function.
In one embodiment, as shown in fig. 15, the API testing system further includes:
the performance testing module 1205 is configured to perform polling execution on the test cases of the APIs according to the calling order of the APIs, and start performance monitoring in the execution process; acquiring a time point corresponding to the performance data with abnormality; acquiring a plurality of test cases corresponding to the API executed at the time point; and performing pressure test on the plurality of test cases, and determining the API causing the performance abnormity and parameter transmission thereof.
Further, in an embodiment, the performance test module 1205 is configured to repeatedly execute the plurality of test cases, and monitor performance data during the execution process; acquiring a time point corresponding to the performance data with abnormality; and acquiring the test case corresponding to the API executed at the time point, and determining the API with abnormal performance and parameter transmission thereof.
Further, in one embodiment, the performance testing module 1205 is configured to graphically display the monitored performance data; when the cursor position is at the position where the performance data is abnormal, reading the name of the test case executed at the time point corresponding to the position where the performance data is abnormal, and displaying the name; and associating the performance data monitoring log with the API scene log through a time point.
It will be understood by those skilled in the art that all or part of the processes in the methods of the embodiments described above may be implemented by hardware related to instructions of a computer program, which may be stored in a computer readable storage medium, for example, in the storage medium of a computer system, and executed by at least one processor in the computer system, so as to implement the processes of the embodiments including the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An API testing method, the method comprising the steps of:
loading a pre-configured entry script;
loading a corresponding configuration file, a common function library and a frame module according to the entry script, wherein the configuration file comprises all use case file paths managed by a table so as to realize that only use cases under a specific path are executed, APIs required to be executed and APIs required to be filtered are managed by the table, and configuration information for realizing different orders of execution priorities aiming at multiple executions of the use cases is set;
generating a test case by utilizing a pre-generated API basic case template based on the method provided by the shared function library, the method provided by the shared function library and the base class in the frame module by the frame module;
executing the test case according to the configuration information contained in the configuration file to obtain an API test result;
outputting the API test result in a log form;
the step of generating the test case by utilizing the pre-generated API basic case template comprises the following steps:
acquiring a basic case template of each API, and generating a test case according to the basic case template of each API;
modifying the corresponding parameters and the related function definitions of the test cases according to the scenes;
the step of obtaining the basic case template of each API and generating the test case according to the basic case template of each API comprises the following steps:
reading an API basic case template script;
acquiring definition description information of an API (application program interface) provided by an application program, and generating a test case according to the definition description information;
before the step of loading the pre-configured entry script, further comprising:
acquiring a base class of a defined API test user, wherein the base class comprises use case basic information and a use case execution sequence, the use case basic information comprises an API name and API description information, and the use case execution sequence comprises initialization, execution, result check and data reduction;
and generating a basic use case template of each API according to the base class, and generating the API basic use case template script.
2. The API testing method of claim 1, prior to said step of loading a preconfigured entry script, further comprising:
calling a preset registration function, and resolving the API interface name matched with the pattern and the definition realization of the corresponding function according to the function format, wherein the API interface is defined to call the registration function.
3. The API testing method according to claim 1, further comprising, after the step of generating the test case using the pre-generated API basic case template:
polling and executing the test cases of each API according to the calling sequence of the API, and starting performance monitoring in the executing process;
acquiring a time point corresponding to the performance data with abnormality;
acquiring a plurality of test cases corresponding to the API executed at the time point;
and performing pressure test on the plurality of test cases, and determining the API causing the performance abnormity and parameter transmission thereof.
4. The API testing method according to claim 3, wherein the step of performing a pressure test on the plurality of test cases to determine the API whose performance is abnormal and the parameter thereof to be transmitted includes:
repeatedly executing the plurality of test cases, and monitoring performance data in the executing process;
acquiring a time point corresponding to the performance data with abnormality;
and acquiring the test case corresponding to the API executed at the time point, and determining the API with abnormal performance and parameter transmission thereof.
5. The API testing method according to claim 4, wherein the step of obtaining the test case corresponding to the API executed at the time point comprises:
graphically displaying the monitored performance data;
when the cursor position is at the position where the performance data is abnormal, reading the name of the test case executed at the time point corresponding to the position where the performance data is abnormal, and displaying the name;
and associating the performance data monitoring log with the API scene log through a time point.
6. An API test system, the system comprising:
the loading module is used for loading a pre-configured entry script, loading a corresponding configuration file, a shared function library and a frame module according to the entry script, wherein the configuration file comprises all use case file paths managed by a table so as to realize that only use cases under a specific path are executed, APIs required to be executed and APIs required to be filtered are managed by the table, and configuration information for realizing execution priorities in different sequences aiming at multiple executions of the use cases is set;
the case initialization module is used for generating a test case by utilizing a pre-generated API basic case template based on the method provided by the shared function library, the method provided by the frame module according to the shared function library and the base class in the frame module;
the case execution module is used for executing the test case according to the configuration information contained in the configuration file to obtain an API test result;
the result output module is used for outputting the API test result in a log form;
the case initialization module is further used for acquiring basic case templates of all the APIs and generating test cases according to the basic case templates of all the APIs;
modifying the corresponding parameters and the related function definitions of the test cases according to the scenes;
the case initialization module is used for reading API basic case template scripts; acquiring definition description information of an API (application program interface) provided by an application program, and generating a test case according to the definition description information;
the system further comprises: the case template generation module is used for acquiring the base class of the well-defined API test user, and comprises case basic information and a case execution sequence; and generating a basic use case template of each API according to the base class, and generating the API basic use case template script.
7. The system of claim 6, further comprising:
and the API interface acquisition module is used for calling a preset registration function and resolving the definition realization of the API interface name matched with the mode and the corresponding function according to the function format, wherein the API interface is defined to call the registration function.
8. The system of claim 6, further comprising:
the performance testing module is used for performing polling execution on the test cases of the APIs according to the calling sequence of the APIs and starting performance monitoring in the execution process; acquiring a time point corresponding to the performance data with abnormality; acquiring a plurality of test cases corresponding to the API executed at the time point; and performing pressure test on the plurality of test cases, and determining the API causing the performance abnormity and parameter transmission thereof.
9. The system of claim 8, wherein the performance testing module is configured to repeatedly execute the plurality of test cases and monitor performance data during execution; acquiring a time point corresponding to the performance data with abnormality; and acquiring the test case corresponding to the API executed at the time point, and determining the API with abnormal performance and parameter transmission thereof.
10. The system of claim 9, wherein the performance testing module is configured to graphically display the monitored performance data; when the cursor position is at the position where the performance data is abnormal, reading the name of the test case executed at the time point corresponding to the position where the performance data is abnormal, and displaying the name; and associating the performance data monitoring log with the API scene log through a time point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510422832.7A CN106339312B (en) | 2015-07-17 | 2015-07-17 | API test method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510422832.7A CN106339312B (en) | 2015-07-17 | 2015-07-17 | API test method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106339312A CN106339312A (en) | 2017-01-18 |
| CN106339312B true CN106339312B (en) | 2021-01-12 |
Family
ID=57826839
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510422832.7A Active CN106339312B (en) | 2015-07-17 | 2015-07-17 | API test method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106339312B (en) |
Families Citing this family (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108572898B (en) * | 2017-03-07 | 2021-11-02 | 北京京东尚科信息技术有限公司 | Method, device, equipment and storage medium for controlling interface |
| CN108664384B (en) * | 2017-03-29 | 2021-05-07 | 富士通株式会社 | Data processing apparatus and data processing method |
| CN107247660A (en) * | 2017-05-05 | 2017-10-13 | 北京奇虎科技有限公司 | The method of testing and test device of a kind of interface |
| CN107124335A (en) * | 2017-06-30 | 2017-09-01 | 郑州云海信息技术有限公司 | One kind is based on cloud sea operating system platform test method and system |
| CN107402884A (en) * | 2017-07-31 | 2017-11-28 | 深圳乐信软件技术有限公司 | Generate the method and device of interface testing code |
| CN107861864A (en) * | 2017-08-25 | 2018-03-30 | 平安普惠企业管理有限公司 | Automated testing method, system and computer-readable recording medium |
| CN107797898B (en) * | 2017-09-28 | 2020-11-27 | 东软集团股份有限公司 | Data acquisition method and device thereof |
| CN107766101B (en) * | 2017-09-30 | 2021-02-19 | 五八有限公司 | Method, device and equipment for processing App starting event |
| CN108628738A (en) * | 2018-01-11 | 2018-10-09 | 百富计算机技术（深圳）有限公司 | The generation method and device of application programming interface test case |
| CN108415829B (en) * | 2018-02-02 | 2022-02-01 | 福建天晴数码有限公司 | Method and terminal for detecting time consumed by loading module |
| CN109344063A (en) * | 2018-09-26 | 2019-02-15 | 深圳竹云科技有限公司 | A kind of automated testing method of api interface |
| CN110232018A (en) * | 2019-05-17 | 2019-09-13 | 浙江数链科技有限公司 | Interface test method, device, computer equipment |
| CN110955593B (en) * | 2019-10-28 | 2023-07-14 | 北京三快在线科技有限公司 | Client testing method and device, electronic equipment and readable storage medium |
| CN113495829A (en) * | 2020-03-20 | 2021-10-12 | 北京海致星图科技有限公司 | Automatic interface testing method and system |
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
| CN112783769A (en) * | 2021-01-19 | 2021-05-11 | 深圳市莫廷影像技术有限公司 | Self-defined automatic software testing method |
| CN114968754A (en) * | 2021-02-26 | 2022-08-30 | 华为云计算技术有限公司 | Application program interface API test method and device |
| CN113518015B (en) * | 2021-04-08 | 2023-03-14 | 重庆长安汽车股份有限公司 | Automatic realization method based on vehicle machine CAN network signal test |
| CN115656792B (en) * | 2022-12-29 | 2023-03-17 | 摩尔线程智能科技(北京)有限责任公司 | Test method and test platform for chip testability design |
| CN115684895B (en) * | 2022-12-29 | 2023-03-21 | 摩尔线程智能科技(北京)有限责任公司 | Chip testability design test method, test platform, and generation method and device thereof |
| CN117724989A (en) * | 2024-02-18 | 2024-03-19 | 粤港澳大湾区数字经济研究院(福田) | Regression testing method and device for interface, terminal and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212362A (en) * | 2006-12-26 | 2008-07-02 | 中兴通讯股份有限公司 | Automatic testing device and method incorporating a variety of testing tools |
| US20080184206A1 (en) * | 2007-01-31 | 2008-07-31 | Oracle International Corporation | Computer-implemented methods and systems for generating software testing documentation and test results management system using same |
| CN104123227A (en) * | 2014-08-13 | 2014-10-29 | 广东电网公司信息中心 | Method for automatically generating testing cases |
| CN104598776A (en) * | 2013-10-31 | 2015-05-06 | 深圳市腾讯计算机系统有限公司 | Method and device for testing software |
-
2015
- 2015-07-17 CN CN201510422832.7A patent/CN106339312B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212362A (en) * | 2006-12-26 | 2008-07-02 | 中兴通讯股份有限公司 | Automatic testing device and method incorporating a variety of testing tools |
| US20080184206A1 (en) * | 2007-01-31 | 2008-07-31 | Oracle International Corporation | Computer-implemented methods and systems for generating software testing documentation and test results management system using same |
| CN104598776A (en) * | 2013-10-31 | 2015-05-06 | 深圳市腾讯计算机系统有限公司 | Method and device for testing software |
| CN104123227A (en) * | 2014-08-13 | 2014-10-29 | 广东电网公司信息中心 | Method for automatically generating testing cases |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106339312A (en) | 2017-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106339312B (en) | API test method and system | |
| US9898396B2 (en) | Automated software testing and validation via graphical user interface | |
| US9465718B2 (en) | Filter generation for load testing managed environments | |
| US20160283353A1 (en) | Automated software testing | |
| US20140298297A1 (en) | Automatic feature-driven testing and quality checking of applications | |
| US8661414B2 (en) | Method and system for testing an order management system | |
| CN114546738A (en) | Server general test method, system, terminal and storage medium | |
| CN113127347A (en) | Interface testing method, device, equipment and readable storage medium | |
| US10592703B1 (en) | Method and system for processing verification tests for testing a design under test | |
| CN112181749A (en) | Hardware testing method and device, electronic equipment and storage medium | |
| EP3734460B1 (en) | Probabilistic software testing via dynamic graphs | |
| CN111221721B (en) | Automatic recording and executing method and device for unit test cases | |
| CN111159028B (en) | Webpage testing method and device | |
| CN106909434B (en) | Method and device for detecting undefined function in executable program | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN109684205B (en) | System testing method, device, electronic equipment and storage medium | |
| US20130283238A1 (en) | Testing system for an integrated software system | |
| CN113806209A (en) | Interface testing method, frame, computer device and storage medium | |
| US10481969B2 (en) | Configurable system wide tests | |
| CN114676066A (en) | Security testing method and device for target application, electronic equipment and storage medium | |
| CN112069508B (en) | Method, system, device and medium for positioning vulnerability API (application program interface) parameters of machine learning framework | |
| CN114416547A (en) | Test case based test method | |
| CN111625459A (en) | Application program testing method and device, computer equipment and storage medium | |
| US20100293018A1 (en) | Test Model Abstraction For Testability in Product Line Engineering | |
| CN113946333B (en) | Mobile terminal logic script execution method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | 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 |