CN111694561A - Interface management method, device, equipment and storage medium - Google Patents

Abstract

The embodiments of the present invention disclose an interface management method, apparatus, device and storage medium. The method includes: when an interface definition instruction input by a user is received, displaying an interface definition interactive interface; collecting interface definition information based on the interface definition interactive interface, and generating an interface document based on the interface definition information; receiving externally input request information , and generate test data corresponding to the request information according to the request information and the interface document. The embodiment of the present invention solves the problem of low front-end and back-end collaboration efficiency by setting the interface definition interactive interface to collect interface definition information and generate interface documents, so that front-end technicians and back-end technicians can carry out development work at the same time, which not only satisfies the requirements of front-end technicians The demand for test data can also prevent back-end technicians from repeatedly revising the interface code in the later stage.

Description

An interface management method, apparatus, device and storage medium

technical field

Embodiments of the present invention relate to the technical field of application development, and in particular, to an interface management method, apparatus, device, and storage medium.

Background technique

In the development process of application products, back-end technicians are responsible for logic and provide data to front-end technicians, and front-end technicians are responsible for receiving back-end data for display and interaction. The front-end and back-end separation development mode allows technicians to focus on improving development efficiency in their respective fields. However, there are also some problems in this collaboration method. For example, due to the lack of technical communication between the front-end technicians and the back-end technicians, the front-end technicians can only perform joint debugging according to the interface documents provided by the back-end technicians. The test data determines whether the interface meets the front-end requirements. If the requirements are not met, back-end technicians are required to rework. This serial working mode will prolong the time of product development, reduce the efficiency of product development, and increase the workload of front-end and back-end technicians.

The existing technology mainly generates interface documents by analyzing the code data written by the back-end technicians, but this technical means also needs to wait for the back-end technicians to finish writing the code before it can be realized. And due to the lack of participation of front-end technicians, there will also be the problem of repeatedly modifying the interface. And the existing interface management tools, such as Swagger, do not have the function of dynamically generating test data, so it cannot meet the requirements of the front-end development process for test data.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide an interface management method, apparatus, device, and storage medium, so as to improve front-end and back-end collaboration efficiency, and dynamically generate test data required by front-end technicians.

In a first aspect, an embodiment of the present invention provides an interface management method, which includes:

When receiving the interface definition instruction input by the user, display the interface definition interactive interface;

Collect interface definition information based on the interface definition interactive interface, and generate an interface document based on the interface definition information;

Receive externally input request information, and generate test data corresponding to the request information according to the request information and the interface document.

In a second aspect, an embodiment of the present invention further provides an interface management apparatus, the apparatus includes:

an interface definition module, configured to display an interface definition interactive interface when receiving an interface definition instruction input by a user, collect interface definition information input by the user based on the interface definition interactive interface, and generate an interface document based on the interface definition information;

The information transmission module is used to receive the request information input by the user;

A response simulation module, configured to generate test data corresponding to the request information according to the request information and the interface document.

In a third aspect, an embodiment of the present invention further provides a device, and the device includes:

one or more processors;

memory for storing one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement any one of the above-mentioned interface management methods.

In a fourth aspect, an embodiment of the present invention further provides a storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute any one of the above-mentioned interface management methods when executed by a computer processor .

In the embodiment of the present invention, the interface definition information is collected by setting the interface definition interactive interface, and the interface document is generated, which solves the problem of low front-end and back-end collaboration efficiency, enables the front-end technical personnel and the back-end technical personnel to carry out development work at the same time, which not only satisfies the requirements of the front-end technical personnel The demand for test data can also prevent back-end technicians from repeatedly revising the interface code in the later stage.

Description of drawings

FIG. 1 is a flowchart of an interface management method according to Embodiment 1 of the present invention.

FIG. 2A is a schematic diagram of a Headers parameter collection module in an interface definition interactive interface provided by Embodiment 1 of the present invention.

FIG. 2B is a schematic diagram of a Query parameter collection module in an interface definition interactive interface provided by Embodiment 1 of the present invention.

FIG. 2C is a schematic diagram of a body parameter collection module in an interface definition interactive interface provided by Embodiment 1 of the present invention.

FIG. 3A is a schematic diagram of an interface definition interactive interface according to Embodiment 1 of the present invention.

FIG. 3B is a schematic diagram of interface definition information according to Embodiment 1 of the present invention.

FIG. 4 is a flowchart of an interface management method according to Embodiment 2 of the present invention.

FIG. 5 is a flowchart of a method for responding to test data according to Embodiment 2 of the present invention.

FIG. 6 is a flowchart of importing and exporting an interface document according to Embodiment 2 of the present invention.

FIG. 7 is a schematic diagram of an interface management apparatus according to Embodiment 3 of the present invention.

FIG. 8 is a schematic structural diagram of a device according to Embodiment 4 of the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention. In addition, it should be noted that, for the convenience of description, the drawings only show some but not all structures related to the present invention.

Example 1

FIG. 1 is a flowchart of an interface management method provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of product development based on front-end and back-end models. The method can be executed by an interface management device, and the device can use software and/or hardware, the apparatus may be configured in a terminal device. Specifically include the following steps:

S110. When an interface definition instruction input by a user is received, display an interface definition interactive interface.

In one embodiment, optionally, the way in which the user inputs the interface definition instruction includes at least one input way among shortcut keys, page options, and codes. Wherein, exemplarily, when the user inputs an interface definition instruction through a shortcut key, a corresponding relationship between the interface definition instruction and the shortcut key is established, exemplarily, the shortcut key may be "shift+T". The specific definition of the shortcut key is not limited here, and the user can customize it. For example, when the user inputs the interface definition instruction through the page option, specifically, the user can input the interface definition instruction by clicking the page option corresponding to the interface definition function on the display interface of the terminal device. Can be an icon. Wherein, exemplarily, when the user inputs the interface definition instruction through the code, a corresponding relationship between the interface definition instruction and the code is established, and the user can input the interface definition instruction by writing the code. Specifically, the user can input the code corresponding to the interface definition instruction in the "run" program of the terminal device.

The interface definition instruction is used to trigger the display of the interface definition interactive interface. The interface definition interactive interface may allow the user to collect interface definition information input by the user.

S120. Collect interface definition information based on the interface definition interactive interface, and generate an interface document based on the interface definition information.

Exemplarily, the user inputs the interface definition information in the interface definition interactive interface based on the content displayed on the interface definition interactive interface and related operation methods.

In an embodiment, optionally, the interface definition information includes basic information, request parameter information, and response data information.

In an embodiment, optionally, the basic information includes interface name, interface method, and interface path information. Among them, for example, the interface name is used to distinguish interfaces with different functions, and the user can customize the settings. In practical applications, front-end technicians and back-end technicians negotiate to determine the required interface functions and the naming method of each functional interface. Wherein, by way of example, the interface method includes a method supported by an HTTP request (HyperText Transport Protocol, hypertext transport protocol). Exemplarily, the interface methods include but are not limited to methods such as GET, POST, PUT, DELETE, HEAD, OPTIONS, PATCH, and TRACE. Among them, GET is used to obtain the specified resource and return the request body; POST is used to submit data to the specified resource for request processing, such as uploading a file; PUT is used to upload the latest content to the specified resource; DELETE is used to delete the specified resource; HEAD is used to Get the specified resource without returning the request body; OPTIONS is used to return the HTTP request method provided by the server for the specified resource; PATCH is used to update part of the content of the specified resource, such as updating a field; TRACE echoes the request received by the server , mainly used for testing or diagnosis. Wherein, the interface path exemplarily includes an interface URI (UniformResource Identifier, uniform resource identifier), and exemplarily, the interface path supports the Restful style, such as /api/users/:id.

In an embodiment, optionally, the request parameter information includes Headers parameter information, Query parameter information, and Body parameter information. The HTTP request message includes a request line, a request body, a blank line and request data. Among them, the request header consists of keyword/value pairs, and the keyword and value are separated by ":". The request header is used to inform the server about the client's request information. The Headers parameter includes the request headers in the HTTP request message. Specifically, the Headers parameter information includes information such as parameter names, parameter values, examples, and remarks, where an example of the Headers parameter information may be Content-Type: application/json. FIG. 2A is a schematic diagram of a Headers parameter collection module in an interface definition interactive interface provided by Embodiment 1 of the present invention. As shown in FIG. 2A , the header parameter collection interface includes an “Add Header” option, and the user can generate a new Headers parameter collection unit by clicking this option. FIG. 2A shows three Headers parameter collection units, and each Headers parameter collection unit includes a parameter name text box, a parameter value text box, and a remark information text box. The user can also click the trash can icon behind the Headers parameter collection unit to delete the corresponding Headers parameter collection unit.

The Query parameter information is a parameter in the URL (Uniform Resource Locator, Uniform Resource Locator) in the HTTP request message, which is located after "?". Query parameters consist of keyword/value pairs, and multiple Query parameters are connected by "&". Specifically, the Query parameter information includes information such as the parameter name, whether it is required, an example, and a remark, where an example of the Query parameter information can be http://example.com/? a=xxx&b=yyy, where a and b represent Query parameters, and xxx and yyy are the values of a and b, respectively. FIG. 2B is a schematic diagram of a Query parameter collection module in an interface definition interactive interface provided by Embodiment 1 of the present invention. As shown in FIG. 2B , the Query parameter collection interface includes an “Add Query parameter” option, and the user can generate a new Query parameter collection unit by clicking this option. FIG. 2B shows three Query parameter collection units, and each Query parameter collection unit includes a parameter name text box, a parameter value text box, and a remark information text box. The "box" in each Query parameter collection unit indicates "required or not". After the user clicks the box, a "√" will be generated in the box. Users can also click the "trash can" icon behind the Query parameter collection unit to delete the corresponding Query parameter collection unit.

The Body parameter includes the request body in the HTTP request message, and supports JSON format. In an embodiment, optionally, a JSON property editor is used to collect Body parameter information. Specifically, the Body parameter information includes information such as attribute name, whether it is required, attribute type, simulation rules, and remarks. FIG. 2C is a schematic diagram of a body parameter collection module in an interface definition interactive interface provided by Embodiment 1 of the present invention. As shown in Fig. 2C, "root" indicates the attribute name, "box" indicates "required", "object" indicates "attribute type", and "mock" indicates "mock rule". The user can click the "+" icon behind the Body parameter acquisition unit to add a new sub-Body parameter corresponding to the Body parameter under the Body parameter, as shown in Figure 2C, "field_1", "field_2" and "field_3" is the sub-Body parameter of "root", and "field_4" is the sub-Body parameter of "field_1". Used to delete the corresponding Body parameter collection unit by clicking the "X" icon behind the Body parameter collection unit.

In one embodiment, optionally, the response data information includes data in JSON format. Wherein, exemplarily, the response data information is used to define constraints and rules for generating test data. Interface Definition The schematic diagram of the response data information acquisition module in the interactive interface is similar to FIG. 4 , and the description is not repeated here.

FIG. 3A is a schematic diagram of an interface definition interactive interface according to Embodiment 1 of the present invention. The interface definition interactive interface shown in Figure 3 includes a basic information collection module, a request parameter collection module and a response data collection module. Among them, the two text boxes after "Interface Path" are the interface method text box and the interface path text box respectively. After editing the definition information of the current interface, the user clicks the "Save" button in the interface to save the interface definition information. Interface Definition The interactive interface also includes an interface list, which is used to display all the collected interfaces. Specifically, the interfaces can be classified, and corresponding interfaces are displayed in different classified lists. Exemplarily, the classified lists include test interfaces.

In one embodiment, optionally, the interface definition information further includes interface status, interface creator and interface update time. The interface state is used to represent the definition state of the current interface. Exemplarily, the interface state may be incomplete, completed, updating, and so on. The interface creator includes the user who created the current interface. Specifically, before displaying the interface definition interaction interface, an account input prompt box is displayed, and when the input account is the same as the saved account, the interface definition interaction interface is displayed, allowing the use of the account for inputting interface definition information. The interface update time is used to record the edited time of the current interface. Specifically, the interface update time is recorded when a save instruction is received.

FIG. 3B is a schematic diagram of interface definition information according to Embodiment 1 of the present invention. The interface definition information of the interface shown in FIG. 3B includes basic information, request parameter information, response data information, remarks and modification records. Among them, the basic information includes name, creator, status, update time, method and path. The request parameter information includes Headers parameter information, Query parameter information, and Body parameter information. Each header parameter collection unit in the Header list includes parameter name, parameter value, example and remarks, and each Query parameter collection unit in the Query list includes parameter name, whether it is required, example and remarks, in the Body list Each Body parameter collection unit of , includes attribute name, whether it is required, attribute type, simulation rules and remarks, wherein, the attribute type includes text type and file type. The text type means that the parameter contains keyword/value pairs, and the file type means that the parameter contains a file. The data type of the response data information is mainly in JSON format. Each collection unit in the parameter list includes the attribute name, whether it is required, attribute type, simulation rules and remarks. The attribute type includes string, number, array, object, boolean and Integer, the above attribute types represent string data type, numeric data type, array data type, reference type, Boolean type and integer data type respectively.

S130: Receive externally input request information, and generate test data corresponding to the request information according to the request information and the interface document.

Wherein, exemplarily, the type of request information includes HTTP request information. Specifically, the test data corresponding to the request information is generated according to the request parameter data in the request information and the response data information defined in the interface document.

In the technical solution of this embodiment, the interface definition information is collected by setting the interface definition interactive interface, and the interface document is generated, which solves the problem of low front-end and back-end collaboration efficiency, and enables front-end technicians and back-end technicians to carry out development work at the same time, which not only satisfies The requirements of front-end technicians for test data can also avoid the need for back-end technicians to revise the interface code repeatedly in the later period.

Embodiment 2

FIG. 4 is a flowchart of an interface management method according to Embodiment 2 of the present invention. The technical solution of this embodiment is a further refinement on the basis of the foregoing embodiment. Optionally, generating the test data corresponding to the request information according to the request information and the interface document includes: matching the request information with the request parameter information in the interface document to obtain the target request. parameter information and response data information corresponding to the target request parameter information; generate test data corresponding to the request information according to the target request parameter information and the response data information.

The specific implementation steps of this embodiment include:

S210. When receiving the interface definition instruction input by the user, display the interface definition interactive interface.

S220. Collect interface definition information based on the interface definition interactive interface, and generate an interface document based on the interface definition information.

S230: Receive externally input request information, match the request information with the request parameter information in the interface document, and obtain target request parameter information and response data information corresponding to the target request parameter information.

Wherein, exemplarily, the type of request information includes HTTP request information. Specifically, the basic information in the request information is matched with the basic information in the interface document. Exemplarily, the basic information includes information such as interface name, interface method, and interface path. After successful matching, the corresponding request information can be obtained. Define the interface, define the target request parameter information corresponding to the interface, and the response data information corresponding to the target request parameter.

S240. Generate test data corresponding to the request information according to the target request parameter information and the response data information.

In an embodiment, optionally, the request information is verified according to the target request parameter information; if the verification is successful, test data corresponding to the request information is generated according to the response data information. Wherein, exemplarily, the parameter type in the request information is verified according to the parameter type in the target request parameter information, if the parameter type in the request information is different from the parameter type in the target request parameter information, the verification fails, if If they are the same, the verification is successful. Wherein, generating the test data corresponding to the request information according to the response data information includes: generating the test data according to the simulation rules in the response data information and the request parameter data in the request information. Among them, the simulation rule is used to identify the generation rule of the test data. In one embodiment, the simulation rule includes defining the data type of the test data, such as @integer for integer data and @string for string data. In one embodiment, the simulation rule includes defining the data type and data length of the test data. For example, @integer(1-10) represents integer data with a value of 1-10, and @string(1-10) represents a value of 1- 10 string data. In one embodiment, the simulation rules include regular expression rules, such as @regex:^[a-zA-Z0-9]+$, where "^" indicates matching the beginning of the input word line, "[a-zA-Z0 -9]" means 26 uppercase letters, 26 lowercase letters and numbers from 0 to 9, and "$" means match the end of the input line.

In one embodiment, optionally, the verification result and the generated test data are returned to the user; wherein the verification result includes a verification failure identifier and remark information corresponding to the verification failure identifier. The verification failure identifier is used to represent different verification failure reasons, and the remark information is used to describe the verification failure reasons. Exemplarily, if the parameter type in the request information of the request parameter is different from the parameter type in the target request parameter information, the verification failure is marked as A, and the remark information is that the parameter type does not meet the requirements. If the required parameter is missing in the request information of the request parameter, the verification failure is marked as B, and the remark information is that the required parameter is missing. The verification failure identification and remark information are not specifically limited here, and the user can customize the settings.

FIG. 5 is a flowchart of a method for responding to test data according to Embodiment 2 of the present invention. The dotted line in FIG. 5 represents the server side, the request information is input to the server side through the client side, and the server side returns the generated response to the client side. The same gateway is used for the reception entry and the response entry of the request information shown in FIG. 5 , and the gateway receives the request information input by the client and the response data input by the server. When the gateway receives the request information, it matches the basic information of the request information with the basic information of the interface in the interface document, and determines the matching defined interface, the target request parameter information of the defined interface, and the response data information corresponding to the target request parameter information. The request information is verified based on the target request parameter information, and the verification response data is sent to the response portal gateway. If the verification is successful, test data is generated based on the response data information and the parameter data in the request information and sent to the response portal gateway. The response entry gateway returns the received verification response data and test data to the client.

On the basis of the above embodiment, optionally, the interface document to be migrated input by the user is received, and the interface definition information in the interface to be migrated document is parsed to obtain the interface definition information that meets the preset format requirements. The interface documents to be migrated include interface documents generated by other interface management platforms. Exemplarily, the other interface management platforms may be the swagger platform, and the data format of the interface documents to be migrated may be JSON format. Interface definition information in interface documents generated by different interface management platforms is defined in different ways. Exemplarily, in this embodiment, "name" is used to represent the parameter name, and other interface management platforms use "" to represent the parameter name. Specifically, parsing the interface definition information in the interface document to be migrated includes: converting the interface definition information in the interface document to be migrated into target interface definition information according to preset format requirements. Exemplarily, replace "definition" in the interface definition information in the migration interface document with "name".

The advantage of this setting is that the swagger platform can generate interface documents, but does not have the function of dynamically generating test data. On the one hand, this embodiment simplifies the steps for technicians to re-enter interface definition information, and on the other hand, improves the compatibility of interface management. in order to better meet the needs of users.

On the basis of the above embodiment, optionally, a target export template and export interface definition information are obtained, and the export interface definition information is filled in the target export template to generate an export interface document. The target export template includes the interface to be exported and the logical relationship between the interfaces. Specifically, the user can edit the default export template to generate the target export template, and obtain the export interface definition information corresponding to the export interface based on the export interface in the target export template.

The advantage of this setting is that different user needs correspond to different interface documents. If only the default interface document can be exported, it cannot meet different user needs. In this embodiment, by setting an export template, the step of repeatedly modifying the exported interface document is avoided, the workload of exporting the interface document is reduced, and the work efficiency is improved.

FIG. 6 is a flowchart of importing and exporting an interface document according to Embodiment 2 of the present invention. Receive the to-be-migrated interface document provided in JSON format or the swagger interface, and parse the to-be-migrated interface document through the import module to obtain the interface definition information that meets the preset format requirements. Through the export template defined in the export module, the interface definition information corresponding to the export template is filled in the export template, and the interface document is generated and exported.

The technical solution of this embodiment solves the problem of low test work efficiency by matching and verifying the request information based on the target request parameter information, and the technician can correct the input request information in time according to the output verification result, thereby improving the efficiency of the test. Test the efficiency of work.

Embodiment 3

FIG. 7 is a schematic diagram of an interface management apparatus according to Embodiment 3 of the present invention. This embodiment is applicable to the case of product development based on the front-end and back-end mode, the apparatus may be implemented in software and/or hardware, and the apparatus may be configured in a terminal device. The interface management apparatus includes: an interface definition module 310 , an information transmission module 320 and a response simulation module 330 .

Wherein, the interface definition module 310 is configured to display the interface definition interactive interface when receiving the interface definition instruction input by the user, collect the interface definition information input by the user based on the interface definition interactive interface, and generate an interface document based on the interface definition information;

an information transmission module 320, configured to receive request information input by a user;

The response simulation module 330 is configured to generate test data corresponding to the request information according to the request information and the interface document.

In the technical solution of this embodiment, the interface definition information is collected by setting the interface definition interactive interface, and the interface document is generated, which solves the problem of low front-end and back-end collaboration efficiency, and enables front-end technicians and back-end technicians to carry out development work at the same time, which not only satisfies The requirements of front-end technicians for test data can also avoid the need for back-end technicians to revise the interface code repeatedly in the later period.

Based on the above technical solution, optionally, the interface definition information includes basic information, request parameter information, and response data information, wherein the request parameter information includes Headers parameter information, Query parameter information, and Body parameter information.

On the basis of the above technical solution, optionally, the response simulation module 330 includes:

a target request parameter information determination unit, configured to match the request information with the request parameter information in the interface document to obtain the target request parameter information and the response data information corresponding to the target request parameter information;

The test data generating unit is used for generating test data corresponding to the request information according to the target request parameter information and the response data information.

On the basis of the above technical solution, optionally, the test data generation unit is specifically used for:

Verify the request information according to the target request parameter information;

If the verification is successful, test data corresponding to the request information is generated according to the response data information.

On the basis of the above technical solution, optionally, the device further includes:

The test data return module is used to return the verification result and the generated test data to the user; wherein the verification result includes a verification failure identifier and remark information corresponding to the verification failure identifier.

On the basis of the above technical solution, optionally, the device further includes:

The import module is configured to receive the interface document to be migrated input by the user, parse the interface definition information in the interface document to be migrated, and obtain the interface definition information that meets the requirements of the preset format.

On the basis of the above technical solution, optionally, the device further includes:

The export module is used to obtain the target export template and export interface definition information, and fill in the export interface definition information into the target export template to generate an export interface document.

The interface management apparatus provided by the embodiment of the present invention can be used to execute the interface management method provided by the embodiment of the present invention, and has corresponding functions and beneficial effects of the execution method.

It is worth noting that in the above-mentioned embodiment of the interface management apparatus, the units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be realized; The specific names of the functional units are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present invention.

Embodiment 4

8 is a schematic structural diagram of a device according to Embodiment 4 of the present invention. This embodiment of the present invention provides services for the implementation of the interface management method in the above-mentioned embodiment of the present invention, and the interface management apparatus in the above-mentioned embodiment can be configured. FIG. 8 shows a block diagram of an exemplary apparatus 12 suitable for use in implementing embodiments of the present invention. The device 12 shown in FIG. 8 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present invention.

As shown in FIG. 8, device 12 takes the form of a general-purpose computing device. Components of device 12 may include, but are not limited to, one or more processors or processing units 16, system memory 28, and a bus 18 connecting various system components including system memory 28 and processing unit 16.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of a variety of bus structures. By way of example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect ( PCI) bus.

Device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by device 12, including volatile and non-volatile media, removable and non-removable media.

System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32 . Device 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. For example only, storage system 34 may be used to read and write to non-removable, non-volatile magnetic media (not shown in FIG. 8, commonly referred to as a "hard disk drive"). Although not shown in Figure 8, a disk drive may be provided for reading and writing to removable non-volatile magnetic disks (eg "floppy disks"), as well as removable non-volatile optical disks (eg CD-ROM, DVD-ROM) or other optical media) to read and write optical drives. In these cases, each drive may be connected to bus 18 through one or more data media interfaces. Memory 28 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of various embodiments of the present invention.

A program/utility 40 having a set (at least one) of program modules 42, which may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data , each or some combination of these examples may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the described embodiments of the present invention.

Device 12 may also communicate with one or more external devices 14 (eg, keyboards, pointing devices, display 24, etc.), may also communicate with one or more devices that enable a user to interact with device 12, and/or communicate with Device 12 can communicate with any device (eg, network card, modem, etc.) that communicates with one or more other computing devices. Such communication may take place through input/output (I/O) interface 22 . Also, the device 12 may communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network such as the Internet) through a network adapter 20 . As shown in FIG. 8 , network adapter 20 communicates with other modules of device 12 via bus 18 . It should be understood that, although not shown, other hardware and/or software modules may be used in conjunction with device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and Data backup storage system, etc.

The processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28, for example, implementing the interface management method provided by the embodiments of the present invention.

Through the above equipment, the problem of low efficiency of front-end and back-end collaboration is solved, so that front-end technicians and back-end technicians can carry out development work at the same time, which not only meets the needs of front-end technicians for test data, but also avoids back-end technicians repeating later Revised interface code.

Embodiment 5

Embodiment 5 of the present invention also provides a storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute an interface management method when executed by a computer processor, and the method includes:

When receiving the interface definition instruction input by the user, display the interface definition interactive interface;

Collect interface definition information based on the interface definition interactive interface, and generate interface documents based on the interface definition information;

Receive externally input request information, and generate test data corresponding to the request information according to the request information and the interface document.

The computer storage medium in the embodiments of the present invention may adopt any combination of one or more computer-readable mediums. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (a non-exhaustive list) of computer readable storage media include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), Erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

A computer-readable signal medium may include a propagated data signal in baseband or as part of a carrier wave, with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device .

Program code embodied on a computer readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations of the present invention may be written in one or more programming languages, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural A programming language, such as the "C" language or similar programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. Where a remote computer is involved, the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN) or wide area network (WAN), or may be connected to an external computer (eg, using an Internet service provider to connect through the Internet) ).

Of course, a storage medium containing computer-executable instructions provided by an embodiment of the present invention, the computer-executable instructions thereof are not limited to the above method operations, and can also perform related operations in the interface management method provided by any embodiment of the present invention. .

Note that the above are only preferred embodiments of the present invention and applied technical principles. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present invention. The scope is determined by the scope of the appended claims.

Claims (10)

1. An interface management method, comprising:

when an interface definition instruction input by a user is received, displaying an interface definition interactive interface;

collecting interface definition information based on the interface definition interactive interface, and generating an interface document based on the interface definition information;

and receiving request information input from the outside, and generating test data corresponding to the request information according to the request information and the interface document.

2. The method of claim 1, wherein the interface definition information comprises basic information, request parameter information, and response data information, wherein the request parameter information comprises heads parameter information, Query parameter information, and Body parameter information.

3. The method of claim 2, wherein generating test data corresponding to the request information from the request information and the interface document comprises:

matching the request information with request parameter information in the interface document to obtain target request parameter information and response data information corresponding to the target request parameter information;

and generating test data corresponding to the request information according to the target request parameter information and the response data information.

4. The method of claim 3, wherein generating test data corresponding to the request information according to the target request parameter information and the response data information comprises:

checking the request information according to the target request parameter information;

and if the verification is successful, generating test data corresponding to the request information according to the response data information.

5. The method of claim 4, further comprising:

returning the verification result and the generated test data to the user; and the verification result comprises a verification failure identifier and remark information corresponding to the verification failure identifier.

6. The method of claim 1, further comprising:

receiving an interface document to be migrated, which is input by a user, and analyzing interface definition information in the interface document to be migrated to obtain interface definition information meeting the requirement of a preset format.

7. The method of claim 1, further comprising:

and acquiring a target export template and export interface definition information, and filling the export interface definition information into the target export template to generate an export interface document.

8. An interface management apparatus, comprising:

the interface definition module is used for displaying an interface definition interactive interface when receiving an interface definition instruction input by a user, acquiring interface definition information input by the user based on the interface definition interactive interface, and generating an interface document based on the interface definition information;

the information transmission module is used for receiving request information input by a user;

and the response simulation module is used for generating test data corresponding to the request information according to the request information and the interface document.

9. An apparatus, comprising:

one or more processors;

a memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the interface management method of any of claims 1-7.

10. A storage medium containing computer-executable instructions for performing the interface management method of any one of claims 1-7 when executed by a computer processor.

Images