CN117459416A - Interface testing method and device, electronic equipment and readable storage medium - Google Patents
Interface testing method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN117459416A CN117459416A CN202311543520.2A CN202311543520A CN117459416A CN 117459416 A CN117459416 A CN 117459416A CN 202311543520 A CN202311543520 A CN 202311543520A CN 117459416 A CN117459416 A CN 117459416A
- Authority
- CN
- China
- Prior art keywords
- interface
- associated resource
- link
- detail
- service
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 154
- 238000000034 method Methods 0.000 claims abstract description 55
- 230000004044 response Effects 0.000 claims abstract description 49
- 238000013507 mapping Methods 0.000 claims description 37
- 238000012545 processing Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 238000004891 communication Methods 0.000 abstract description 4
- 230000008569 process Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011981 development test Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/02—Capturing of monitoring data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides an interface testing method, an interface testing device, electronic equipment and a readable storage medium, and relates to the technical field of communication, wherein the method comprises the following steps: acquiring interface path data associated with a service to be tested, wherein the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between the associated resource detail interfaces and the associated resource list interfaces in the interface path data; invoking a root link to obtain a response result; and based on the response result, sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation to execute the interface test of the service to be tested. According to the embodiment of the application, each interface in the service to be tested can be automatically tested, the testing efficiency is improved, and the degree of automation is high.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to an interface testing method, an apparatus, an electronic device, and a readable storage medium.
Background
In the related art, a global Wide area network (Web) service is generally provided with a plurality of query interfaces. Currently, testing for these query interfaces requires writing test cases one by one. In addition, since the software development process often faces the variation of the requirements, the interfaces need to be added, deleted or modified, and thus corresponding test cases need to be adjusted manually. Therefore, in the prior art, the workload of testing the interfaces arranged in the Web service is large, a great amount of time is required to be consumed by development or testing personnel, and the degree of automation testing is low.
Disclosure of Invention
The embodiment of the application provides an interface testing method, an interface testing device, electronic equipment and a readable storage medium, which are used for solving the problems of large interface testing workload and low automation testing degree in the prior art.
In order to solve the technical problems, the application is realized in the following way:
in a first aspect, an embodiment of the present application provides an interface testing method, where the method includes:
acquiring interface path data associated with a service to be tested, wherein the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between the associated resource detail interfaces and the associated resource list interfaces in the interface path data;
Invoking a root link in the associated resource interface relationship to obtain a response result;
and based on the response result, sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation so as to execute the interface test of the service to be tested.
In a second aspect, an embodiment of the present application further provides an interface testing apparatus, including:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring interface path data associated with a service to be detected, the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between each associated resource detail interface and each associated resource list interface in the interface path data;
the result module is used for calling the root links in the associated resource interface relationship to acquire a response result;
and the calling module is used for sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation based on the response result so as to execute the interface test of the service to be tested.
In a third aspect, an embodiment of the present application provides an electronic device, including: a processor, a memory, and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the interface testing method of the first aspect described above.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium, where a computer program is stored, where the computer program is executed by a processor to implement the steps of the interface testing method described in the first aspect.
In the embodiment of the application, by acquiring the associated resource details and the associated resource list interfaces in the interface path data related to the service to be tested and the relationship between the associated resource details and the associated resource list interfaces, namely the associated resource interface relationship, when the interface test of the service to be tested is carried out, only the root links in the associated resource interface relationship are required to be called, and the associated resource detail interfaces and the associated resource list interfaces related to the root links in all the associated resource interface relationships are sequentially called until the call test of all the interfaces is completed. In this way, the embodiment of the application can obtain the association resource interface relation according to the obtained interface path data association, associate all interfaces to be tested in the service to be tested, and call the association resource detail interface and the association resource list interface in the association resource interface relation without writing a test case, without manual participation, reduce the workload of interface test, execute the automated test flow of the interface and have higher degree of automation test.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is one of the flowcharts of an interface testing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of the structure of an associated resource interface relationship in one embodiment of the present application;
FIG. 3 is a second flowchart of an interface testing method according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an interface testing device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
For ease of understanding, some of the matters related to the embodiments of the present application are described below:
interface test is an indispensable link in the software development process, and is mainly used for detecting the correctness of an interface. Interface testing typically requires writing test cases first, and then using test tools, such as postman, etc., to construct test requests to invoke the service interface under test to check the correctness of the interface. The interface design style of Web services typically uses the state transfer (REpresentational State Transfer, RESTful) specification, while using hypertext as the state of an application (Hypermedia as the Engine of Application State, HATEOAS) is one of the most mature constraints and specifications in the RESTful specification that provides interaction between clients and servers through hypermedia, and decoupling between clients and servers can be achieved. The Web service designs an interface by using the HATEOAS specification so that link information can be contained in the resource interface, and the client can discover actions that can be performed according to the link information therein.
In the embodiment of the application, an interface testing method, an interface testing device, electronic equipment and a readable storage medium are provided to solve the problems that in the prior art, test cases need to be written for interface testing, testing workload is large, and automation degree is low.
Referring to fig. 1, fig. 1 is one of flowcharts of an interface testing method provided in an embodiment of the present application, as shown in fig. 1, the method includes the following steps:
step 101, obtaining interface path data associated with a service to be tested, wherein the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between the associated resource detail interfaces and the associated resource list interfaces in the interface path data.
It should be noted that, the service to be tested in the present application may correspond to a specific service in actual application, and further complete the development test of the service by performing an interface test on the service to be tested. The method and the device can be applied to Web services for automatic testing, wherein interfaces of the services to be tested can be designed according to HATEOAS specifications, and various related resource links can be added in response results of the services to be tested. Due to the self-contained nature of HATEOAS, a connection relationship between the associated resource detail interface and the associated resource list interface, which are included in the interface path data, can be determined, for example, with an associated resource interface relationship. And the interface path data of the service to be tested is not needed to construct the resource association relationship, but is needed to prevent repeated calling, and the response result body of the service to be tested can use the JSON format. The interface path data may include various related resource links in the service response body to be tested, and may specifically be an associated resource detail interface and an associated resource list interface.
It should be noted that the interfaces of the service to be tested can be divided into two types, specifically, an associated resource detail interface and an associated resource list interface. In particular, the associated resource detail interface in the present application may contain associated resource detail information and list links (links) of associated resources. And list information in the associated resource list interface associated with the list link can be obtained by directly calling the list link of the associated resource. The associated resource list link may include a plurality of associated resource list data (data), page data (page no), a size of each page (page size), and a total number of resources (total), where the associated resource list data includes brief information of the associated resource and a link (link) of a corresponding associated resource detail interface. The detail information about the resource in the associated resource detail interface can be obtained by calling a link of one associated resource detail interface in the associated resource list interface.
In the above step, the obtaining of the interface path data associated with the service to be tested may be obtaining all the interface path data associated with the service to be tested, and it may be searched whether there is an interface that is not covered yet in the interface test process, and the interface is not added to the subsequent associated resource interface relationship, so as to prevent that the display result is empty when the interface is queried due to lack of coverage of the interface path data, and the associated resource detail interface or the associated resource list interface therein cannot be invoked. In addition, the repeated calling can be avoided by acquiring all the interface path data related to the service to be tested, and the interface paths which are already called can be saved in the process of calling the interfaces because of the possible ring relation between each associated resource detail interface and the associated resource list interface in the interface path data so as to judge whether the current interface needs to be continuously called.
It can be understood that the association relationship between the association resource detail interface and the association resource list interface can be the association relationship between the existing association resource detail interface and the association resource list interface in the interface path data, and all interfaces of the service to be tested can be connected to form an association resource interface relationship. The association resource interface relationship may exist in the form of a topology map, for example, fig. 2. Fig. 2 is a schematic structural diagram of an association resource interface relationship in an embodiment of the present application, where an interface path "/" may be an interface entry of a service to be tested, by requesting the interface, an association resource list link "/resource1" and "/resource2" of the service to be tested may be obtained, and requesting one of the resource list interfaces, such as "/resource1", may obtain a resource list of the service under test. Each resource1 has a resource detail interface, such as "/resource1/111", which is called to obtain the associated resource3 list interface under resource 1. All associated resource detail interfaces and all associated resource list interfaces in the service to be tested can be connected in the mode to form a topological graph, so that an associated resource interface relation is formed.
It should be noted that, the root link in the associated resource interface relationship may be an associated resource detail interface or an associated resource list interface, as shown in fig. 2, where the root link is an associated resource list interface. Because the links corresponding to the associated resource list interface are resolved when the root links are called, the result returned by the call is not null when the root links are associated resource list links in fig. 2. And when the root link is an associated resource detail interface, the returned calling result is null.
In the above steps, by following the HATEOAS specification, all interface path data of the service to be tested is obtained in the response of the test service to the interface query of the service to be tested, and the associated resource detail interface and the associated resource list interface in the interface path data, and the relationship between the associated resource detail interface and the associated resource list interface, namely the associated resource interface relationship, are obtained. And calling each interface according to the determined associated resource interface relationship, providing a basis for automatic test, and facilitating the execution of an automatic test flow.
Step 102, calling a root link in the associated resource interface relationship to obtain a response result.
In a specific embodiment, for the execution process of each interface test of the service to be tested, a root link in the associated resource interface relationship may be called first, and the interface type of the root link may be determined according to the returned response result by calling the root link.
Step 103, based on the response result, sequentially calling the associated resource detail interface and the associated resource list interface related to the root link in the associated resource interface relation to execute the interface test of the service to be tested.
In a specific embodiment of the application, when the root link is the associated resource list interface, each associated resource detail interface in the associated resource list interface can be called, and when the root link is the associated resource detail interface, the associated resource list interface in the associated resource detail interface can be called, so that the calling of all interfaces in the associated resource interface relationship is realized, the testing of each interface in the service to be tested is completed, and the calling of the automatic testing flow is completed. Meanwhile, the interface test result can be determined according to the call feedback result, manual participation is not needed, and the automation degree is high.
It should be noted that, before the interface test is executed in the embodiment of the present application, a tester may send a test request to a test service, the test service constructs the test request after receiving the test service, and sends the test request to a service to be tested, and the service to be tested returns a test result to the test service through the embodiment described above, so as to complete the interface test of the service to be tested. Therefore, the execution body of the application may be the aforementioned test service, and the test service may be a design applied to perform an interface test on the service to be tested, which is not particularly limited in the application.
Optionally, the acquiring interface path data associated with the service to be tested includes:
acquiring all interface paths associated with the Internet application Web service based on the open source data packet;
caching all interface paths and acquiring all mapping relations in all interface paths;
determining whether the interface path corresponding to the target mapping relation is an interface path associated with the service to be tested based on the interface request method and the class name corresponding to the interface in one target mapping relation, wherein the target mapping relation is any one of the all mapping relations, and one target mapping relation comprises the interface path, the interface request method and the class name corresponding to the interface of the Web service;
obtaining the interface path associated with the service to be tested under the condition that the interface path corresponding to the target mapping relation is the interface path associated with the service to be tested;
and acquiring interface path data associated with the service to be tested based on the target mapping relation.
In a specific embodiment of the present application, the interface path data of the service to be tested may be obtained through an open source packet, for example, a spring-boot-starter-actuator open source packet is adopted, the open source packet provides interface data of all paths associated with the Web service, and the default interface path may be "/drivers/maps". By sending call requests to all the interface paths respectively, all the mapping relations (maps) of the Web service can be obtained. Because the embodiment of the application needs to test the service to be tested, and the interface path data acquired based on the open source packet contains all types of interface paths, all the interface paths need to be screened, and the interface paths needing to be tested are determined.
Specifically, after caching all the interface paths, all the mapping relations can be obtained in all the interface path data, and to obtain the specific content of each mapping relation, the content in the interface path data needs to be analyzed. The json data in the Web service interface path can be analyzed, mapping relations of the interface paths are obtained, and each mapping relation comprises the interface path, the interface request method and the class name corresponding to the interface of the Web service. And then, screening out all interface paths to be tested in the service to be tested according to the acquired interface request method and the class name corresponding to the interface.
For example, through judging logic of whether the interface request method is equal to GET, other types of requests can be filtered, and meanwhile, the interfaces under one package can be screened according to class names corresponding to the interfaces, so that an interface path which needs to be subjected to interface test in the service to be tested is finally obtained. The class name corresponding to the interface is adopted to screen the interface path, because part of interfaces possibly exist in the service to be tested without testing, and the previously adopted open source data packet, such as a spring-boot-starter-actuator packet, also provides some interfaces of the class needing to be tested, such as query interfaces of a request (GET) class sent to specific resources, which do not belong to the range of interface testing of the service to be tested, and need to be filtered. Therefore, the interface test is conveniently executed on the interface path which needs to be subjected to the interface test in the service to be tested, the test efficiency of each interface in the service to be tested is improved, and the test resources are saved.
Optionally, the sequentially calling the associated resource detail interface and the associated resource list interface related to the root link in the associated resource interface relationship to execute an interface test on the service to be tested, including:
invoking the root link;
under the condition that the interface path data of the service to be tested is newly added or modified, a query interface is called to obtain interface path data of a refreshing interface cache, wherein the query interface is connected with the refreshing interface, and the refreshing interface is an interface for caching the newly added or modified interface path data of the service to be tested in the service to be tested;
updating the associated resource interface relation based on the interface path data of the refreshing interface cache acquired by the query interface;
and sequentially calling the related resource detail interface and the related resource list interface which are related to the root link in the updated related resource interface relationship so as to execute the interface test of the service to be tested.
In a specific implementation, since the service to be tested may have iterative update of a version, an interface to be tested in the service to be tested may be newly added or modified, so that each interface path of the service to be tested needs to be updated in time, and the associated resource interface relationship is updated according to the updated interface paths, so that each associated resource detail interface and associated resource list interface can be adjusted in time according to the change of the interface paths, and the automated interface test of the service to be tested is completed without manual intervention. The degree of automation is higher.
It can be understood that a query interface can be provided in the test service, and the query interface can query all interface path data of the service to be tested, and when the interface of the service to be tested is newly increased or modified due to version upgrade and the like, the new or modified interface path information in the service to be tested can also be obtained through the query interface. Specifically, the query interface and the refresh interface may be set to connect, and the refresh interface may be set in the service to be tested, and when the interface in the service to be tested is newly added or modified, the newly added interface path data may be cached through the refresh interface, or the changed interface path data may be cached. At this time, the query interface may learn and acquire the newly added or modified interface path data through the refresh interface.
In addition, the beneficial effect achieved by the refresh interface can also be achieved by setting a refresh parameter (refresh) in the query interface. For example, the query interface may cache all interface path data of a previous version of the service to be tested, and by setting a refresh parameter in the query interface, the refresh cache of the newly added or modified interface path of the service to be tested may be implemented through the refresh parameter. When the refresh parameter indicates true (true), it means that the cache needs to be refreshed, and when the refresh parameter indicates false (false), the cache does not need to be refreshed. Wherein the default value of the refresh parameter may be set to false. Therefore, the query interface can be called before the interface test of the service to be tested is carried out, so that the latest interface path data can be conveniently pulled from the service to be tested, the interface path data of the service to be tested in the query interface can be updated, and the practicability and the version iteration adaptability are high.
Furthermore, the query interface can be called before the root link is called to acquire the interface path data of the service to be tested, the latest interface path data is acquired, the interface test requirement of the service to be tested is met, and manual participation is not needed.
Optionally, the calling the root link in the associated resource interface relationship to obtain a response result includes:
judging whether the root link is called or not;
sending a call request to the service to be tested under the condition that the root link is not called, wherein the call request is constructed based on the root link;
and calling the root link based on the calling request, and acquiring the response result of the root link.
In yet another embodiment of the present application, invoking the root link also requires a determination as to whether the root link has been invoked. Because the test service includes all interface path data of the service to be tested, and also includes the interface path on which the call test has been performed, it is necessary to determine whether the root link has been called before the call is performed. And recording and storing the called interfaces in the execution process of each interface test, and comparing the current root link with the called interfaces when the root link is used as the interface link needing to be called currently. When the comparison result shows that the root link is not called, a call request can be directly initiated to the service to be tested. The call request can be constructed based on the root link, the call request can be an http request, and the call request can be generated to the service to be tested through encoding. Therefore, whether the root link is called or not is judged, repeated calling of the interface can be effectively avoided, testing resources are saved, and the degree of automation is high.
In addition, before sending a call request to the service under test, an interface path matching the current link (e.g., root link) is required, such as the link "http:// ip: port/resource1/111" would match to interface path "/resource1/{ id }". The interface path matching mode can use an AntPathMatcher class provided in a spring framework, wherein the match method provides a path matching function.
Optionally, after the determining whether the root link is invoked, the method further includes:
and returning a first result under the condition that the root link is called, wherein the first result is used for indicating ending the call to the root link.
In one embodiment of the present application, if it is determined that the root link has been previously invoked, a first result may be directly returned, and the test service may be indicated to end the invocation of the root link through the first result. For example, if the display has been invoked, a true may be returned directly, representing that the link and its associated links have all been invoked to completion. By timely returning the instruction of ending the root link call, repeated call of the interface can be avoided, and test resources are saved.
Optionally, the obtaining the response result of the root link includes:
Receiving a response result of the service to be tested to the call request of the root link;
and acquiring a target link based on the response result, wherein the target link is associated with one associated resource list interface in the associated resource interface relation, or the target link is associated with one associated resource detail interface.
In a specific embodiment of the present application, when a service to be tested receives a call request sent by a test service, the service to be tested responds to the call request, and a result of the response result is sent to the test service. And the target link is acquired through the result of the response result, so that the content information of the response result can be saved into the memory of the test service by using the result of the key value pair after the result of the response result is acquired. The key can be set as a link, the value is a response body, and the link and the response body are correspondingly set.
Specifically, since the interface types may include two types of associated resource detail interfaces and associated resource list interfaces, the target link may be an associated resource detail interface or an associated resource list interface. The target link is also an interface belonging to the associated resource interface relationship. The response result is obtained through the invocation of the root link, and then the target link is obtained from the response result, so that the interface associated with the root link can be judged, the interface type of the target link is judged, the target link and the interfaces associated with the target link can be traversed and invoked further, the test of the interfaces of the service to be tested is completed, the manual participation is not needed, the test cost is reduced, the test resources are saved, and the degree of automation is higher.
Optionally, the sequentially calling the associated resource detail interface and the associated resource list interface in the associated resource interface relationship includes:
judging whether the target link is empty or not;
under the condition that the target link is not empty, determining that the target link is a target associated resource detail interface, and calling a list link contained in the target associated resource detail interface, wherein the associated resource interface relation comprises the target associated resource detail interface;
and under the condition that the target link is empty, determining that the target link is a target associated resource list interface, and sequentially calling each detail link contained in the target associated resource list interface, wherein the associated resource interface relation comprises the target associated resource list interface.
In yet another embodiment of the present application, after the target link is acquired, it may be first determined whether the target link is empty, and by this determination, the interface type to which the target link belongs can be determined. Specifically, when the target link is empty, it indicates that the target link is one associated resource list interface included in the associated resource interface relationship, that is, the target associated resource list interface. After determining the target associated resource list interface, one list link contained in the target associated resource list interface can be called, and the calling of all interfaces in the associated resource interface relation is completed by calling the list link or calling all interfaces associated with the list link together, so that the automatic interface test of the service to be tested is completed.
In addition, when the target link is not empty, the condition that the detail information is contained in the target link represents that the target link is an associated resource detail interface included in the associated resource interface relationship, namely, the target associated resource detail interface. After determining the detail interface of the target associated resource, one detail link contained in the detail interface of the target associated resource can be called, and by calling the detail link or calling the detail link and each interface associated with the detail link, all the associated resource list interfaces and the associated resource detail interfaces in the associated resource interface relationship are called together, so that the automatic interface test of the service to be tested is completed.
It should be noted that, the above list link corresponds to an associated resource list interface, the corresponding associated resource list interface can be located by calling the list link, meanwhile, the calling of the list link may also correspond to the calling of the corresponding associated resource list interface, the associated resource list interface includes a plurality of interface links, which are all different associated resource detail links, and the interface test of the service to be tested is completed by calling the list link and simultaneously calling the associated resource detail interface in the list link through the interface relation associated by the list link. The detail link is equivalent to an associated resource detail interface, and can be positioned to the corresponding associated resource detail interface through the calling detail link, and as the associated resource detail interface comprises an associated resource list interface, namely the calling detail link can also call the associated resource list interface therein, then other associated resource detail interfaces associated with the associated resource list interface can be called together, and the calling of all interfaces in the associated resource interface relation of the service to be tested is completed.
Optionally, the calling a list link included in the target associated resource detail interface includes:
traversing each associated resource detail interface associated with the list link contained in the target associated resource detail interface, wherein one list link corresponds to one associated resource list interface, one associated resource list interface associates N associated resource detail interfaces, and N is an integer greater than or equal to 1;
and under the condition that each associated resource detail interface is traversed, calling the detail link corresponding to each associated resource detail interface, wherein one associated resource detail interface corresponds to one detail link.
In yet another specific embodiment of the present application, after determining that the target link is an associated resource detail interface, the traversing process may determine whether any interface has been previously invoked, may exclude the interfaces that have been invoked, and may perform a call test on the interfaces that have not been invoked, so as to save test resources by traversing each associated resource detail interface associated with the list link included in the target associated resource detail interface. Then, after the traversal of each interface is completed, the call test for each interface is started. And each associated resource detail interface in the list link can be called in a recursion way through the list link until the result of calling each interface in the associated resource interface relation is obtained.
In addition, if a failure result exists in the calling result, the fact that the interfaces which are not called exist in the related resource interface relation is indicated, and the calling needs to be continued, so that the calling of all the interfaces is completed. When the returned result is true, the interface call test of the service to be tested can be ended by indicating that all interfaces complete call. Therefore, the interface calling process of the service to be tested does not need to be manually participated, and the automatic testing process is efficient and convenient.
Optionally, the sequentially calling each detail link included in the target associated resource list interface includes:
analyzing M associated resource detail data associated with the list links contained in the target associated resource list interface to obtain M detail links, wherein each associated resource detail data contains a corresponding detail link, and M is an integer greater than or equal to 1;
traversing the target associated resource list interface and calling M detail links.
In another specific embodiment of the present application, after determining that the target link is the associated resource list interface, the detail links in the associated resource detail data may be obtained by parsing M associated resource detail data associated with the list link. This is because the list links correspond to associated resource list interfaces, which are made up of a plurality of associated resource detail interfaces, or an associated resource detail interface and its associated data information make up an associated resource detail data. And each associated resource detail interface corresponds to one detail link, so that M detail links can be obtained by analyzing M associated resource detail data. And then traversing the target associated resource list interface, and under the condition that the traversing is completed, determining that the non-invoked interfaces exist, and calling each non-invoked detail link to complete the calling of all interfaces in the associated resource interface relation.
In addition, if the results of calling each interface are true, the resource detail link and the related resource link are successfully called, the true can be directly returned without going through the detail link in the related resource detail data, otherwise, the next detail link is required to be continuously called.
The test for realizing the interface in the embodiment of the application can be realized in a mode of timing test or active test. The timing test can be implemented by setting a timing task, and by periodically executing the above embodiment, the test of the interface to be tested is automatically executed, and the obtained interface test result can be saved in the log file of the test service. In addition, the setting of the timing task can be realized through an annotation (@ Scheduled) provided by an open-source application (spring-boot) framework on an object-oriented programming language (Java) platform, and the timing period can be flexibly configured. In addition, the active test can be realized through an interface for actively triggering the test provided by the test service, the test flow can be started for trial, and the test result can be directly obtained through the return of the response result. In this way, the embodiment of the application can be realized by a timing test or an active test mode, and the interface test can be periodically executed by timing test configuration, or the test interface can be actively called to trigger a single full-quantity interface test.
Referring to fig. 3, the interface testing method in the present application may specifically further include the following steps:
step 201, obtaining interface path data associated with a service to be tested, wherein the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relation between each associated resource detail interface and each associated resource list interface in the interface path data;
step 202, calling a root link in the associated resource interface relationship to obtain a response result;
step 203, judging whether the root link is called;
step 204, in case the root link has been called, returning a first result, where the first result is used to indicate ending the call to the root link
Step 205, sending a call request to the service to be tested under the condition that the root link is not called;
step 206, receiving the response result of the service to be tested to the call request
Step 207, obtaining the target link based on the response result
Step 208, judging whether the target link is empty;
step 209, determining that the target link is a target associated resource list interface when the target link is empty, and analyzing M associated resource detail data associated with the list link contained in the target associated resource list interface to obtain M detail links;
Step 210, traversing the target associated resource list interface;
step 211, judging whether traversing the associated resource list interface is completed or not;
step 212, recursively calling M detail links under the condition of traversing the associated resource list interface;
step 213, based on the result returned by the calling detail link, judging whether the calling result has errors;
step 214, determining that the target link is a target associated resource detail interface under the condition that the target link is not empty;
step 215, traversing each associated resource detail interface associated with the list link contained in the target associated resource detail interface;
step 216, judging whether traversing each associated resource detail interface is completed or not;
step 217, calling the detail links corresponding to each associated resource detail interface;
step 218, judging whether the calling result has errors or not, and displaying an unrecalled interface or not;
step 219, if the call result is wrong, the interface test of the service to be tested is finished, and the call result returns true;
and 220, ending the interface test of the service to be tested under the condition that the calling result is correct, and returning an error (flag) to the calling result.
It should be noted that after the interface testing process of the service to be tested is finished, all interface paths of the service to be tested and the interface paths which are already called can be compared, the interface paths which are not already called are found out and written into the log file of the testing service, so that the interface testing process is convenient to use as reference data in the next test, and the automation level of the interface testing process is improved.
It should be noted that, the interface testing method provided in the embodiment of the present application may implement each process implemented by the embodiment of the method, and may achieve the same beneficial effects, and a specific implementation manner of the interface testing method may refer to the related description of the embodiment shown in fig. 1, so that the description is not repeated.
The embodiment of the application further provides an interface testing device, as shown in fig. 4, the interface testing device 300 specifically includes:
an obtaining module 301, configured to obtain interface path data associated with a service to be tested, where the interface path data includes an associated resource detail interface, an associated resource list interface, and an associated resource interface relationship, where the associated resource interface relationship is an association relationship between each associated resource detail interface and each associated resource list interface in the interface path data;
the result module 302 is configured to invoke a root link in the association resource interface relationship to obtain a response result;
and a calling module 303, configured to sequentially call the associated resource detail interface and the associated resource list interface related to the root link in the associated resource interface relationship based on the response result, so as to execute an interface test on the service to be tested.
Optionally, the acquiring module 301 includes:
the first acquisition sub-module is used for acquiring all interface paths associated with the Internet application Web service based on the open source data packet;
the first sending sub-module is used for caching all the interface paths and acquiring all the mapping relations in all the interface paths;
a first determining submodule, configured to determine, based on the interface request method and the class name corresponding to the interface in one target mapping relationship, whether the interface path corresponding to the target mapping relationship is an interface path associated with the service to be tested, where the target mapping relationship is any one of the all mapping relationships, and one target mapping relationship includes an interface path of the Web service, an interface request method, and a class name corresponding to an interface;
the second obtaining sub-module is used for obtaining the interface path associated with the service to be tested under the condition that the interface path corresponding to the target mapping relation is the interface path associated with the service to be tested;
and the third acquisition sub-module is used for acquiring interface path data associated with the service to be tested based on the target mapping relation.
Optionally, the calling module 303 includes:
the first calling sub-module is used for calling the root link;
the second calling sub-module is used for calling a query interface to acquire the interface path data cached by a refreshing interface when the interface path data of the service to be tested is newly added or modified, wherein the query interface is connected with the refreshing interface, and the refreshing interface is an interface used for caching the newly added or modified interface path data of the service to be tested in the service to be tested;
and the third calling sub-module is used for sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation so as to acquire an interface test result of the service to be tested.
Optionally, the result module 302 includes:
a first judging sub-module, configured to judge whether the root link is called;
the second sending submodule is used for sending a calling request to the service to be tested under the condition that the root link is not called, wherein the calling request is constructed based on the root link;
and the fourth calling sub-module is used for calling the root link based on the calling request and obtaining the response result of the root link.
Optionally, after the determining whether the root link is invoked, the interface testing device 300 further includes:
and the return module is used for returning a first result when the root link is called, wherein the first result is used for indicating ending the call to the root link.
Optionally, the fourth calling sub-module includes:
the first receiving unit is used for receiving a response result of the service to be tested to the call request of the root link;
and the acquisition unit is used for acquiring a target link based on the response result, wherein the target link is associated with one associated resource list interface in the associated resource interface relation, or the target link is associated with one associated resource detail interface.
Optionally, the calling module 303 includes:
the second judging submodule is used for judging whether the target link is empty or not;
the second determining submodule is used for determining that the target link is a target associated resource detail interface and calling one list link contained in the target associated resource detail interface under the condition that the target link is not empty, wherein the associated resource interface relation comprises the target associated resource detail interface;
And the third determining submodule is used for determining that the target link is a target associated resource list interface under the condition that the target link is empty, and sequentially calling each detail link contained in the target associated resource list interface, wherein the associated resource interface relation comprises the target associated resource list interface.
Optionally, the second determining submodule includes:
the first traversing unit is used for traversing each associated resource detail interface associated with the list link contained in the target associated resource detail interface, wherein one list link corresponds to one associated resource list interface, one associated resource list interface is associated with N associated resource detail interfaces, and N is an integer greater than or equal to 1;
and the calling unit is used for calling the detail links corresponding to each associated resource detail interface under the condition that each associated resource detail interface is traversed, wherein one associated resource detail interface corresponds to one detail link.
Optionally, the third determining submodule includes:
the analyzing unit is used for analyzing M associated resource detail data associated with the list links contained in the target associated resource list interface to obtain M detail links, wherein each associated resource detail data contains a corresponding detail link, and M is an integer greater than or equal to 1;
And the second traversing unit is used for traversing the target associated resource list interface and calling M detail links.
It should be noted that, the interface testing apparatus 300 provided in the embodiment of the present application may implement each process implemented by the embodiment of the method described in fig. 1 or fig. 3, and may achieve the same beneficial effects, and a specific implementation manner of the interface testing apparatus may refer to the related description of the embodiment shown in fig. 1 or fig. 3, so that the description is not repeated in this embodiment.
Referring to fig. 5, fig. 5 is a block diagram of an electronic device according to an embodiment of the present application, as shown in fig. 5, including: a processor 400, a memory 420 and a program or instructions stored on the memory 420 and executable on the processor 400, the processor 400 for reading the program or instructions in the memory 420; the electronic device also includes a bus interface and transceiver 410.
A transceiver 410 for receiving and transmitting data under the control of the processor 400.
Wherein in fig. 5, a bus architecture may comprise any number of interconnected buses and bridges, and in particular, one or more processors represented by processor 400 and various circuits of memory represented by memory 420, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 410 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 400 in performing operations.
The processor 400 is configured to read a program or an instruction in the memory 420, and perform the following steps:
acquiring interface path data associated with a service to be tested, wherein the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between the associated resource detail interfaces and the associated resource list interfaces in the interface path data;
invoking a root link in the associated resource interface relationship to obtain a response result;
and based on the response result, sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation to execute the interface test of the service to be tested.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
acquiring all interface paths associated with the Internet application Web service based on the open source data packet;
caching all interface paths and acquiring all mapping relations in all interface paths;
determining whether the interface path corresponding to the target mapping relation is an interface path associated with the service to be tested based on the interface request method and the class name corresponding to the interface in one target mapping relation, wherein the target mapping relation is any one of the all mapping relations, and one target mapping relation comprises the interface path, the interface request method and the class name corresponding to the interface of the Web service;
Obtaining the interface path associated with the service to be tested under the condition that the interface path corresponding to the target mapping relation is the interface path associated with the service to be tested;
and acquiring interface path data associated with the service to be tested based on the target mapping relation.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
invoking the root link;
under the condition that the interface path data of the service to be tested is newly added or modified, a query interface is called to obtain interface path data of a refreshing interface cache, wherein the query interface is connected with the refreshing interface, and the refreshing interface is an interface for caching the newly added or modified interface path data of the service to be tested in the service to be tested;
updating the associated resource interface relation based on the interface path data of the refreshing interface cache acquired by the query interface;
and sequentially calling the related resource detail interface and the related resource list interface which are related to the root link in the updated related resource interface relationship so as to execute the interface test of the service to be tested.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
judging whether the root link is called or not;
sending a call request to the service to be tested under the condition that the root link is not called, wherein the call request is constructed based on the root link;
and calling the root link based on the calling request, and acquiring the response result of the root link.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
and returning a first result under the condition that the root link is called, wherein the first result is used for indicating ending the call to the root link.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
receiving a response result of the service to be tested to the call request of the root link;
and acquiring a target link based on the response result, wherein the target link is associated with one associated resource list interface in the associated resource interface relation, or the target link is associated with one associated resource detail interface.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
judging whether the target link is empty or not;
under the condition that the target link is not empty, determining that the target link is a target associated resource detail interface, and calling a list link contained in the target associated resource detail interface, wherein the associated resource interface relation comprises the target associated resource detail interface;
and under the condition that the target link is empty, determining that the target link is a target associated resource list interface, and sequentially calling each detail link contained in the target associated resource list interface, wherein the associated resource interface relation comprises the target associated resource list interface.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
traversing each associated resource detail interface associated with the list link contained in the target associated resource detail interface, wherein one list link corresponds to one associated resource list interface, one associated resource list interface associates N associated resource detail interfaces, and N is an integer greater than or equal to 1;
And under the condition that each associated resource detail interface is traversed, calling the detail link corresponding to each associated resource detail interface, wherein one associated resource detail interface corresponds to one detail link.
Optionally, the processor 400 is configured to read the program or the instruction in the memory 420, and perform the following steps:
analyzing M associated resource detail data associated with the list links contained in the target associated resource list interface to obtain M detail links, wherein each associated resource detail data contains a corresponding detail link, and M is an integer greater than or equal to 1;
traversing the target associated resource list interface and calling M detail links.
The electronic device in the embodiment of the present application may implement an interface testing method as described in fig. 1 when running, and may implement the same technical effects, and achieve the same beneficial effects, and may specifically refer to the description in the above embodiment, so that repetition is avoided and no further description is provided herein.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the processes of the embodiment of the interface testing method described in fig. 1 are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is provided herein.
Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, to implement each process of the embodiment of the interface testing method described in fig. 1, and to achieve the same technical effect, so that repetition is avoided, and details are not repeated here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.
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 apparatus 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 apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.
Claims (12)
1. An interface testing method, the method comprising:
acquiring interface path data associated with a service to be tested, wherein the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between the associated resource detail interfaces and the associated resource list interfaces in the interface path data;
invoking a root link in the associated resource interface relationship to obtain a response result;
and based on the response result, sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation so as to execute the interface test of the service to be tested.
2. The method of claim 1, wherein the obtaining interface path data associated with the service under test comprises:
acquiring all interface paths associated with the Internet application Web service based on the open source data packet;
caching all interface paths and acquiring all mapping relations in all interface paths;
determining whether the interface path corresponding to the target mapping relation is an interface path associated with the service to be tested based on the interface request method and the class name corresponding to the interface in one target mapping relation, wherein the target mapping relation is any one of the all mapping relations, and one target mapping relation comprises the interface path, the interface request method and the class name corresponding to the interface of the Web service;
Obtaining the interface path associated with the service to be tested under the condition that the interface path corresponding to the target mapping relation is the interface path associated with the service to be tested;
and acquiring interface path data associated with the service to be tested based on the target mapping relation.
3. The method according to claim 1, wherein said sequentially invoking the associated resource detail interface and the associated resource list interface in the associated resource interface relationship related to the root link to perform an interface test for the service under test comprises:
under the condition that the interface path data of the service to be tested is newly added or modified, a query interface is called to obtain interface path data of a refreshing interface cache, wherein the query interface is connected with the refreshing interface, and the refreshing interface is an interface for caching the newly added or modified interface path data of the service to be tested in the service to be tested;
updating the associated resource interface relation based on the interface path data of the refreshing interface cache acquired by the query interface;
and sequentially calling the related resource detail interface and the related resource list interface which are related to the root link in the updated related resource interface relationship so as to execute the interface test of the service to be tested.
4. The method of claim 1, wherein invoking the root link to obtain the response result comprises:
judging whether the root link is called or not;
sending a call request to the service to be tested under the condition that the root link is not called, wherein the call request is constructed based on the root link;
and calling the root link based on the calling request, and acquiring the response result of the root link.
5. The method of claim 4, wherein after said determining if the root link has been invoked, the method further comprises:
and returning a first result under the condition that the root link is called, wherein the first result is used for indicating ending the call to the root link.
6. The method of claim 4, wherein the obtaining the response result for the root link comprises:
receiving a response result of the service to be tested to the call request of the root link;
and acquiring a target link based on the response result, wherein the target link is associated with one associated resource list interface in the associated resource interface relation, or the target link is associated with one associated resource detail interface.
7. The method of claim 6, wherein the sequentially invoking the associated resource detail interface and the associated resource list interface in the associated resource interface relationship comprises:
judging whether the target link is empty or not;
under the condition that the target link is not empty, determining that the target link is a target associated resource detail interface, and calling a list link contained in the target associated resource detail interface, wherein the associated resource interface relation comprises the target associated resource detail interface;
and under the condition that the target link is empty, determining that the target link is a target associated resource list interface, and sequentially calling each detail link contained in the target associated resource list interface, wherein the associated resource interface relation comprises the target associated resource list interface.
8. The method of claim 7, wherein said invoking a list link contained in said target associated resource detail interface comprises:
traversing each associated resource detail interface associated with the list link contained in the target associated resource detail interface, wherein one list link corresponds to one associated resource list interface, one associated resource list interface associates N associated resource detail interfaces, and N is an integer greater than or equal to 1;
And under the condition that each associated resource detail interface is traversed, calling the detail link corresponding to each associated resource detail interface, wherein one associated resource detail interface corresponds to one detail link.
9. The method of claim 7, wherein the sequentially invoking each detail link contained in the target associated resource list interface comprises:
analyzing M associated resource detail data associated with the list links contained in the target associated resource list interface to obtain M detail links, wherein each associated resource detail data contains a corresponding detail link, and M is an integer greater than or equal to 1;
traversing the target associated resource list interface and calling M detail links.
10. An interface testing apparatus, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring interface path data associated with a service to be detected, the interface path data comprises associated resource detail interfaces, associated resource list interfaces and associated resource interface relations, and the associated resource interface relations are the associated relations between each associated resource detail interface and each associated resource list interface in the interface path data;
The result module is used for calling the root links in the associated resource interface relationship to acquire a response result;
and the calling module is used for sequentially calling the associated resource detail interface and the associated resource list interface which are related to the root link in the associated resource interface relation based on the response result so as to execute the interface test of the service to be tested.
11. An electronic device, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the interface testing method of any of claims 1 to 9.
12. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the interface testing method of any of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311543520.2A CN117459416A (en) | 2023-11-20 | 2023-11-20 | Interface testing method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311543520.2A CN117459416A (en) | 2023-11-20 | 2023-11-20 | Interface testing method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117459416A true CN117459416A (en) | 2024-01-26 |
Family
ID=89596690
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311543520.2A Pending CN117459416A (en) | 2023-11-20 | 2023-11-20 | Interface testing method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117459416A (en) |
-
2023
- 2023-11-20 CN CN202311543520.2A patent/CN117459416A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108628661B (en) | Automatic establishment method of cloud manufacturing service and cloud manufacturing system | |
| US7657591B2 (en) | Dispatching client requests to appropriate server-side methods | |
| US10452522B1 (en) | Synthetic data generation from a service description language model | |
| US20110246635A1 (en) | Simplifying determination of dependencies among soa services | |
| CN110399107B (en) | Log printing method, device, storage medium and equipment | |
| CN113572651B (en) | Cloud platform resource management method and system based on multi-protocol equipment management architecture | |
| CN111309593A (en) | JSON interface verification method, device and equipment and computer readable storage medium | |
| US11665247B2 (en) | Resource discovery agent computing device, software application, and method | |
| CA3017523C (en) | Technologies for auto discover and connect to a rest interface | |
| CN113360519A (en) | Data processing method, device, equipment and storage medium | |
| CN110716912B (en) | SQL performance detection method and server | |
| CN111752820B (en) | gRPC interface pressure test method, computer equipment and storage medium | |
| CN111367685A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN117041111A (en) | Vehicle cloud function test method and device, electronic equipment and storage medium | |
| CN117459416A (en) | Interface testing method and device, electronic equipment and readable storage medium | |
| CN113836212B (en) | Method for automatically generating Json data by database data, readable medium and electronic equipment | |
| CN114860480A (en) | Web service proxy method, device and storage medium based on Serverless | |
| CN112702441A (en) | Container-based access data processing method, device and system and storage medium | |
| Mengistu | Distributed Microservice Tracing Systems: Open-source tracing implementation for distributed Microservices build in Spring framework | |
| CN117632445B (en) | Request processing method and device, task execution method and device | |
| US20240028346A1 (en) | Linking kubernetes resources with underlying cloud infrastructure | |
| CN117851210A (en) | Pressure performance testing method, server, system, electronic equipment and storage medium | |
| US8230001B2 (en) | Providing information about a system using scripts | |
| CN116233123A (en) | Information processing method and device, processor and electronic equipment | |
| CN117725892A (en) | Parameter configuration file format conversion method, device, equipment and storage medium |
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 |