Data generation method, software development system, electronic equipment and storage medium

Abstract

The invention is suitable for the technical field of computers, and provides a data generation method, a software development system, electronic equipment and a storage medium, and the method comprises the following steps: receiving an interface calling request sent by a front end; according to the request address, calling a preset back-end interface service to obtain a calling result of the target interface; if the calling result indicates that the target interface does not exist, searching interface data structure information comprising the request address and the request type from at least one piece of pre-stored interface data structure information according to the interface calling request and pre-stored searching path configuration information, and sending the interface data structure information to the target interface; determining the searched interface data structure information as target interface data structure information; and generating target interface simulation data of the target interface according to the target interface data structure information, and sending the target interface simulation data to the front end. The joint debugging efficiency of front and rear end interfaces can be improved.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular to a data generation method, a software development system, an electronic device and a storage medium. Background Art

[0002] In the process of software project development, it is usually necessary to conduct joint debugging of the front-end and back-end interfaces. When conducting joint debugging of the front-end and back-end interfaces, the front-end calls the back-end interface, and the back-end interface transmits data to the front-end, which displays the data. When the display is abnormal, the front-end code and the back-end code can be integrated and tested to ensure that the entire system can operate normally.

[0003] In the related art, the joint debugging of the front-end and back-end interfaces often depends on the progress of the back-end interface development. If the back-end interface is not well developed, it cannot be called, resulting in low efficiency of the joint debugging of the front-end and back-end interfaces. Summary of the invention

[0004] The embodiments of the present application provide a data generation method, a software development system, an electronic device and a storage medium, which can solve the problem in the related art that when the back-end interface is not well developed, it cannot be called, resulting in low efficiency of front-end and back-end interface joint debugging.

[0005] A first aspect of an embodiment of the present application provides a data generation method, including:

[0006] Receive an interface call request sent by the front end, wherein the interface call request includes a request address and a request type, and the request address is used to access the target interface;

[0007] According to the request address, call the preset backend interface service to obtain the call result of the target interface;

[0008] If the call result indicates that the target interface does not exist, searching for the interface data structure information including the request address and the request type from at least one pre-stored interface data structure information according to the interface call request and the pre-stored search path configuration information, and determining the found interface data structure information as the target interface data structure information;

[0009] According to the target interface data structure information, target interface simulation data of the target interface is generated, and the target interface simulation data is sent to the front end.

[0010] A second aspect of an embodiment of the present application provides a data generating device, including:

[0011] A request receiving unit is used to receive an interface call request sent by the front end, wherein the interface call request includes a request address and a request address, and the request address is used to access the target interface; a service calling unit is used to call a preset back-end interface service according to the request address to obtain a call result for the target interface; an information acquiring unit is used to search for interface data structure information including the request address and the request type from at least one pre-stored interface data structure information according to the interface call request and pre-stored search path configuration information if the call result indicates that the target interface does not exist, and determine the found interface data structure information as the target interface data structure information; a data generating unit is used to generate target interface simulation data of the target interface according to the target interface data structure information, and send the target interface simulation data to the front end.

[0012] The third aspect of the embodiment of the present application provides a software development system, including a front end and a back end, wherein the front end is used to send an interface call request to the back end, the interface call request includes a request address and a request type, and the request address is used to access a target interface. The back end is used to provide the front end with data of a target interface adapted to the interface call request using each step of the data generation method provided in the first aspect during the software development process.

[0013] The fourth aspect of an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data generation method provided in the first aspect when executing the computer program.

[0014] A fifth aspect of an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, each step of the data generation method provided in the first aspect is implemented.

[0015] The implementation of the data generation method, software development system, electronic device and storage medium provided by the embodiments of the present application has the following beneficial effects: calling the preset backend interface service through the request address in the interface call request, and when the call result indicates that the target interface does not exist, using the interface call request and the search path configuration information, searching the target interface data structure information including the request address and the request type from the pre-stored interface data structure information, generating the target interface simulation data of the target interface through the target interface data structure information, and sending the target interface simulation data to the front end. In this way, when the backend interface is not well developed, the front end can use the generated target interface simulation data to complete the front-end and back-end interface joint debugging, avoiding the need to wait for the backend interface to be developed before the front-end and back-end interface joint debugging can be performed, which helps to reduce the dependence of the front-end and back-end interface joint debugging on the progress of the back-end interface development, and can achieve the simultaneous development of the front-end interface and the back-end interface, which helps to improve the efficiency of the front-end and back-end interface joint debugging. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 is a flow chart of an implementation of a data generation method provided in an embodiment of the present application;

[0018] Figure 2 This is a flowchart for obtaining target interface data structure information provided by an embodiment of the present application;

[0019] Figure 3 is a flowchart for obtaining target interface data structure information provided by another embodiment of the present application;

[0020] Figure 4 is a flowchart for obtaining target interface data structure information provided by another embodiment of the present application;

[0021] Figure 5 This is a flowchart for realizing the generation of target interface simulation data provided by an embodiment of the present application;

[0022] Figure 6 is a flow chart of an implementation of a data generation method provided by another embodiment of the present application;

[0023] Figure 7 is a flow chart of an implementation of a data generation method provided by another embodiment of the present application;

[0024] Figure 8 is a flowchart of implementing an interface loader loading interface information provided by an embodiment of the present application;

[0025] Fig. 9 It is a flowchart of the implementation of the data generator generating simulation data provided by an embodiment of the present application;

[0026] Fig.10 is a structural block diagram of a data generating device provided in one embodiment of the present application;

[0027] Fig.11 It is a structural block diagram of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0028] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0029] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0030] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0031] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0032] In order to illustrate the technical solution of the present application, the following embodiments are used for illustration.

[0033] See also Figure 1 , Figure 1 This is a flowchart for implementing a data generation method provided in an embodiment of the present application. The flowchart may include the following steps 101 to 104.

[0034] Step 101: Receive an interface call request sent by a front end.

[0035] Among them, the above-mentioned interface call request is usually information for requesting to call the back-end interface. The interface call request usually includes a request address and a request type. The request address is used to access the target interface, and the request address is usually the access address of the target interface. The request type is usually the type of the interface call request. For example, the request type can be a get type, a post type, a put type, an options type, etc. In actual applications, the above-mentioned interface call request may also include other information, for example, it may also include a request source address. Among them, the above-mentioned request source address is usually the address of the front-end interface that sends the interface call request. Among them, the above-mentioned target interface is the interface that the front-end needs to call.

[0036] In this embodiment, the execution subject of the above data generation method is usually an electronic device, which can be specifically a backend. It should be noted that the electronic device can be hardware or software. When the electronic device is hardware, it can be implemented as a distributed electronic device cluster consisting of multiple electronic devices, or it can be implemented as a single electronic device. When the electronic device is software, it can be implemented as multiple software or software modules, or it can be implemented as a single software or software module, which is not specifically limited here.

[0037] In practice, the front end can send the above-mentioned interface call request to the above-mentioned execution entity through the network, so that the above-mentioned execution entity can receive the above-mentioned interface call request through the network, and obtain the information carried in the interface call request, such as the above-mentioned request address and request type carried in the interface call request.

[0038] Step 102, calling a preset backend interface service according to the request address, and obtaining a calling result of the target interface.

[0039] Among them, the above-mentioned preset backend interface service is usually a pre-set service for simulating the backend interface. Among them, the above-mentioned call result is usually used to indicate whether the target interface exists. In practice, the call result can be implemented as a callback function. The callback function is usually a function passed as a parameter, and the callback function includes parameters indicating the call result, and different call results correspond to different parameter values. For example, when the call result indicates that the target interface exists, the corresponding parameter value in the callback function can be 200; when the call result indicates that the target interface does not exist, the corresponding parameter value in the callback function can be 404.

[0040] In practice, after obtaining the request address, the electronic device can call the preset backend interface service, and send the request address to the preset backend interface service, triggering the preset backend interface service to find the target interface corresponding to the request address. When the target interface exists in the preset backend interface service, the interface data of the target interface can be obtained. At this time, the preset backend interface service can return the call result indicating the existence of the target interface to the electronic device and the interface data of the target interface. When the preset backend interface service does not exist, the call result indicating that the target interface does not exist can be returned to the electronic device. Among them, the above-mentioned preset backend interface service can be a service running in the electronic device, or it can be a proxy service outside the electronic device. When the preset backend interface service is a proxy service, the electronic device can process the interface call request by calling the proxy service and receive the call result returned by the proxy service, which helps to ensure the security of the electronic device. For example, if the call result is "1", it indicates that the target interface exists, and the call result is "0", it indicates that the target interface does not exist. When the target interface exists in the preset backend interface service, the preset backend interface service can return the call result "1" indicating the existence of the target interface to the electronic device, and return the interface data of the target interface. When the preset backend interface service does not have a target interface, the preset backend interface service may return a call result "0" indicating that the target interface does not exist to the electronic device. It should be noted that this embodiment does not limit the implementation form of the call result.

[0041] In some embodiments, when calling a preset backend interface service, the above-mentioned execution entity usually needs to first load a pre-stored service configuration file, then read the service configuration information in the service configuration file, and start the preset backend interface service based on the service configuration information to implement the various functions of the preset backend interface service. Among them, the above-mentioned service configuration information is usually used to configure the preset backend interface service. In practice, the preset backend interface service is used to implement the functions of each backend interface. For example, when calling a backend interface, the preset backend interface service can return the data of the backend interface.

[0042] In some implementations, if the call result indicates that the target interface exists, the call result returned by the execution entity may include interface data of the target interface.

[0043] Step 103: If the call result indicates that the target interface does not exist, then based on the interface call request and the pre-stored search path configuration information, search for the interface data structure information including the request address and the request type from at least one pre-stored interface data structure information, and determine the found interface data structure information as the target interface data structure information.

[0044] Wherein, the above-mentioned search path configuration information is usually information pointing to the path for searching the target interface data structure information. In practice, the path pointed to by the search path configuration information may include a cache file, an interface management server, etc. Wherein, the cache file is usually used to cache the interface data structure information, and the interface management server is usually a server for storing the interface data structure information. As an example, the interface management server may be a YApi server, a Swagger server, etc. Wherein, the above-mentioned target interface data structure information is usually the interface data structure information of the target interface, the interface data structure information is usually information describing the interface, and the interface data structure information may include the request type of the interface, the request address of the interface, the request parameters of the interface, the response body of the interface, etc. Wherein, the request type of the interface is usually used to indicate the type of request for calling the back-end interface, such as get type, post type, put type, options type, etc. The request address of the interface is usually used to access the corresponding interface. For example, the request address of the interface may be the uniform resource locator (URL) of the interface. The request parameters of the interface are usually the input parameters of the interface. In practice, the front end sends the request parameters of the interface to the back end, and the back end uses the received request parameters of the interface for corresponding processing. The response body of the interface is usually the result output by the backend in response to the interface call request.

[0045] In practice, after the above-mentioned execution subject calls the preset back-end interface service and obtains the call result of the target interface, the call result can be classified. For example, when the call result is implemented as a callback function, the call result can be classified based on the parameter value in the callback function. If the call result indicates that the target interface exists, that is, the back-end has developed the target interface corresponding to the current interface call request, and the back-end has the interface data corresponding to the current interface call request, the above-mentioned execution subject can directly use the interface data as the response data of the current interface call request and send the interface data to the front-end. If the call result indicates that the target interface does not exist, that is, the back-end has not yet developed the target interface corresponding to the current interface call request, and the back-end does not have the data corresponding to the current interface call request, the above-mentioned execution subject can search for the interface data structure information including the request address and the request type according to the path pointed to by the pre-stored search path configuration information, and determine the found interface data structure information as the target interface data structure information. As an example, the execution subject may use the request type in the interface call request to match the request type of the interface of each interface data structure information pre-stored in the corresponding path, and use the request type in the interface call request to match the request type of the interface of each interface data structure information pre-stored in the corresponding path to obtain the interface data structure information including the request address and request type of the interface call request in the corresponding path, and determine the obtained interface data structure information as the target interface data structure information. As another example, the execution subject may obtain the search path of the interface data structure information by searching the path configuration information, and then use the interface call request to search for the interface data structure information corresponding to the interface call request from the pre-established call request-interface data structure information correspondence table under the search path, and determine the obtained interface data structure information as the target interface data structure information. Among them, the call request-interface data structure information correspondence table may be a correspondence table pre-established by the execution subject, storing the correspondence between multiple call requests and interface data structure information.

[0046] Step 104: Generate target interface simulation data of the target interface according to the target interface data structure information, and send the target interface simulation data to the front end.

[0047] In practice, the above-mentioned execution subject can input the target interface data interface information into a pre-trained simulation data generation model, such as a convolutional neural network model, a recurrent neural network model, a support vector machine model, etc., to generate the target interface simulation data of the target interface, or can use simulation data generation tools, such as JsonSchemaFaker, Data-Processer, lazy-mock, etc., to generate the target interface simulation data of the target interface. After generating the target interface simulation data of the target interface, the above-mentioned execution subject can send the generated target interface simulation data to the front end.

[0048] The data generation method provided in this embodiment calls the preset backend interface service through the request address in the interface call request. When the call result indicates that the target interface does not exist, the interface call request and the search path configuration information are used to search the target interface data structure information including the request address and the request type from the pre-stored interface data structure information. The target interface simulation data of the target interface is generated through the target interface data structure information, and the target interface simulation data is sent to the front end. In this way, when the backend interface is not well developed, the front end can use the generated target interface simulation data to complete the front-end and back-end interface joint debugging, avoiding the need to wait for the backend interface to be developed before the front-end and back-end interface joint debugging can be performed, which helps to reduce the dependence of the front-end and back-end interface joint debugging on the progress of the back-end interface development, and can achieve the simultaneous development of the front-end interface and the back-end interface, which helps to improve the efficiency of the front-end and back-end interface joint debugging.

[0049] In some embodiments, the search path configuration information may include first path information and second path information, wherein the first path information points to the target cache file and the second path information points to the target interface management server. Figure 2 , Figure 2 This is an implementation flowchart for obtaining target interface data structure information provided by an embodiment of the present application. The flowchart may include the following steps 201 to 202.

[0050] Step 201: search for interface data structure information including a request address and a request type from a target cache file pointed to by the first path information, and determine the found interface data structure information as target interface data structure information.

[0051] Among them, the above-mentioned first path information can be implemented as a field in the search path configuration information, such as an access token field. The token field is usually used to identify the file name of the cache file. The file name of the target cache file usually matches the first path information, and the file name of the target cache file can be the same as or corresponding to. As an example, if the file name of the target cache file is "one two three" and the first path information is "123", it can be considered that the file name of the target cache file corresponds to the first path information. At this time, the file name of the target cache file matches the first path information.

[0052] In practice, the above-mentioned execution entity can search for interface data structure information that includes both the request address of the interface call request and the request type of the interface call request from the various interface data structure information stored in the target cache file pointed to by the first path information, and determine the found interface data structure information as the target interface data structure information.

[0053] Step 202: If the target interface data structure information does not exist in the target cache file, the interface data structure information including the request address and the request type is searched from the target interface management server pointed to by the second path information, and the found interface data structure information is determined as the target interface data structure information.

[0054] The second path information generally includes a server indication field, which is generally used to indicate a target interface management server, and the target interface management server generally corresponds to the server indication field in the second path information. For example, the Swagger server corresponds to the server indication field in the second path information.

[0055] In practice, when the target interface data structure information does not exist in the target cache file, the above-mentioned execution subject can obtain the target interface data structure information from the target interface management server pointed to by the second path information. Specifically, the above-mentioned execution subject can use the second path information to obtain the target interface management server, and then match the request addresses of each interface data structure information stored in the target interface management server with the request addresses of the interface call request, and match the request types of each interface data structure information stored in the target interface management server with the request types of the interface call request, to obtain interface data structure information that matches the request type and request address of the interface call request, and determine the obtained interface data structure information as the target interface data structure information.

[0056] In this embodiment, the target cache file is usually stored in the local memory. The target interface data structure information is first obtained from the target cache file pointed to by the first path information, which can achieve rapid acquisition of the target interface data structure information, improve the efficiency of obtaining the target interface data structure information, and help improve the efficiency of generating simulation data. When the target interface data structure information does not exist in the target cache file, the target interface data structure information is then obtained from the target interface management server pointed to by the second path information, which helps to ensure the stability of obtaining the target interface data structure information.

[0057] In some embodiments, when the target interface data structure information does not exist in the target cache file and the target interface data structure information does not exist in the target interface management server, it means that the target interface requested in the interface call request is wrong, and the above-mentioned execution entity can send indication information indicating response failure to the front end.

[0058] In some embodiments, after determining the found interface data structure information as the target interface data structure information, the method may further include: storing at least one interface data structure information included in the target interface management server into a target cache file.

[0059] The at least one interface data structure information includes the target interface data structure information. In practice, the execution subject can create a target cache file according to a preset file name format, and then store the at least one interface data structure information included in the target interface management server into the target cache file.

[0060] In this embodiment, at least one interface data structure information included in the target interface management server is stored in the target cache file, which facilitates the subsequent direct acquisition of the target interface data structure information from the target cache file, and helps to improve the efficiency of acquiring the target interface data structure information.

[0061] See also Figure 3 , Figure 3 This is an implementation flowchart for obtaining target interface data structure information provided by another embodiment of the present application. The flowchart may include the following steps 301 to 302.

[0062] Step 301: If the target interface management server pointed to by the second path information is a YApi server, a message acquisition request is sent to the YApi server.

[0063] Among them, the above-mentioned message acquisition request is usually used to trigger the YApi server to return at least one interface data structure information stored in the YApi server. In practice, the YApi server can send all stored interface data structure information based on the received message acquisition request. When the target interface management server pointed to by the second path information is a YApi server, the above-mentioned execution subject can generate a message acquisition request through the http request tool and the first path information, and then send the message acquisition request to the YApi server, triggering the YApi server to return at least one interface data structure information stored in the YApi server. Among them, the http request tool is usually a tool for initiating http requests, such as Axios. For example, a message acquisition request is generated through Axios and the token field, and then the message acquisition request is sent to the YApi server, triggering the YApi server to return at least one interface data structure information stored in the YApi server.

[0064] Step 302: Receive at least one interface data structure information returned by the YApi server, and search for the interface data structure information including the request address and the request type from the at least one interface data structure information obtained.

[0065] In practice, for each interface data structure information obtained, the above-mentioned execution entity can match the request address in the interface data structure information with the request address included in the interface call request, and match the request type in the interface data structure information with the request type included in the interface call request, to obtain interface data structure information in which the corresponding request address matches the request address of the interface call request, and the corresponding request type matches the request type of the interface call request.

[0066] In this embodiment, when the target interface management server pointed to by the second path information is a YApi server, a message acquisition request is sent to the YApi server, and interface data structure information including a request address and a request type is searched from at least one interface data structure information returned by the YApi server, which helps to improve the efficiency of obtaining the target interface data structure information.

[0067] See also Figure 4 , Figure 4 This is a flowchart for implementing obtaining target interface data structure information provided by another embodiment of the present application. The flowchart may include the following steps 401 to 402.

[0068] Step 401: If the target interface management server pointed to by the second path information is a Swagger server, the interface data address of the Swagger server is determined according to the request address.

[0069] The above interface data address is adapted to the request address of the interface call request. In practice, the interface data address may be the same as the request address.

[0070] In practice, when the target interface management server pointed to by the second path is a Swagger server, the interface data address of the Swagger server usually corresponds to the request address in the interface call request, and the above-mentioned execution entity can directly use the request address in the interface call request as the interface data address of the Swagger server.

[0071] Step 402: Obtain at least one interface data structure information stored in the Swagger server from the interface data address of the Swagger server, and search for interface data structure information including the request type from the at least one interface data structure information obtained.

[0072] In practice, the Swagger server may send the stored interface data structure information when the interface data address is accessed. The execution subject may obtain at least one interface data structure information stored in the Swagger server from the interface data address of the Swagger server through Axios and the interface data address of the Swagger server. For each interface data structure information obtained, the execution subject may match the request type in the interface data structure information with the request type included in the interface call request to obtain the interface data structure information including the request type.

[0073] In this embodiment, when the target interface management server is a Swagger server, at least one interface data structure information stored in the Swagger server is obtained from the interface data address of the Swagger server, and interface data structure information including the request type is searched from the at least one interface data structure information obtained, which helps to improve the efficiency of obtaining the target interface data structure information.

[0074] See also Figure 5 , Figure 5 This is an implementation flowchart of generating target interface simulation data provided by an embodiment of the present application. The flowchart may include the following steps 501 to 502.

[0075] Step 501: Generate a data file name according to the request type and request address included in the target interface data structure information.

[0076] In practice, the request type included in the target interface data structure information is the same as or corresponds to the request type in the interface call request, and the request address included in the target interface data structure information is the same as or corresponds to the request address in the interface call request. In practice, the above-mentioned execution entity can generate a data file name according to the format of the pre-set data file name using the request type and request address included in the target interface data structure information. For example, the format of the pre-set data file name is [request address].[request type].json, the request type included in the target interface data structure information is post, and the request address included in the target interface data structure information is A, and the data file name [A].[post].json can be generated.

[0077] Step 502, searching for a target simulation data cache file whose corresponding file name matches the data file name from the currently cached simulation data cache file, and determining the interface simulation data in the target simulation data cache file as the target interface simulation data.

[0078] In practice, the currently cached simulation data cache file pre-stores multiple simulation data cache files, and each simulation data cache file may include multiple interface simulation data. The above-mentioned execution subject may use the file names corresponding to the currently cached simulation data cache files to match the generated data file names respectively, determine the simulation data cache file whose corresponding file name matches the generated data file name as the target simulation data cache file, and then determine the interface simulation data in the target simulation data cache file as the target interface simulation data.

[0079] In this embodiment, the request type and request address included in the target interface data structure information are used to generate a data file name, and the target simulation data cache file whose corresponding file name matches the data file name is searched from the currently cached simulation data cache file, and the interface simulation data in the target simulation data cache file is determined as the target interface simulation data. The target interface simulation data can be quickly obtained from the currently cached simulation data cache file, which helps to improve the efficiency of generating simulation data.

[0080] In some embodiments, after the interface simulation data in the target simulation data cache file is determined as the target interface simulation data, the following steps 1 and 2 may also be included.

[0081] Step 1: If there is no target simulation data cache file whose corresponding file name matches the data file name, the request type and request address are input into a pre-established data generation model to obtain target interface simulation data of the target interface.

[0082] Among them, the above-mentioned data generation model is usually a pre-established model for generating interface simulation data. In practice, the data generation model is used to characterize the correspondence between the request type and request address and the target interface simulation data. The data generation model can be an artificial intelligence model, such as the ChatGPT model, or it can be a simulation data generation tool, such as JsonSchemaFaker. In practice, when there is no target simulation data cache file with a corresponding file name matching the generated data file name in the currently cached simulation data cache file, the above-mentioned execution subject can first input the request type and request address into the artificial intelligence model, and use the artificial intelligence model to generate interface simulation data. If the artificial intelligence model cannot generate interface simulation data, the above-mentioned execution subject can then input the request type and request address into the simulation data generation tool, and use the simulation data generation tool to generate interface simulation data. For example, when there is no target simulation data cache file whose file name matches the generated data file name in the currently cached simulation data cache file, first input the request type and request address into the ChatGPT model, and use the ChatGPT model to generate interface simulation data. If the ChatGPT model cannot generate interface simulation data, then input the request type and request address into JsonSchemaFaker, and use JsonSchemaFaker to generate interface simulation data. Afterwards, the above-mentioned execution entity can use the interface simulation data generated by the artificial intelligence model or simulation data generation tool as the target interface simulation data of the target interface.

[0083] Step 2: Generate a simulation data cache file according to the data file name and the target interface simulation data, and cache the generated simulation data cache file.

[0084] In practice, the execution subject may use the data file name as the file name to create a simulation data cache file, and then store the target interface simulation data into the simulation data cache file.

[0085] In this embodiment, when there is no target simulation data cache file with a corresponding file name matching the data file name in the currently cached simulation data cache file, the target interface simulation data is generated by using an artificial intelligence model, which can quickly generate the target interface simulation data and improve the efficiency of generating simulation data. When the artificial intelligence model cannot generate the target interface simulation data, the target interface simulation data is generated by using a simulation data generation tool, which can ensure that the target interface simulation data of the target interface can be generated, which helps to improve the stability of generating the target interface simulation data. The generated target interface simulation data is stored in the simulation data cache file, so that when the target interface simulation data is subsequently obtained, it can be directly obtained from the cached simulation data cache file, which helps to improve the efficiency of obtaining the target interface simulation data.

[0086] See also Figure 6 , Figure 6 It is a flowchart of the implementation of the data generation method provided by another embodiment of the present application, and the flowchart may include the following steps 601 to 6013. Steps 601 to 6013 are executed by the electronic device, and may be specifically executed by the back end.

[0087] Step 601, load the service configuration file and read the service configuration information.

[0088] Here, the execution subject can load the service configuration file through the yaml.load() method in js-yaml to read the service configuration information therein.

[0089] Step 602: Receive an interface call request sent by the front end.

[0090] Step 603: Call the preset backend interface service according to the request address to obtain the call result of the target interface.

[0091] Here, after obtaining the request address, the above-mentioned execution subject can call the preset backend interface service, and send the request address to the preset backend interface service, triggering the preset backend interface service to find the target interface corresponding to the request address, and obtain the call result of the target interface.

[0092] Step 604, determine whether the call is successful, if the call is successful, execute step 605, if the call is unsuccessful, execute step 606.

[0093] Step 605: Send response data to the front end.

[0094] Here, the response data is the interface data of the target interface. When the call is successful, the response data can be sent to the front end.

[0095] Step 606: Search the target interface data structure information including the request address and the request type from the target cache file.

[0096] Here, when the call fails, the target interface data structure information can be obtained from the target cache file first.

[0097] Step 607: If the target cache file does not contain the target interface data structure information, determine the target interface management server.

[0098] In practice, there are usually multiple interface management servers, and the above-mentioned execution subject can determine the target interface management server by searching the server indication field in the path configuration information.

[0099] Step 608: If the target interface management server is a YApi server, the target interface data structure information is obtained from the YApi server.

[0100] Here, when the target interface management server is a YApi server, the execution subject may obtain the target interface data structure information matching the request type and the request address through the YApi server.

[0101] Step 609: If the target interface management server is a Swagger server, the target interface data structure information is obtained from the Swagger server.

[0102] Here, when the target interface management server is a Swagger server, the above-mentioned execution subject can obtain the target interface data structure information matching the request type and the request address through the Swagger server.

[0103] Step 6010: Store at least one interface data structure information included in the target interface management server into the target cache file.

[0104] Here, the execution subject may store all interface data structure information included in the target interface management server into the target cache file.

[0105] Step 6011, searching for a target simulation data cache file from the currently cached simulation data cache files, and determining the interface simulation data therein as the target interface simulation data.

[0106] Here, the above-mentioned execution entity can use the request type and request address included in the target interface data structure information to generate a data file name, and then use the generated data file name to search for a target simulation data cache file that matches the data file name from the currently cached simulation data cache file, and determine the interface simulation data in the target simulation data cache file as the target interface simulation data.

[0107] Step 6012: If the target simulation data cache file does not exist in the currently cached simulation data cache file, the target interface simulation data is generated by using a pre-established data generation model.

[0108] Here, the target interface simulation data can be generated by using a pre-established data generation model.

[0109] Step 6013, storing the generated target interface simulation data into a simulation data cache file.

[0110] Here, the execution subject may create a simulation data cache file based on the data file name, and then store the target interface simulation data into the simulation data cache file.

[0111] In this embodiment, the specific operations of steps 601-6013 are substantially the same as those in the above embodiments, and will not be described in detail herein.

[0112] See also Figure 7 , Figure 7 This is a flowchart of a data generation method provided by another embodiment of the present application, and the flowchart may include the following steps 701 to 7011. Steps 701 to 7011 are executed by the electronic device, and may be specifically executed by the backend.

[0113] Step 701: Receive an interface call request sent by the front end.

[0114] Here, the interface call request includes a request address, and the request address is used to access the target interface.

[0115] Step 702, determine whether to proxy the backend interface service.

[0116] Here, the backend interface service is the above-mentioned preset backend interface service. When the backend interface service is proxy, step 703 is executed, and when the backend interface service is not proxy, step 706 is executed.

[0117] Step 703, proxy backend interface service.

[0118] In practice, the above execution entity can proxy the backend interface service based on the request address in the interface call request.

[0119] Step 704: the backend interface responds.

[0120] Here, the backend interface response is the above call result.

[0121] Step 705, determine whether the interface status is 404.

[0122] When the interface status is 404, step 706 is executed, and when the interface status is not 404, step 7010 is executed. Here, when the interface status is 404, it indicates that the backend interface does not exist, and when the interface status is 200, it indicates that the backend interface exists.

[0123] Step 706: The interface loader loads the interface information.

[0124] The interface loader is used to load the interface information. The interface loader corresponds to the above-mentioned preset storage device. The interface loader includes but is not limited to the above-mentioned target cache file and the interface management server. In practice, when the interface status is 404, the above-mentioned execution subject can load the interface information through the interface loader.

[0125] Step 707, determine whether the interface information is matched.

[0126] When the interface information is not matched, step 708 is executed, and when the interface information is matched, step 709 is executed. Here, the interface information corresponds to the above interface data structure information, and the matched interface information corresponds to the above target interface data structure information. In practice, the above execution subject can match the request address and request type of each interface information in the interface loader with the request address and request type in the interface call request, and determine whether the interface information is matched based on the matching result.

[0127] Step 708, return 404 request status.

[0128] Here, the 404 request status is usually information indicating that the request failed. In practice, when the interface information is not matched, it means that there is a problem with the target interface requested in the current interface call request, and the execution subject can return the 404 request status. Afterwards, the execution subject can execute step 706, use the 404 request status as the request response, and output the request response to the front end.

[0129] Step 709: The data generator generates simulation data.

[0130] Here, the data generator corresponds to the pre-established data generation model, and the simulation data corresponds to the target interface simulation data. In practice, when the interface information is matched, the execution subject can input the matched interface information into the data generator to generate simulation data.

[0131] Step 7010, generate simulation data and return 200 request status.

[0132] The 200 request status is used to indicate that the request is successful. In practice, after the simulation data is generated by the data generator, the execution subject may send the generated simulation data to the front end, and send the 200 request status to the front end.

[0133] Step 7011, output request response.

[0134] In practice, when the interface status is not 404, it indicates that the backend interface exists, and the above-mentioned execution subject can directly use the interface data as the response data of the current interface call request, and output the request response including the response data to the front end. In practice, when there is no interface information matching the interface call request in the interface information loaded by the interface loader, it indicates that there is a problem with the target interface requested in the current interface call request, and the above-mentioned execution subject can output the request response with the 404 request status to the front end. In practice, when the data generates simulation data, the above-mentioned execution subject can output the generated simulation data to the front end, as well as the 200 request status indicating that the request is successful.

[0135] See also Figure 8 , Figure 8This is a flowchart for implementing an interface loader loading interface information provided by an embodiment of the present application. The flowchart may include the following steps 801 to 806.

[0136] Step 801, obtaining interface information from the target cache file.

[0137] Here, the interface information is the above interface data structure information. In practice, the above execution subject can obtain the interface information including the request address and the request type from the target cache file.

[0138] Step 802, determine whether the interface information is obtained.

[0139] When the interface information is not obtained, step 803 is executed; when the interface information is obtained, step 806 is executed.

[0140] Step 803: determine the target interface management server.

[0141] In practice, the above execution entity may determine the target interface management server by searching the server indication field in the path configuration information.

[0142] Step 804: The target interface management server is a YApi server, and the YApi interface is downloaded.

[0143] In practice, when the target interface management server is a YApi server, the above-mentioned execution subject can send a message acquisition request to the YApi server to obtain the interface information of the YApi server.

[0144] Step 805: The target interface management server is a Swagger server, and the Swagger interface is downloaded.

[0145] In practice, when the target interface management server is a Swagger server, the above-mentioned execution subject can determine the interface data address of the Swagger server, and obtain the interface information in the Swagger server from the interface data address of the Swagger server.

[0146] Step 806, return interface information.

[0147] In practice, the above execution entity may return the interface information obtained from the target cache file, or the interface information obtained from the YApi server, or the interface information obtained from the Swagger server.

[0148] See also Fig. 9 , Fig. 9 This is an implementation flowchart of a data generator providing a data generator according to an embodiment of the present application generating simulation data. The flowchart may include the following steps 901 to 906.

[0149] Step 901, obtaining interface data from a simulation data cache file.

[0150] Here, the interface data is the target interface simulation data. In practice, the execution subject can generate a data file name based on the target interface data structure information, and then search the simulation data cache file for the interface data that matches the data file name.

[0151] Step 902, determine whether the interface data is obtained, if the interface data is not obtained, execute step 903, if the interface data is obtained, execute step 906.

[0152] Step 903, using OpenAI to generate simulated data.

[0153] In practice, the above-mentioned execution entity can input the request type and request address into Openai and use Openai to generate simulation data.

[0154] Step 904, determine whether the generation is successful.

[0155] When the data is not generated successfully, step 905 is executed, and when the data is generated successfully, step 906 is executed.

[0156] Step 905, using JsonSchemaFaker to generate simulation data.

[0157] In practice, the above execution entity can input the request type and request address into JsonSchemaFaker and use JsonSchemaFaker to generate interface simulation data.

[0158] Step 906, returning interface data.

[0159] Here, the interface data is the target interface simulation data. In practice, the returned interface data can be the interface data obtained from the simulation data cache file, or the simulation data generated by OpenAI, or the simulation data generated by JsonSchemaFaker.

[0160] See also Fig.10 , Fig.10 1 is a structural block diagram of a data generating device 1000 provided in an embodiment of the present application, including:

[0161] A request receiving unit 1001 is used to receive an interface call request sent by a front end, wherein the interface call request includes a request address and a request type, and the request address is used to access a target interface; a service calling unit 1002 is used to call a preset back-end interface service according to the request address to obtain a call result for the target interface; an information acquiring unit 1003 is used to search for interface data structure information including the request address and the request type from at least one pre-stored interface data structure information according to the interface call request and pre-stored search path configuration information if the call result indicates that the target interface does not exist, and determine the found interface data structure information as the target interface data structure information; a data generating unit 1004 is used to generate target interface simulation data of the target interface according to the target interface data structure information, and send the target interface simulation data to the front end.

[0162] In some embodiments, the search path configuration information includes first path information and second path information, the first path information points to the target cache file, and the second path information points to the target interface management server; the information acquisition unit 1003 includes a cache acquisition module and an information matching module (not shown in the figure). The cache acquisition module searches for interface data structure information including the request address and the request type from the target cache file pointed to by the first path information, and determines the found interface data structure information as the target interface data structure information; the information matching module is used to search for interface data structure information including the request address and the request type from the target interface management server pointed to by the second path information if the target interface data structure information does not exist in the target cache file, and determines the found interface data structure information as the target interface data structure information.

[0163] In some embodiments, the information acquisition unit 1003 also includes an information storage module (not shown in the figure), which is used to store at least one interface data structure information included in the target interface management server into the target cache file, wherein the at least one interface data structure information includes the target interface data structure information.

[0164] In some embodiments, the information matching module is specifically used to: determine the interface management server that matches the server indication field among multiple interface management servers as the target interface management server, and obtain target interface data structure information that matches the target field, request type and request address from the target interface management server.

[0165] In some embodiments, the information matching module is further specifically used to: if the target interface management server pointed to by the second path is a YApi server, send a message acquisition request to the YApi server, wherein the message acquisition request is used to trigger the YApi server to return at least one interface data structure information stored in the YApi server; receive at least one interface data structure information returned by the YApi server, and search for interface data structure information including a request address and a request type from the at least one interface data structure information obtained.

[0166] In some embodiments, the information matching module is specifically used to: if the target interface management server pointed to by the second path is a Swagger server, determine the interface data address of the Swagger server according to the request address, wherein the interface data address matches the request address; obtain at least one interface data structure information stored in the Swagger server from the interface data address of the Swagger server, and search for interface data structure information including the request address and the request type from the at least one interface data structure information obtained.

[0167] In some embodiments, the data generation unit 1004 may further include a file generation module and a data determination module (not shown in the figure). The file generation module is used to generate a data file name according to the request type and request address included in the target interface data structure information; the data determination module is used to search for a target simulation data cache file whose corresponding file name matches the data file name from the currently cached simulation data cache file, and determine the interface simulation data in the target simulation data cache file as the target interface simulation data.

[0168] In some embodiments, the data generation unit 1004 may also include a model input module and a file cache module (not shown in the figure). The model input module is used to input the request type and the request address into a pre-established data generation model to obtain the target interface simulation data of the target interface if there is no target simulation data cache file whose corresponding file name matches the data file name, wherein the data generation model is used to characterize the corresponding relationship between the request type and the request address and the target interface simulation data; the file cache module is used to generate a simulation data cache file according to the data file name and the target interface simulation data, and cache the generated simulation data cache file.

[0169] The data generation device provided in this embodiment can use the generated target interface simulation data to complete the front-end and back-end interface joint debugging when the back-end interface is not developed, avoiding the need to wait for the back-end interface to be developed before the front-end and back-end interface joint debugging can be performed. This helps to reduce the dependence of the front-end and back-end interface joint debugging on the progress of the back-end interface development, and can achieve the simultaneous development of the front-end interface and the back-end interface, which helps to improve the efficiency of the front-end and back-end interface joint debugging.

[0170] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the data generation method in this application. Their specific functions and technical effects can be found in the embodiment section of the data generation method and will not be repeated here.

[0171] In some embodiments, the software development system may include a front end and a back end, wherein the front end is used to send an interface call request to the back end, the interface call request includes a request address and a request type, and the request address is used to access the target interface. The back end is used to provide the front end with data of the target interface adapted to the interface call request using the data generation method in the present application during the software development process.

[0172] See also Fig.11 , Fig.11 1 is a block diagram of an electronic device 1100 provided in an embodiment of the present application. The electronic device 1100 in this embodiment includes: at least one processor 1101 ( Fig.11 Only one processor is shown in the figure), a memory 1102, and a computer program 1103 stored in the memory 1102 and executable on at least one processor 1101, such as a data generation method program. When the processor 1101 executes the computer program 1103, the steps in the above-mentioned embodiments of the data generation method are implemented. When the processor 1101 executes the computer program 1103, the functions of the modules / units in the above-mentioned embodiments of the apparatus are implemented, such as, Fig.10 The functions of the request receiving unit 1001 to the data generating unit 1004 are shown.

[0173] Exemplarily, the computer program 1103 may be divided into one or more units, one or more units are stored in the memory 1102, and are executed by the processor 1101 to complete the present application. One or more units may be a series of computer program instruction segments that can complete specific functions, and the instruction segments are used to describe the execution process of the computer program 1103 in the electronic device 1100. For example, the computer program 1103 may be divided into a request receiving unit, a service calling unit, an information obtaining unit, and a data generating unit. The specific functions of each unit have been described in the above embodiments and will not be repeated here.

[0174] The electronic device 1100 may be a computing device such as an electronic device, a desktop computer, a tablet computer, a cloud electronic device, and a mobile terminal. The electronic device 1100 may include, but is not limited to, a processor 1101 and a memory 1102. Those skilled in the art will appreciate that Fig.11 It is only an example of the electronic device 1100 and does not constitute a limitation of the electronic device 1100. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0175] The processor 1101 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0176] The memory 1102 may be an internal storage unit of the electronic device 1100, such as a hard disk or memory of the electronic device 1100. The memory 1102 may also be an external storage device of the electronic device 1100, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device 1100. Optionally, the memory 1102 may also include both an internal storage unit of the electronic device 1100 and an external storage device. The memory 1102 is used to store computer programs and other programs and data required by the electronic device 1100. The memory 1102 may also be used to temporarily store data that has been output or is to be output.

[0177] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0178] If the integrated module is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and the computer program that can be completed by instructing the relevant hardware through a computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device that can carry computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.

[0179] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0180] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A data generation method, characterized in that: Applied to the backend, the method includes: Receiving an interface call request sent by the front end, wherein the interface call request includes a request address and a request type, and the request address is used to access a target interface; According to the request address, a preset backend interface service is called to obtain a call result of the target interface; If the call result indicates that the target interface does not exist, searching for interface data structure information including the request address and the request type from at least one pre-stored interface data structure information according to the interface call request and pre-stored search path configuration information, and determining the found interface data structure information as the target interface data structure information; According to the target interface data structure information, target interface simulation data of the target interface is generated, and the target interface simulation data is sent to the front end.

2. The data generation method according to claim 1, characterized in that: The search path configuration information includes first path information and second path information, the first path information points to the target cache file, and the second path information points to the target interface management server; The step of searching, according to the interface call request and the pre-stored search path configuration information, the interface data structure information including the request address and the request type from at least one pre-stored interface data structure information, and determining the found interface data structure information as the target interface data structure information comprises: Searching for interface data structure information including the request address and the request type from the target cache file pointed to by the first path information, and determining the found interface data structure information as the target interface data structure information; If the target interface data structure information does not exist in the target cache file, the interface data structure information including the request address and the request type is searched from the target interface management server pointed to by the second path information, and the found interface data structure information is determined as the target interface data structure information.

3. The data generation method according to claim 2, characterized in that: After determining the found interface data structure information as the target interface data structure information, the method further includes: The at least one interface data structure information included in the target interface management server is stored in the target cache file, wherein the at least one interface data structure information includes the target interface data structure information.

4. The data generation method according to claim 2, characterized in that: The step of searching the target interface management server pointed to by the second path information for interface data structure information including the request address and the request type includes: If the target interface management server pointed to by the second path information is a YApi server, sending a message acquisition request to the YApi server, wherein the message acquisition request is used to trigger the YApi server to return at least one interface data structure information stored in the YApi server; Receive at least one interface data structure information returned by the YApi server, and search for the interface data structure information including the request address and the request type from the received at least one interface data structure information.

5. The data generation method according to claim 2, characterized in that: The step of searching the target interface management server pointed to by the second path information for interface data structure information including the request address and the request type includes: If the target interface management server pointed to by the second path information is a Swagger server, determining the interface data address of the Swagger server according to the request address, wherein the interface data address is adapted to the request address; At least one interface data structure information stored in the Swagger server is obtained from the interface data address of the Swagger server, and the interface data structure information including the request type is searched from the obtained at least one interface data structure information.

6. The data generation method according to any one of claims 1 to 5, characterized in that: The step of generating target interface simulation data of the target interface according to the target interface data structure information comprises: Generate a data file name according to the request type and the request address included in the target interface data structure information; From the currently cached simulation data cache files, a target simulation data cache file whose corresponding file name matches the data file name is searched, and the interface simulation data in the target simulation data cache file is determined as the target interface simulation data.

7. The data generation method according to claim 6, characterized in that: After determining the interface simulation data in the target simulation data cache file as the target interface simulation data, the method further includes: If there is no target simulation data cache file whose corresponding file name matches the data file name, inputting the request type and the request address into a pre-established data generation model to obtain the target interface simulation data of the target interface, wherein the data generation model is used to characterize the corresponding relationship between the request type and the request address and the target interface simulation data; Generate a simulation data cache file according to the data file name and the target interface simulation data, and cache the generated simulation data cache file.

8. A software development system, characterized in that: The system comprises a front end and a back end; The front end is used to send an interface call request to the back end, the interface call request includes a request address and a request type, and the request address is used to access the target interface; The backend is used to provide the frontend with the data of the target interface adapted to the interface call request by adopting the method as described in any one of claims 1 to 7 during the software development process.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the data generating method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the data generating method according to any one of claims 1 to 7 is implemented.

Images